Related
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
Xperia 1 goes on boot loop after flashing the ROM.
What happened.
>Flashed Xperia 1 using new flasher.
>Device started and while setup went on boot loop with a message"Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds."
I tried to repair using Xperia Companion but it won't stay to the Flashmode. It goes on loop with the message.
Used original cable and things.
But the device goes to fastboot mode if I press volume up during plugging.
Flashtool and new flasher cannot since the device won't go to flashmode while volume down and plugging.
What can I do further? Please help.
Does the phone turn on again after it automatically turns off?
What region did you flash btw?
It turns on and off automatically in two of the cases.
1. Connected to the PC.
2. Connected to the charger.
But stays in Fastboot mode connected to PC.
I was getting bootlops after flashing rom (locked bootloader, wanted to change region), using both newflasher and flashtool. In my case the problem was i had to wipe/format reset when flashing with flashtool, otherwise got a bootloop.
Once phone is booting, force a shutdown with volume + and power at the same time, then hold volume - and connect to pc, then use flashtool.
snake218 said:
I was getting bootlops after flashing rom (locked bootloader, wanted to change region), using both newflasher and flashtool. In my case the problem was i had to wipe/format reset when flashing with flashtool, otherwise got a bootloop.
Once phone is booting, force a shutdown with volume + and power at the same time, then hold volume - and connect to pc, then use flashtool.
Click to expand...
Click to collapse
Yes, I tried that way but the problem is it won't stay in Flashmode. It shows that warning and goes to bootloop.
I still can see the light turns green while doing so but cannot hold.
Same with me, recover using pc companion and use good cable..
The problem i have because using bad cable
blegs said:
Same with me, recover using pc companion and use good cable..
The problem i have because using bad cable
Click to expand...
Click to collapse
Thanks!
My phone doesn't stay in flashmode.
It only stay without loop and message in Fastboot mode.
Else would have flashed already!!
Yes my phone always said my phone not trusted..
I tried using newflashe always failed.
But after chae the cable and recovery from pc companion now its work
I agree, it might be PC problem (drivers) or cable definitelly. Try diferent cable and diferent pc, go to someone with PC and try with his cable
munjeni said:
I agree, it might be PC problem (drivers) or cable definitelly. Try diferent cable and diferent pc, go to someone with PC and try with his cable
Click to expand...
Click to collapse
Thank you but the thing doesn't work.
I tried on Windows 7 PC ;
Installed Xperia Companion and Xperia one driver and yet again it booted into fastbootmode but not flashmode.
I used USB C-C cable, and then another sony phone cable but it didn't work.
I even tried a short cable of a battery bank.
Thats strange. Can you write in details what you have flashed and what you have skipped? Did you done something with your trim area?
Hi @munjeni
I unluckily flashed new device J8110. It was a new firmware for device named Sphinx or something similar which isn't released yet.
It was to be j9110 actually. I then flashed the firmware through new flasher. I flashed everything. Then device booted and during setup steps it rebooted. Then I knew the device was different.
I tried flashing J 9110 but then the device started showing the mesaage.
Why don't you reflash trought fastboot? Boot an recovery image with fastboot:
fastboot boot recovery.img
you will need to unlock bootloader to be able to do that. Trought recovery and adb to recovery you can do many things e.g. flash an custom rom... etc, just for idea.
I have thought of it but loosing drm keys was reason.
jeoleo7 said:
I have thought of it but loosing drm keys was reason.
Click to expand...
Click to collapse
Doesn't matter anyway as you need access to the phone to toggle OEM unlock before unlocking bootloader
So..
What should I be doing?
jeoleo7 said:
I have thought of it but loosing drm keys was reason.
Click to expand...
Click to collapse
But do you have choice? Did you tried?
fastboot erase userdata
Usedata sometimes cause boot loop and message on screen about corruption. Another thing which I curently thinking about, is your battery charged? Maybe empty battery don't allow you to get into flash mode.
munjeni said:
But do you have choice? Did you tried?
fastboot erase userdata
Usedata sometimes cause boot loop and message on screen about corruption. Another thing which I curently thinking about, is your battery charged? Maybe empty battery don't allow you to get into flash mode.
Click to expand...
Click to collapse
I'm not sure. It was more than 50% when I did everything.
Not sure now.
Will it charge in fastboot mode?
I don't own device to be able to tell you. Seems you are not only one who have problem with flashmode, here https://forum.xda-developers.com/z3/xperia-z3v-general/bricked-sony-z3v-access-fastboot-t3510214 . Did you tried to erase userdata trought fastboot? I'm believing you will need to unlock bootloader first because you have no choice with locked bootloader because everything you try going to give you "command not allowed". Unlock bootloader, install an recovery, trought recovery you can reflash broken things, e.g. reguest from somebody with same device to give you raw partitions dump (excluding trim area, system, data, cache) and use DD command to reflash it on your phone, remember do not touch trim area, its on first partition! Good luck!
munjeni said:
I don't own device to be able to tell you. Seems you are not only one who have problem with flashmode, here https://forum.xda-developers.com/z3/xperia-z3v-general/bricked-sony-z3v-access-fastboot-t3510214 . Did you tried to erase userdata trought fastboot? I'm believing you will need to unlock bootloader first because you have no choice with locked bootloader because everything you try going to give you "command not allowed". Unlock bootloader, install an recovery, trought recovery you can reflash broken things, e.g. reguest from somebody with same device to give you raw partitions dump (excluding trim area, system, data, cache) and use DD command to reflash it on your phone, remember do not touch trim area, its on first partition! Good luck!
Click to expand...
Click to collapse
That link is 3 years old....
Without access to the phone there will be no access to the OEM unlock. Without that I don't think the bootloader can be unlocked.
It's hard to properly brick a sony phone with flashmode. With previous ones a different PC with different cables etc has worked
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
GiantMurloc said:
I accidentally flashed the wrong logo.img and now my phone does not boot anymore, its just a black screen
idk if there is a way to write the phone without booting it, if someone got an idea what I could do, please help me :'(
Click to expand...
Click to collapse
can you boot into fast boot mode
muneeb rizwan said:
can you boot into fast boot mode
Click to expand...
Click to collapse
nope, the screen stays black and it doesn't even vibrate anymore
GiantMurloc said:
nope, the screen stays black and it doesn't even vibrate anymore
Click to expand...
Click to collapse
does your computer detects it
muneeb rizwan said:
does your computer detects it
Click to expand...
Click to collapse
the device list in linux stays the same when i plug or unplug it, so I think its not detected by the pc
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
StaryMuz said:
It would be better if you told us exactly what you did. Step by step. Then we can more easily assess how serious the error may have been.
Click to expand...
Click to collapse
so, I broke my system img today, the phone was in a bootloop and I downloaded the system img and boot img from c.mi.com, then I found out that there is actually a logo.img for the splashscreen and tried to create my own, I thought it would be alright if I flash it and I could get back to fastboot if its not working. well seems like that was wrong, now the phone is not booting anymore :'(
I there any way to the phone before it tried to start the logo.img?
On my old lenovo tablet there was a software called mtk tool that was able to flash the device before it starts anything
so I found out that I could try to boot my phone into the edl mode, so I can flash it with mi flash tool, but I would need to remove the phone cover for that, so it would be my last option, any other idea?
The question is whether the phone doesn't actually report anything when connected to a PC. In Windows detection is easy, how it is verifiable in Linux I have no idea. The phone can report to different kinds of drivers, including the COM port. EDL mode can be triggered by test points from the phone's motherboard, but sometimes also by button combinations. I don't know of a suitable button combination yet, but it is used from the off state of the phone when the phone is connected to a PC.
As for the tablet connection you mentioned, it was definitely an MTK CPU and it has different procedures to upload than Qualcomm. With us, you have to connect the phone first.
So I tried it on my windows and it also didn't show up in device manager. Anyway I will buy a phone repair kid and try to fix it in the EDL mode, thank you ^^