Database Develop

[Q] adb error -- can´t flash cmw recovery

Hello,
I just bought my Xperia Z and I am loving it. However, I have a little problem.
My phone is rooted, unlocked bootloader but I am trying to flash CWM recovery using ADB to flash custom ROMS but I cannot. I use ADB and I even type: fileboot devices to check that my phone is well recognized and it is just fine. ( I have USB debugging ticked).
I type: fastboot flash boot and then I drag and drop the file: Z_DooMLoRD_AdvStkKernel_FW-434_v3 and it says:
sending ´boot´ (9892 kb)...
OKAY [0.620 s]
writing ´boot´...
FAILED (remote: Command not allowed)
finished. total time: 0.620s
Any ideas?

Try to flash doomkernel v06?it has both Cwm and twrp..
Sent from my Xperia Z
---------- Post added at 11:11 AM ---------- Previous post was at 11:07 AM ----------
arielito said:
Hello,
I just bought my Xperia Z and I am loving it. However, I have a little problem.
My phone is rooted, unlocked bootloader but I am trying to flash CWM recovery using ADB to flash custom ROMS but I cannot. I use ADB and I even type: fileboot devices to check that my phone is well recognized and it is just fine. ( I have USB debugging ticked).
I type: fastboot flash boot and then I drag and drop the file: Z_DooMLoRD_AdvStkKernel_FW-434_v3 and it says:
sending ´boot´ (9892 kb)...
OKAY [0.620 s]
writing ´boot´...
FAILED (remote: Command not allowed)
finished. total time: 0.620s
Any ideas?
Click to expand...
Click to collapse
And btw did you leave a space after boot? fastboot flash boot boot.img
Sent from my Xperia Z

joejoe23 said:
Try to flash doomkernel v06?it has both Cwm and twrp..
Sent from my Xperia Z
---------- Post added at 11:11 AM ---------- Previous post was at 11:07 AM ----------
And btw did you leave a space after boot? fastboot flash boot boot.img
Sent from my Xperia Z
Click to expand...
Click to collapse
Thank you. I tried the kernel you suggested but it´s the same
Regarding the space, yes, I leave it and then drag and drop. This is frustating. I really want to try custom roms, undervolting, etc. Please any more suggestions?

Drag and drop? AFAIK ADB only works from the command line. You have to specify the file to flash.
"fastboot flash boot boot.img"

Thank you everyone. I finally did it. It turned out that I thought I had the bootloader unlocked but it was just POSSIBLE to unlocked. OH GOSH!!! I unlocked it and flash my CWM recovery without problems. Thanks again for your help! How can I change this to solved?

Are you using windows 8.
if so activate the unsigned driver installation..

variable not found error

I have moto x dev ed, I just unlock the bootloader. i tried to install this custom recovery i keep getting this.
<bootloader> variable not supported!
target reported max download size of 805306368 bytes
etc etc...
im trying to download the twrp custom recovery
i dont why it keeps doing that

I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?

Groid said:
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Click to expand...
Click to collapse
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo

Fastboot the recovery.img then type fastboot reboot and choose recovery in fastboot menu

dat010man said:
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Click to expand...
Click to collapse
Sounds like it did not flash correctly because the laying down android leads to the stock recovery. I would try redownloading twrp for ghost again and make sure that is in the folder with fastboot and verify your getting the file name correct when flashing. Just repeating the steps all the through may be successful, we all miss a step occasionally. Good luck [emoji106]
Edit: p.s. I did read somewhere that some people had issue with recovery not sticking after flashing. They got around this by typing the command fastboot reboot bootloader right after flashing the recovery. After that custom recovery would stick.

I'm still getting the same error. Am I suppose to hold the volume up button until the recovery loads?

If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?

Travisdroidx2 said:
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Click to expand...
Click to collapse
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?

dat010man said:
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
Click to expand...
Click to collapse
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?

Travisdroidx2 said:
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Click to expand...
Click to collapse
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash

dat010man said:
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
Click to expand...
Click to collapse
Shouldn't have to rename it but sounds like you got it working. Great.

Travisdroidx2 said:
Shouldn't have to rename it but sounds like you got it working. Great.
Click to expand...
Click to collapse
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application

dat010man said:
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
Click to expand...
Click to collapse
I thought you said when you renamed it that it worked? So still no?

Travisdroidx2 said:
I thought you said when you renamed it that it worked? So still no?
Click to expand...
Click to collapse
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it

dat010man said:
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
Click to expand...
Click to collapse
Put the twrp.img file in your SDK folder with your fastboot.exe files. Not on your device.
Is USB debugging turned on?
If so in download mode when you type fastboot devices do you see your device?
If so you just shift right click and open command prompt from that folder you have the files in on your PC.
Then fastboot flash recovery "name of file". IMG
After that volume down to recovery and then volume up to enter twrp.

Just to be clear, you are using the command:
fastboot flash recovery twrp-2.8.4.0-ghost.img (assuming twrp-2.8.4.0.img is the recovery file) and you have copied 'SuperSU-v2.46.zip' into the root of internal memory (called sdcard). After flashing the recovery, you should definitely not boot directly to the system. You should issue the command fastboot reboot-bootloader. Then, choose recovery from the menu and up arrow to start it. I can't remember the exact order of things, but somewhere along the way twrp will prompt you about the supersu and near the end it will ask about making changes so the stock recovery isn't applied back over twrp. Let it make the changes. When you do boot into the system you should have root.

[Q] Recovery partition not found

It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks

sambastrakan said:
It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
Click to expand...
Click to collapse
I am guessing the reason you are running CM11 LBL is due to the restriction imposed by a locked bootloader and not because you are choosing to miss out on all the Lollipop fun. If that's the case, I don't think you can flash a recovery via fastboot the same way you can with an UBL. You said it yourself that you have tried flashing recoveries multiple times w/o success. As far as I know, your bootloader needs to be unlocked for flashing via fastboot commands.
On the other hand if your bootloader's unlockable or you relocked it sometime in the past and forgot about it, I suppose unlocking it would do the trick. Just in case you don't know, dial up *#*#7378423#*#* and see if its unlockable.
Also what is your current recovery? I am guessing it one that came with the kernel you are using and not something you flashed separately?
Btw did you flash Williams kernel separately or did it come with the ROM? If you did flash it separately then how did you do it? Also you mentioned you flashed a kernel - did you mean via fastboot or something else like FlashTool?

No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks

sambastrakan said:
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
Click to expand...
Click to collapse
Since your bootloader's unlocked and your phone's probably rooted, why don't you use Rashr to flash the file? It will replace the recovery you have right now (cyanogenmod recovery?) with the one you wanna flash.
Note: This recovery stays even when you flash new ROMs so if want something else you will have to reflash via Rashr or flash stock firmware kernel with FlashTool.
Also if you switch to Lollipop, you can have dual recoveries if you follow the instructions on the Tangerine kernel thread.
http://forum.xda-developers.com/xperia-sp/orig-development/kernel-tangerine-kernel-v1-t3073297
Edit: What recovery do you have with Williams kernel right now?

Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.

akashsaini7 said:
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
Click to expand...
Click to collapse
It is very possible ...
Thx

Useful
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.

kojata said:
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
Click to expand...
Click to collapse
thank you. i will have a look.

facing the same problem.. did u manage to fix it yet?

l2azoredge said:
facing the same problem.. did u manage to fix it yet?
Click to expand...
Click to collapse
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.

sambastrakan said:
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
Click to expand...
Click to collapse
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?

l2azoredge said:
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
Click to expand...
Click to collapse
I don't think so. what kernel are you using ? Seems your kernel ignore recovery partition....

Having the same problem after upgrading to CM 13. Any solution would be appreciated.
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
Click to expand...
Click to collapse
Thank god this nasty hack did the trick. However I placed my recovery.img inside the /system, so my command was 2- using command: dd if=/system/recovery.img of=/dev/block/mmcblk0p11

Try to flash with minimal adb fastboot.
If not,try this method: flash your recovery as boot(fastboot flash boot recovery.img), see if it works,then flash your kernel again.

Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said

IiroP said:
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
Click to expand...
Click to collapse
Has someone tried it already? I am afraid after installing the recovery in the boot partition and something goes wrong, that then the phone will be bricked.
Might it be the afore mentioned Kernel issue? My Xperisa XP has the kernel: 3.4.0-perf-g4c8352f-00783-gce6e17b
Thx for replies.
[EDIT]
Installing TWRP in boot partition worked fine. Let us see how it works with an Update.

The same problem
I have the same problem. Maybe Sony didn't create a recovery partition on this Phone, I unlocked it in 2016 and now i don't remember how i did this.
I only can flash boot, but afeter install system from twrp or cwm, this recovery disappear so i can't install gapps.

My experience with "Partition Not Found" is:
1.- Install Stock Rom, later of install Root
2.- Install TWRP with CMD (But the 2.8 high version, (On the internet there is a version of CMD that only makes one click and ready) Note* i Update to 3.0.1, later of install 2.8 version.
(Now update to device to Android 7, or 6, or 5)
3.- Install Rom + Gapps + Root (Note* Install Root because later u need install TWRP App)
4.- After of install rom, install TWRP App, Download and Flash Image TWRP (in the same app) on device
5.- Finally check u TWRP if all install is correct.
Saludos!
Actually i have Android 7 (Candy Rom + Fusion Kernel) with TWRP y everything is fine!

After flash zip via twrp BRICKED

Hi I need help,
1. I used "Huawei update etractor" to create fleshable zip from official ROM (boot.img, system.img, cache,img, cust.img, userdata.img)
2. I flashed this zip via TWRP
3. after reboot is phone in BOOTLOOP and recovery(volume + and powerbutton ) dont work and ADB dont work too,
4. BOOTLOADER is UNLOCKED still
5. fastboot is working BUT I tried flash (boot.img and recovery.img) from many ROMs this is unsucessfully
Exist some solution for me?
I have HUAWEI ASCEND P7-L10

Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work

RangerP7 said:
Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work
Click to expand...
Click to collapse
THX for answer.
I cannot enter to twrp after flashed.
How can I wipe everything when I have available only fastboot.?
I don't know previously version. I tried flash images via fastboot several ROMS - without successfully.
Problem is in flash ROM version only ? really? If is it true I will be flash all rom order by version

Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work

RangerP7 said:
Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work
Click to expand...
Click to collapse
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
C:\adb>fastboot erase boot
erasing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
i cannot enter to twrp.
After flash previously instaled version rom ->> it is Without progress ->> Phone is in bootloop still

soki.niva said:
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
Click to expand...
Click to collapse
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp

RangerP7 said:
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp
Click to expand...
Click to collapse
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)

Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133

RangerP7 said:
Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133
Click to expand...
Click to collapse
B129 is Vodafone version and worked without bootloop.
do you have any idea?

soki.niva said:
B129 is Vodafone version and worked without bootloop.
do you have any idea?
Click to expand...
Click to collapse
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...

RangerP7 said:
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...
Click to expand...
Click to collapse
I read other post, problem was made :
I created fleshable zip(via huawei extractor), BUT with bad profile(ASCEND P6 profile) because profile for P7 is missing.
Is it any solution for me?

Could you flash the images via fastboot?

RangerP7 said:
Could you flash the images via fastboot?
Click to expand...
Click to collapse
It appears that is working.
Commands of type: fastboot flash boot boot.img - are finised without error.

And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?

RangerP7 said:
And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?
Click to expand...
Click to collapse
I flashed all images (boot,recovery, cache, cust, userdata, and system)
No, I don't know 3 buttons method. What is it ? hold volume up volume down and power button. without changes...
Please I need name of partition for ASCEND P7 -> Do you know? for example : What is number of partition is for recovery partition="/dev/block/mmcblk0pXX" ...?
<File type="recovery" partition="/dev/block/mmcblk0p11">recovery.img</File>
<File type="boot" partition="/dev/block/mmcblk0p12">.boot.img</File>
<File type="system" partition="/dev/block/mmcblk0p16">system.img</File>
<File type="cache" partition="/dev/block/mmcblk0p17">cache.img</File>
<File type="cust" partition="/dev/block/mmcblk0p18">cust.img</File>
<File type="userdata" partition="/dev/block/mmcblk0p19">userdata.img</File>

The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your external storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry

soki.niva said:
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)
Click to expand...
Click to collapse
Step 3 is wrong. You cannot flash official Huawei ROMs via custom recovery, even if they've been made bootable by Huawei Update Extractor.
What you need to do is use Update Extractor again to extract RECOVERY.IMG of the ROM that is currently installed on your phone. Then flash it with following command:
fastboot flash recovery RECOVERY.IMG
If that's not sufficient you can try the same thing with BOOT.IMG | SYSTEM.IMG | CUST.IMG
---------- Post added at 04:26 AM ---------- Previous post was at 04:21 AM ----------
RangerP7 said:
The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your internal storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry
Click to expand...
Click to collapse
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.

Milan-XDA said:
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.
Click to expand...
Click to collapse
Sorry my fault... Of cause the external storage
Thank you

RangerP7 said:
Sorry my fault... Of cause the external storage
Thank you
Click to expand...
Click to collapse
I tried but no results... why not solution not work(not exists?)when fastboot menu still works?

What exactly is not working? I (we) cannot help you with no information?

Stuck in TWRP

So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help

It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?

Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too

If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.

AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.

Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.

ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.

AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update

ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.

AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!

ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical