Database Users

Deleted everything - how to copy ROM on internal storage???

Hello.
I am german. Excuse my bad english.
I wiped everything. Also internal storage. Now the device don`t want to boot. I tried to copy a rom on internal storage but I dont even have access on it. I can boot in TWRP. I tried mount but cant activate USB Storage.
How can I copy a ROM on internal storage? Can anyone please help me?
Is there an IMG Rom that I can flash per fastboot?
Thank you...

maierbosch said:
Hello.
I am german. Excuse my bad english.
I wiped everything. Also internal storage. Now the device don`t want to boot. I tried to copy a rom on internal storage but I dont even have access on it. I can boot in TWRP. I tried mount but cant activate USB Storage.
How can I copy a ROM on internal storage? Can anyone please help me?
Is there an IMG Rom that I can flash per fastboot?
Thank you...
Click to expand...
Click to collapse
Via adb sideload in TWRP
https://twrp.me/faq/ADBSideload.html

I tried adb sideload in twrp. It gives me an error in twrp. In windows I can't connect to the handy via adb. Device can't be found.
But I will try again as shown in your link. Thank you.

Do you have fastboot?
Yes,
http://forum.xda-developers.com/showthread.php?t=3216511
No, check general forum for bricked guide.
Sent from my ONE A2005 using Tapatalk

maierbosch said:
I tried adb sideload in twrp. It gives me an error in twrp. In windows I can't connect to the handy via adb. Device can't be found.
But I will try again as shown in your link. Thank you.
Click to expand...
Click to collapse
You can try this "oneplustoolbox_V5.3_Setup" ...in chinese....from oneplus2 chinese forum
sorry,i can't post the link....sent you the private message
download the link then install...make sure to turn off the antivirus software
the first option is drivers setup...setup both of them
turn on your mobile in TWRP then connect to computer
then you can access the internal storage
copy the ROM in zip style,then flash it

maierbosch said:
I tried adb sideload in twrp. It gives me an error in twrp. In windows I can't connect to the handy via adb. Device can't be found.
But I will try again as shown in your link. Thank you.
Click to expand...
Click to collapse
You can push files to your sd card using adb.
adb should work from twrp.
Go to your system's device manager. Try manually selecting adb driver for the device that shows up with yellow exclamation mark sign.

Hello an a relay big THANK YOU for everyone who broke his head in case of my problem.
http://forum.xda-developers.com/showpost.php?p=63202300&postcount=30
Here I found my solution.
Starting Batch in fastboot mode an now my device is running well.
THANK YOU VERY VERY MUCH!

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.

Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk

I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.

colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk

Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?

No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk

Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.

Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.

colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk

Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.

colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

Erased my phone, need help.

I screwed up. I rooted my phone (oneplus 5) and was in the process of trying some new roms.
Went to install another rom and accidentally hit erase pretty much everything.
I figure no sweat, I'll just copy a rom from my PC onto the phone. No so easy.
Went in recovery (TWRP) The PC see the phone and "internal Storage" but won't allow me to copy anything to the phone, so I can't copy the rom to get back up and running.
Is there a way to flash the rom (zip) in fastboot onto the phone or a way to copy the zip to the phone so I can install it using TRWP?
Thanks.

I've had a mounting issue before, try rebooting to recovery, if that fails again I flashed the stock recovery to format all partitions then re flashed twrp.

blackcell1 said:
I've had a mounting issue before, try rebooting to recovery, if that fails again I flashed the stock recovery to format all partitions then re flashed twrp.
Click to expand...
Click to collapse
I can get into TWRP, but I have no files there (on the phone) to flash. How do I flash from the PC? I have the ROM zip files on the PC.

Click reboot, recovery on twrp and reconnect your phone to your PC and it should mount so you can drag files over

blackcell1 said:
Click reboot, recovery on twrp and reconnect your phone to your PC and it should mount so you can drag files over
Click to expand...
Click to collapse
That is not working and the device is no longer appearing in windows. Add to that, this time when I tried to communicating with it in fastboot, it the PC was reading "waiting for device" and doesn't seem to be communicating with the phone. Ugh.

Format user data in TWRP, reboot back into recovery and then try again.
Or you can run these commands in fastboot:
fastboot erase userdata
fastboot format userdata
Reboot into recovery and see if it works

rickysidhu_ said:
Format user data in TWRP, reboot back into recovery and then try again.
Or you can run these commands in fastboot:
fastboot erase userdata
fastboot format userdata
Reboot into recovery and see if it works
Click to expand...
Click to collapse
It is not.
I erased data in TWRP still will not appear in windows.
I can not connect with fastboot any longer, When in fastboot and trying to connect via the PC (fastboot device) I am getting "waiting for any device" I hope I'm not dead in the water.

noncomjd said:
It is not.
I erased data in TWRP still will not appear in windows.
I can not connect with fastboot any longer, When in fastboot and trying to connect via the PC (fastboot device) I am getting "waiting for any device" I hope I'm not dead in the water.
Click to expand...
Click to collapse
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date

noncomjd said:
I screwed up. I rooted my phone (oneplus 5) and was in the process of trying some new roms.
Went to install another rom and accidentally hit erase pretty much everything.
I figure no sweat, I'll just copy a rom from my PC onto the phone. No so easy.
Went in recovery (TWRP) The PC see the phone and "internal Storage" but won't allow me to copy anything to the phone, so I can't copy the rom to get back up and running.
Is there a way to flash the rom (zip) in fastboot onto the phone or a way to copy the zip to the phone so I can install it using TRWP?
Thanks.
Click to expand...
Click to collapse
If you have the rom on PC but you're enable to copy into device..... maybe ADB sideload? Through TWRP you can also sideload a rom, connecting the phone to pc but only if ADB driver is recognized....
EDIT: if i dont remember wrong you need only to open TWRP>Advanced>ADB Sideload>Swipe to start then connect the phone to pc and the command is adb sideload zipname.zip
Hope i've not forgot something :good:

rickysidhu_ said:
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date
Click to expand...
Click to collapse
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.

rickysidhu_ said:
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date
Click to expand...
Click to collapse
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.

noncomjd said:
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.
Click to expand...
Click to collapse
No problem! We all have 'derp' errors every now and then lol. Glad you got it working!

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.