Database Develop

Unable to Reflash via LG Flash Tool

Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock ROM.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
Came back to it after a few weeks and issue has been resolved. Despite error warnings fastboot operated correctly, only manually. Any script etc. that booted device into fastboot would never find the device. Simple as flashing recovery and restoring a backup.
tl;dr: I'm not very bright.

FiniteDGk said:
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock KDZ.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
EDIT: Forgot to include that I see the proper devices in device manager.
EDIT 2: Device is properly configured and can be found in ADB when powered on.
Click to expand...
Click to collapse
where u able to fix it? i currently have no recovery or OS it just stays at the LG screen i can only get into Download mode i tried to flash a kdz but it cant read my phone....it turns on but thats it i cant got past the LG screen and when i connect my phone now i get different device drivers than before like LGE AndroidNet USB Serial Port and USB Modem....idk what to do

ZUK Brick... (totally)

The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me

gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
EDIT: Sorry, I post on the wrong section. If someone can move this post on the right section ...

gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
try to use QPST (Qfil) method. This is final method can bring back your phone. If fail, congratulation ! :silly:

I success with QFIL Zui works but it's awful
Unfortunately, I try to install stock cos but I have the same issue.... Bootloop after "App update message".
I don't know why

Try flashing Cyanogen Os using fastboot

I did that...
I flash with the tool via fastboot. But bootloop result...
I also tried to flash CM13 via TWRP but I have an error message...
Do you have any other solutions?

I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice

Here u go, QFIL CM 12 ROM: https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8

So with the ham version is the same as the QFIL version?

gaara19 said:
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Click to expand...
Click to collapse
READ THIS( use google translate)
BTW, what are the fastboot commands that you are using?

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!

I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?

It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).

First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.

I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.

Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0

xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.

YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.

Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.

Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice

Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen

xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.

Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You

Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.

Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.

Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks

Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.

Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.

Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.

Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.

[HELP] Looking for last (or any) ota update.zip for D415

Hi everybody
I need to find an update.zip to flash it on stock recovery and attempt to repair the phone system.
Long story short..
I restore my D415 (previously with Lineage 14.1) to stock firmware (KK) via KDZ file and LG flash tool, then update it to LP with LG Mobile Support Tool and everything was good, then i tried to root the device with the LG OneClick Root (which i used several times before to root my phone without problems) but i don't know what happened during the batch process and now Download Mode has been replaced with Fastboot mode and the device hangs on the T-Mobile startup screen, so i can't flash a KDZ file again to restore the phone without a Downlaod Mode. The fastboot mode throws "remote: unknown command" with every command i tried (except fastboot getvar all; which shows "unlocked: no") even reboot doesn't work.
Tried everything even booting on Qualcomm Qdload mode (shorting the phone with test points) to reflash the firmware files but couldn't succeed because QFIL, QPST Software Downloader and BoardDiag they all threw errors.
I can access the stock recovery mode by pressing home button when the "erasing" screen appears after selecting "yes" on factory reset menu, so i need an official update to try to fix this phone, don't know if its gonna work or if this is a hardware issue but at least i want to try. Buying a new one is very difficult for me right now.
Thanks for any help.

Sony Xperia 1 mrk ii [XQ-AT51] soft bricked after FW change with newflasher

I could really use a bit of help.
I wanted to root my phone (Nordic edition of XQ-AT51). I went to XperiFirm (5.4.0) and found the most possible fit, being Customized EU 58.0.3.132 / R14A.
I tried Flashtool64 (0.9.31.0) but it got stuck on Device connected in flashmode, and nothing happened for 10 minutes.
Went in here and found a nice guide suggesting Newflasher. successfully-flashed-customization-t4119707
Downloaded it (version 36) , following the guide for removing any .ta files, and then moved Newflasher to same dir as the downloaded firmware, ran it as administrator answered
n,n,n,y and everything went without visible error (and quite fast)
Case is, now my phone is stuck in an endless reboot loop - first it complains about the unlocked bootloader, then showing the Sony logo for a few seconds, and then restarting.
I can break it by going into Flashmode, but thats about it.
Any good suggestion on how to move forward from here ?

Try reflashing again. What ta files did you remove, exactly? You should have only removed the simlock.ta, and do a full wipe (don't preserve userdata). Also, how did you unlock the bootloader beforehand? Via cmd, and did you toggle "enable oem unlock" in dev options?

iArvee said:
Try reflashing again. What ta files did you remove, exactly? You should have only removed the simlock.ta, and do a full wipe (don't preserve userdata). Also, how did you unlock the bootloader beforehand? Via cmd, and did you toggle "enable oem unlock" in dev options?
Click to expand...
Click to collapse
Thank you for the feedback !
I unlocked the bootloader using fastboot (and entered the key generated by the sony webpage) - and prior to that enabled USB debugging and OEM Unlock within dev options.
Then I did what in retrospect might be the rootcause for the misery. I followed a guide for rooting the phone (the purpose of unlocking the bootloader alltogether) but failed to realize that the boot file I was after should likely match the excact SW the phone is running (which isn't available on XperiFirm) - so I used Magisk with the file to generate a patched version on the phone, and then I used fastboot to install the patched loader. Following that the phone started to complain about Corrupt Software (in a somewhat similar endless boot loop).
So - in order to get the SW on the boot on the same page, I re-downloaded the full FW to get that on the phone.
First I tried using the Flashtool (updated drivers and stuff) but as mentioned that one got stuck, I've seen other users in here getting stuck at the same, and found this guide suggesting using Newflasher, removed all .ta files, following the guide saying that was the golden nugget and went into it (all going fine, probably not the best thing in retrospect to have said yes to removing the persistent part?)
I have downloaded the firmware again, and this time only removed the simlock.ta as suggested. Loaded that, again with newflasher, including wiping the persistent part (as it'd been done before anyway), but the result is sadly the same, phone starts to complain about the unlocked bootloader (which is fine obviously) and the for a brief second shows the Sony logo before it restarts. Only options to change that pattern are the vol up or vol down following a USB to PC connection.
I could try a different software, but the available set is quite limited.
Oh, and should it be relevant somehow, to get it back to life, I do have another phone which I haven't touched with the right software.

please rollback boot loader to lock and try flash by newflasher again