Develop Bugs

Would you consider this a clean install?

Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!

ivan.panchev said:
Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
Click to expand...
Click to collapse
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system

Lowxorx said:
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Click to expand...
Click to collapse
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!

ivan.panchev said:
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
Click to expand...
Click to collapse
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )

Lowxorx said:
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Click to expand...
Click to collapse
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!

ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you have the stock 3.2.6 zip file you can follow theses instructions on the official oneplus site. There are both TWRP and stock recovery guide.

ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"

noobtoob said:
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
Click to expand...
Click to collapse
After the second full charge, I think the things are a lot better - I have only used it for 30 minutes screen on today but is still on 82% (with more than 10 hours idle), which a lot like what I used to have when with 3.2.1. Plus, I am in an area with low network coverage, so that's draining the battery as well. Thanks for all of your answers, if I feel the need, will probably flash the whole stock rom with TWRP.

First time flashing an open beta from stock, non-rooted and locked bootloader

I am looking forward to flash the upcoming pie open beta on my stock, non-rooted 5t with locked bootloader and got some questions:
1. Do I need to register somewhere to be part of a beta program like it is with the google pixel line?
2. Are there OTAs where I do not have to wipe my storage or is there just one zip?
3. Is it even possible to go from stable to beta without wiping the storage?
4. Can I flash the zip via the settings app like I did several times with oxygen updater?
5. Can I go back to stable OOS version when pie is finally released without wiping? Even though: what would be wiped? Just apps or photos as well?
6. What version must I be on to flash a beta? I am currently running OOS 5.1.6 . Didn't update to 5.1.7 because I heard some people have insane battery drain
Looking forward for some answers!
Thanks

First of all there's no Android Pie in OP 5T Beta Oxygen OS yet.
Leaked Pie is Hydrogen OS which is official ROM for China, but it does not include Google Apps and you have to unlock bootloader in order to switch between HydrogenOS and OxygenOS. Unlocking bootloader will wipe EVERYTHING on your phone.
1. No
2. No, you have to download full zip in order to switch from stable to beta and you have to backup EVERYTHING on your phone before you do so.
3. Only with unlocked bootloader and custom recovery, but unlocking bootloader wipes everything on your phone.
4. No, zip downloaded from OnePlus' site must be flashed in recovery.
5. You can go back, but it will wipe everything on your phone.
6. It doesn't matter as you will be flashing full rom.

thanks a lot for your answers!
Youtube has some videos where people flash an open beta via settings menu over a stable image without loosing data but that must be somehow wrong.
Got another question regarding whatsapp:
This year there were news that whatsapp changed their backup service to be somehow different. I got very old chats on my phone I want to keep. I do daily google drive automatic backups.
If I restore my whatsapp after flashing the open beta. Will get all my chats back or will there be something missing?
thanks for the quick answer!

You don't have to wipe or unlock anything. Read official instruction: https://www.oneplus.com/pl/support/softwareupgrade/details?code=7

collection rom Gsi 9/10 for realmeQ/5pro

Hello !!!
Gsi Rom for realme Q
This is the best version for realme Q.Works well, but fingerprint error, hope someone can fix it
Installation Instructions:
1. Download the GSI from the links above, and uncompress it.
2. Wipe Data, Dalvik, and Cache,system . No wipe vendor
3. Remove Magisk if it was previously installed, by using its uninstaller script. Magisk files are stored in the kernel image, and in the /data/adb folder, which are left untouched when wiping data and flashing the GSI. Another option is to flash your stock rom and manually delete the content of the /data/adb folder.
4. Flash the GSI to system partition (AB devices : flashing a vbmeta.img file for your device may also be required).
5. Boot and perform a factory reset.
6. (Optional) Reboot and flash Magisk, and maybe additional files.
7. Reboot and Enjoy.
If you want to update rom, you can also always try to dirty flash, i.e. wipe Dalvik and Cache (not Data) and flash System image. But if you experience a strange behavior, a clean flash may be required
Note : if flash Gapps you need resize system in teamwin,then flash gapps
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
Rom download :
Link download android 9 rr7.0 : https://drive.google.com/file/d/1--pQfJlNR2V9OEFeLCoT--tmftT8OFGZ/view?usp=drivesdk
link download android 10 AOSP : Download
Link download Rom Msm 9 : Download
How to fix bug any rom:
Link download fix lag,fix bt audio,fix mtp,fix power rom havoc,magisk stable for android Q and more ..
Folder click here

Great, found your thread on telegram, this is what I need, I am fed up with Color OS

It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partition before flashing the image.

greenys' said:
It's not half bad but there are two major problems with the ROM. First it seems it can't read exfat 128 GB as card which is a shame for I won't format it to inferior fat32 to lose all my stuff. Second, whenever I set a screen lock, no matter what kind of it'll tell me that I entered incorrect code. Means I cannot lock the screen with any kind of security measure. I could solve the external as card issue by flashing lineage os boot.img but I couldn't the screen lock issue. Aside these I have no problem. Testing other gsi ROMs.
Edit.: No. Screen lock isn't rom but vendor issue. I accidentally wiped vendor partikon before flashing the image.
Click to expand...
Click to collapse
I will note that people do not wipe vendor

29y6145 said:
I will note that people do not wipe vendor
Click to expand...
Click to collapse
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?

greenys' said:
I just noticed that I didn't wipe vendor either. It's not even in the wipeable section if you try advanced wipe. For some reason if I go from one gsi to another lock screen password/pattern will not work. I have to flash stock zip first, then wipe data, system, cache, davlik and at last flash gsi image. Between going from one gsi to another you have to do this in order to keep lock screen password function. Right now I'm struggling with Magisk Safetynet. Any good method to bypass?
Click to expand...
Click to collapse
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.

29y6145 said:
I realized that. Today I tested android Q on realme Q, it worked. I cannot set the screen password, the system only allows swiping. I am looking into this problem.
Click to expand...
Click to collapse
Flashing stock vendor img solved the issue on my device. Although I tried AOSP Pie not Q.

update android 10 and permissiver for andoid 10

Update Installation Instructions .

Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?

Tmv_Josue said:
Hi, awesome thread, congrats to you @29y6145.
I see now that you added two more ROMs, the AOSP10 and the MSM-Xtended 9. Any of them are more stable than the others? I was looking for stability in the entire OS and Camera that any other thing.
By the way, Why you remove the links to TWRP and Permissiver_v5?
I installed the Resurrection Remix 7.0.2 and see that doesn't have Magisk by default. I should install Magisk via your TWRP built-in Magisk installer or from the official Magisk website?
Click to expand...
Click to collapse
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1

29y6145 said:
I am editing some posts, and will re upload important files.
Both of the 2 Roms you speak are fine. I will give you a tutorial about the Havoc rom.
I have upload permissiver #1
Click to expand...
Click to collapse
Did you manage to pass safetynet with gsi?

greenys' said:
Did you manage to pass safetynet with gsi?
Click to expand...
Click to collapse
You try

@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?

Tmv_Josue said:
@29y6145
This Petnoire's_SafetyNet_Spoofer_magisk.zip should be used instead of the Realme5ProColorOSMagiskFixBETA.zip?
Or both should be flashed?
Click to expand...
Click to collapse
You use Petnoire's_SafetyNet_Spoofer_magisk or module safeynet in magisk .
Im use module safety in magisk It works perfectly.

@29y6145
What is exactly the name of that Magisk's Safety module that you mentioned?
I searched in Magisk and only found hackintosh5's SafetyPatch and Didgeridoohan's MagiskHide Props Config.
Is any of them?

My realme Q device has unlocked BL and installed TWRP, while using lineage oS 16 Android P, how to refresh this Android Q GSI image? Is it refreshed directly with TWRP REC?

@TrancyMeng.
*Any ROM in IMG format should be flashed trought Fatboot, but you need to wipe the other installation first, in adb run this to enter in TWRP:
adb reboot recovery
Then in TWRP:
*Wipe > System, Data, Cache, Dalvik
*Reboot > BootLoader (Fastboot)
Then in Fastboot/Bootloader run this command:
fastboot flash system romNAME.img
Reboot to recovery/TWRP and flash:
Permissiver_v5.zip

After refresh the Andrews Q GSI ROM, why the speaker will have a current sound, and call and play the local media file will not. How to troubleshise the patch to do it? Can you trouble with you to provide a patch for the repair sound?

THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.

FAILED (remote: sparse image size span overflow.) error

Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
I recently wanted to give some GSI images a try and tried to flash AOSP. I tried to flash the system image using fastboot and also SP Flash Tool (of MTK). Both gave me the same error:
FAILED (remote: sparse image size span overflow.)
After getting this error, i reset my phone and my default system is still there, so nothing is being written to the system partition. I thought maybe treble AOSP images are larger than my phone's system partition but when i checked, the default system img of my phone is actually larger than the GSI images (I have also tried a "go" version of a gsi image with the same outcome).
What is my problem here please?
PS: My bootloader is unlocked.

What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.

Chaos Storm said:
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Click to expand...
Click to collapse
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?

twilightened said:
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
Click to expand...
Click to collapse
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.

Chaos Storm said:
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?

twilightened said:
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
Click to expand...
Click to collapse
No, you are doing it correctly. I think they compress them to save bandwidth.

just need to resize that partition

twilightened said:
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
Click to expand...
Click to collapse
Which device? Please tell.
I have also Blackview A20 (go).
Flash stock with spflash. Only for stock
Let it reboot. reset. Allow it to reboot once again. Check everything GPS/wifi/bt. Enable ON
Do not connect to Google accounts. not needed.
Enable adb
Charge at least 90% - some devices will NOT flash and silently ignore.
fastboot erase system
fastboot flash system gsi.img
fastboot reboot
If it asks you a password, just type anything. Then it will ask you reset phone. Say OK.
all done
Note always check the sha1sum or md5sum of GSI. Despite having

kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
Excuse me, I'm new to this, would you have a tutorial? I have several phones that would help

kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
how can i resize the partition pls?

how to rescue my data?

I'm using Official Pixel Experience 11.0 and I noticed there got a beta version for Pixel Experience 12, Considered it's "beta" instead of "alpha" or "prebuild", I think it wouldn't be that risky, So I just flashed it via the Pixel Experience Recovery's sideload. When I try to check how wonderful my new system was, Dang, it directly entered the Recovery and all my data have not been backup! I have tried to sideload to the old PE11 but not work. Then I installed twrp and orange fox tried to backup my data but seems data and sdcard partitions could not be unencrypt. Any have ideas about how to rescue my data? Or is there any way I could backup all the encrypted partition to a img so I could deal with this encrypt later instead of doing nothing? These data is important to me.

No. If tou carefully read instructions, you can not go from A11 to a12 without formatting data, then install now already we have beta.

tze_vitamin said:
No. If tou carefully read instructions, you can not go from A11 to a12 without formatting data, then install now already we have beta.
Click to expand...
Click to collapse
So it's all kinds of rom does not support ota update from a11 to a12 or just I used a wrong method? I wondered if I could take my data out from this phone without rescue the system? I could reinstall the system but I really export my data.

You will not find OTA custom ROM , a11 to A12, you can maybe find A12 to A12. But if you wait for stock ROM tou will get it OTA . custom ROM is different.. especially if someone is not encrypted and formatting is important to be able to flash and boot system

tze_vitamin said:
You will not find OTA custom ROM , a11 to A12, you can maybe find A12 to A12. But if you wait for stock ROM tou will get it OTA . custom ROM is different.. especially if someone is not encrypted and formatting is important to be able to flash and boot system
Click to expand...
Click to collapse
Thank you very much for you info, but I wondered if it is possible to export my data out of the phone?

I found on youtube, Put your phone into Fastboot and in ADB type Backup all
after installing system , again in ADB type restore.
try research about this commands on google to have it for next time if something similir happend