Hi
I'm using Windows 7 64 bit, flashtool version 0.6.9.1
Here is my device info before the tragedy D:
ROM : Gin2JB (i forget the version)
Kernel : Lupus kernel (again forget the version)
I don't know what happen but my phone won't turned on D: when i press the power button it's vibrating, it even can go to the flashmode and fastboot mode, but it just wont show anything on screen D: is it my screen or what?
i already try to turn it on and wait for a while, so the phone can load and I try to call my own number but i can't, it's not connected D:
i think it's a little strange because it's happening when i'm reading a Visual Novel via VNDS, then i decided to take a break, and put the screen off by pressing the power button, then i try to turn it on again, usually when i try to turn on the screen again, it's lagging a little and the screen turned on normally , but the this time only the sound playing and *pop* the phone turned off completely! and then i try to turn on the phone but it won't D: i pull out the battery and turn it on again, and still it won't turned on D:
I even try to flash a .ftf file R800i_4.0.2.A.0.42_Generic.ftf (Here is the MD5 in case i flash a broken .ftf MD5 : 317FCA41566A2FE8331B670087DB015F)
after flashing i try to turn it on again but no luck D:
And if i try to pull out the battery and turn it on like normal and wait for a while (So if it's really the screen problem maybe it's load up to normal state) then try to plug it to the computer (Note : The memory card is not detected), the flashtool log show like this :
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
INFO - Device disconnected <--- I'm not unpluging my phone but it's disconnected automatically! and windows keep installing a new driver for MTP USB Device! right after the install for new driver fail, the "Device disconnected" message show up then it's connected automatically again and then it's doing same thing again and again D:
So any suggestion or idea what happen to my phone? D: is it really the screen? or the software? or anything else maybe??? if you need more info regarding my problem i'll be happy to tell you
sorry if my English is baaad :silly: not my mother tongue~~~
harunakaze said:
Hi
I'm using Windows 7 64 bit, flashtool version 0.6.9.1
Here is my device info before the tragedy D:
ROM : Gin2JB (i forget the version)
Kernel : Lupus kernel (again forget the version)
I don't know what happen but my phone won't turned on D: when i press the power button it's vibrating, it even can go to the flashmode and fastboot mode, but it just wont show anything on screen D: is it my screen or what?
i already try to turn it on and wait for a while, so the phone can load and I try to call my own number but i can't, it's not connected D:
i think it's a little strange because it's happening when i'm reading a Visual Novel via VNDS, then i decided to take a break, and put the screen off by pressing the power button, then i try to turn it on again, usually when i try to turn on the screen again, it's lagging a little and the screen turned on normally , but the this time only the sound playing and *pop* the phone turned off completely! and then i try to turn on the phone but it won't D: i pull out the battery and turn it on again, and still it won't turned on D:
I even try to flash a .ftf file R800i_4.0.2.A.0.42_Generic.ftf (Here is the MD5 in case i flash a broken .ftf MD5 : 317FCA41566A2FE8331B670087DB015F)
after flashing i try to turn it on again but no luck D:
And if i try to pull out the battery and turn it on like normal and wait for a while (So if it's really the screen problem maybe it's load up to normal state) then try to plug it to the computer (Note : The memory card is not detected), the flashtool log show like this :
INFO - Device connected with USB debugging off
INFO - For 2011 devices line, be sure you are not in MTP mode
INFO - Device disconnected <--- I'm not unpluging my phone but it's disconnected automatically! and windows keep installing a new driver for MTP USB Device! right after the install for new driver fail, the "Device disconnected" message show up then it's connected automatically again and then it's doing same thing again and again D:
So any suggestion or idea what happen to my phone? D: is it really the screen? or the software? or anything else maybe??? if you need more info regarding my problem i'll be happy to tell you
sorry if my English is baaad :silly: not my mother tongue~~~
Click to expand...
Click to collapse
Ok, as i understand it, you used to have gin2JB rom with Lupus kernel when you got black screen, then you flashed stock firmware.
Stock firmware don't have usb debbuging enabled by default and that is why you are getting "Device connected with USB debugging off"
You could try to update flashtool to see will that solve device disconnection problem.
Also, try different usb cable and even different usb port at motherboard (including back ports)
PC companion should work even with USB debugging disabled. If he recognize devise normaly, it is most likely hardware error. And maybe it's even flex slider cable fault (because it's weakest part of xPlay)
You try to open and close gamepad (and even some middle positions, when it's not even open or closed) when powering on. If you see screen working even for few seconds, then it's most likely damaged flex.
Ofcourse, maybe screen is dead, but chanse for that is lower (but not impossible)
Hi
Thanks for the reply, now i'm positive it's an hardware failure D: because i try to flash LuPuS_zeus_Stock-gB+iCsv7-full.img, and turn it on, and wait for a while, and *boom* pc companion detect my phone, well i don't know i should be happy or not D: (i'm still hoping it's a software failure though )
well i think the screen is dead, i try the "middle position" method but it wont work D:
well now any suggestion how to fix it?
I have another question though how can i use my android as modem (tethering) without configuring anything via phone (because it's half dead now), any info would be nice
As for flex cable, check out this thread from CriGiu about similar problem (to lazy to type it again ). It is not hard but you need special screwdriver
As for tethering, things can be little tricky. You need only to select tethering options in menu I know, with black screen it can be tricky
There is a way to see what is in phone but it is also... tricky
There is program for PC that can show what is on screen of phone, but it needs usb debugging enabled. Stock firmware don't have it enabled but most of custom roms have it. You "only" need to flash custom rom
Without working screen, it can be hard to install custom rom from recovery, but not impossible. I have an idea, you can try it if you want:
-download file in attachment and unpack it in some folder in PC
-download some recent GB or ICS custom rom frox XDA (for Play, ofcorse)
-make folder named "A1" on sdcard and place your rom into that folder (i guess you still can do that, most probably with pc companion if sd card is not mounted already)
-flash lupus ics/gb v7 kernel (skip if it's already flashed)
-power on phone in fastboot mode (or stay in it if you just flashed kernel)
-from unpacked folder double-click on file named "start.bat". It will erase all system and data on phone (but not sd card)
-disconnect and power on phone
-now, since it's lupus kernel, and since system is erased, it will boot directly to cwm recovery
-wait about 30sec or minute to make sure it is in recovery (since you can't see anything, we are guessing here)
-press menu button once (that should select "install zip" from recovery menu)
-press home button 4 (four) times (or maybe 5 or 6 , just in case ). Luckily, it will flash rom from first folder in sdcard (and that's why name "A1" for folder - use capital letter, it does matter)
-wait 5 minutes for rom to be flashed (just in case) and reboot (battery off/on)
-wait 10minutes rom to boot (maybe less, depends on rom)
-from attachment folder start file named "droidAtScreen-1.0.1.cmd" on pc (i do hope you have java installed on pc)
-if all goess well, you should see on PC screenshots of phone
-use dpad buttons to navigate to tethering options (and make sure to disable lockscreen - in case touchscreen is not working). If your touchscreen is working, it's flex cable 99% faulty :fingers-crossed:
If it doesn't work, you can flash stock firmware back so you can use pc companion
As i said, tricky, but not impossible :laugh:
Good luck :fingers-crossed:
Related
so my phone r800i xperia play i tried to get cm9 aqnd when it told me to fastboot
reboot the device to cwm it didnt turn on and when i press on button it just makes a buzz and it connects to my comp it like 1 min and the red light flickers while its pluged in to my computer using usb then it pops up unkown device plugged in your pc.then fails to install it help fastboot and flash mode wont turn on.
i asked my cousin who worked with these problems he says you have to do some complex thing on your computer. Any other way i might send it to sony.
it keeps poping up that it cannot recognize my usb plugged in .
Try downloading and running the update service:
http://sony-ericsson-update-service.en.uptodown.com
This should flash your phone back to default (stock) ROM I believe. It worked for me when I deleted /system
Flashtool is much better that SEUS in my opinion. Much more flexible.
When my Play would be rebooting constantly I:
1. Connected it to pc, Let it recognize my device
2. Before it would reboot again, I took the battery out.
3. Entered fastboot mode
4. Flashed new firmware
Hi guys, so my problem is I was installing a new rom on my rooted D855. everything was going along fine but then the process stalled. I left it running for 15 - 20 minutes but it was still on 33%. I tried holding the power button in desperation which shut the thing down. Now when I try to factory reset it goes to the prompt screen, I answer yes, then it asks me to confirm. from there however it goes to LG splash screen and eventually a black screen with Fastboot mode started. -reset- portcharge -reset- portcharge fastboot: processing commands in the top left corner. That's it.. If I try download mode it goes to the download screen and then to the black screen as described above.
Sounds pretty ordinary but if there is an answer out there I am sure one of you guys will know it.
TIA
i had some similar other issue and the only way i got out of it, is by using the lg flashtool 2014 and the KDZ file appropriate to your version
there is a thread with a step by step instructions.
you launch the flashtool, then insert the kdz file (original stock rom) then you put your phone into download mode (making sure in windows/controlpanel/devicemanager/ports - comp port 41 for the device driver)
you press volume up and plug it into the pc, the pc sees the phone and it starts reflashing the custom rom to your cell.
i presume that as soon as your download mode is working by flashing whatever command is corrupt and makes your phone black should be bypassed by then
i hope it helps - look for the thread how to flash the lg
Thanks I'll give it a shot. Not sure device manager is seeing it properly. I'll have a play and see. Thanks again for the reply
O.K here's the thing, my phone is seen in device manager as a Samsung Android Phone. Under the details tab it shows it connected via USB Modem Phone ADB Port. There is no option to change the port to 41. Anybody who can help I would be very grateful......
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
Hello all,
I was on ICS 4.04 custom ROM with unlocked bootloader, and my ON/OFF button was failing since several days. In one of that times that I switched off the phone, I could not switch it ON anymore. I had not installed any thing (app, ROM, etc) before the problem. I bought a new ON/OFF module (3 € :cyclops: ) and the problem still goes on.
SIMPTOMS:
If I try to turn it ON, it really works (brivates and the retro ilumination works fine) but I only get a black screen (no logo and sound). If I connect the phone to PC it is recognized. I can go into flash/fastboot mode (green/blue led), I can charge it (red/green led).
If I tyry to switch it off normally trough the on/off button, it does not response (I can not turn it off in this way, only taking off the battery). The white lights in the 2 lower buttons reamins always on if I press the home button, so I can now that the pnone had not turned off.
If I try to go into recovery I can not do it (not purple light), the screen remains black with the retro ilumination working fine
WHAT I HAVE DONE
- to buy a new ON/OFF module that work fine (I think...)
- As I can go into flash/fastboot mode, I have installed several new stock roms with flashtool (GB, ICS) and several kernels without result
- I have checked all the internal conections in the PCB and screen, all seem to be right
- I have tried to go into the phone trough adb, but as I have installed stock roms, I have not enabled the debug mode in the phone, so I can not connect with it. I have searched the web, but I have not been able to find a method to enable the debug mode in the phone
- I have locked/unlocked the bootloader several times
- take off the batery a whole night and to try it again
I am thinking in a problem with the screen, but it was working fine just before to turn it off before the problem. The problem is that I do not want to spend the money for a new screen without to know if the problem is in the PCB :silly:
The more strange thing is that I can not to turn it off normally through the on/off boton , it seems that the phone has gone into a loop internally when you turn it on.
Some ideas?... Thanks in advance
You have the problem that your phone doesn't boot, the problems lies within your kernel,
first of all to fix it, use flashtool and search for a stock firmware for your arc, don't know if you got a lt15i?(Xperia Arc) or lt18i (Xperia Arc S).
This will fix your booting problem...
Make sure your bootloader is unlocked, make sure you follow the ROM-instructions step-by-step when you install one, because this is the reason you failed installing your custom kernel.
Some instructions on how to install a custom rom =>
Step 1. Gather information about YOUR phone. (write down your phone type, your kernel version, your baseband version etc....)
Step 2. On your phone go the your Settings>About Phone> Build Number and press this about 7 times, you'll notice the notification of becoming 'developer', then go back to settings>developer settings (above About Phone) and scroll to whenever you find USB-Debugging, make it active
Step 3. Install ADB and fastboot drivers for your phone
Step 4. Unlock your bootloader
Step 5. Find and download a compatible ROM ( Make sure your phone type is listed as working ... ) and install recovery on your phone.
Step 6. Open up the ROM zip-file and look for the kernel (Boot.img) inside of the ROM and extract it OR Download a kernel which is supported by the downloaded ROM
Step 7. Copy your Kernel image (boot.img) to the ADB Driver map (not necessary but alot easier to work this way) and copy your ROM-zipfile to your SD or Internal Memory.
Step 8. Open up a (Command) Terminal and use the 'cd'-command to explore to your map with adb drivers
Step 9. Connect your phone with your computer and type in the terminal-window: adb reboot fastboot
Step 10. You'll notice your LED changing to blue when it worked. Then type in fastboot flash boot boot.img
Whenever this step has worked you'll have flashed a custom kernel on your phone....
Step 11. Then you got to boot into recovery using Power + Volume Down
Step 12. In recovery do a Full Wipe, and install your ROM (+ Gapps whenever you need google play store.)
You now have a custom ROM and kernel installed!
many thanks MrMaddTraxx. That is not my problem, but your answer will be very usefull for me in the future :good:
Definetively I think that the problem is that the screen is broken. My main problem was that I have not enabled the USB debugging in my mobile and I could not make any important change on it.
Finally I got to enable USB debugging as I show in this post:
http://forum.xda-developers.com/showpost.php?p=61792353&postcount=204
Once I have USB debugging, I could enable the screen with this wanderfull app:
http://forum.xda-developers.com/showthread.php?t=2786395
I could control my phone as the touch screen works OK. I have been able too to connect it to my TV through HDMI, seeing my mobile in it too.
So the only thing to do is to buy a neww screen. I would like to ask you if you believe really that the problem is in the screen (as the backlight and touch screen work fine) or in the connections for the screen in the PCB
thanks
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.