Database Users

Can't update/flash bootloader after using nVflash

Hi!
Yesterday followed AndroidRoot.mobi's guide how to backup the blobs and important files, it went successfully. But now I am stuck with the 4.13 bootloader and I want to update to 4.23. I've tried several methods without any results.
I've tried to flash an unmodified version of the 4.13, flash a factory image that comes with the 4.13 also been trying wugs toolkit. The error I get is "BadParameters".
Does anyone know what I should do to update the bootloader to 4.23?

Flash with fastboot, if it doesn't work then be sure to post all input/output from cmd/terminal here

demkantor said:
Flash with fastboot, if it doesn't work then be sure to post all input/output from cmd/terminal here
Click to expand...
Click to collapse
I have tried to flash via fast boot, but it doesn't work. I will post a screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So you have a working tablet, but want to update bootloader right? Do you have WiFi only n7? Can you check something else as well, run this
fastboot getvar all

demkantor said:
So you have a working tablet, but want to update bootloader right? Do you have WiFi only n7? Can you check something else as well, run this
fastboot getvar all
Click to expand...
Click to collapse
Yep, the tablet works fine (Stock 5.1.1), but it annoys me that it seems to be impossible to update the bootloader.
Yes, it is an Wifi only 32GB.
Here is the output from fastboot getvar all
Edit
Doesn't it look a bit strange that the partition-size:bootloader is blank?
I also tried to flash the bootloader from an another computer and got the same result as above but I noticed that in the upper-left corner there is a text "signature match"

Yeah this is what I was afraid of, not a huge issue, especially as you have the backed up blobs from nv flash
I've seen this from time to time where device works and boots but there is an issue with bootloader partition, normally when this happens in another partition like /cache you would just reformat and be on your way but you don't want to reformat bootloader, its a risky thing to do
I would suggest to be safe and make a copy of those nv flash blobs and keep it all safe, if an issue arises you can use that back up
As for fixing completely I can't say for sure, possible restoring backup now will do it, but I can't say for sure
As of now I would just stick with what you have unless you are in dire need of lollipop

demkantor said:
Yeah this is what I was afraid of, not a huge issue, especially as you have the backed up blobs from nv flash
I've seen this from time to time where device works and boots but there is an issue with bootloader partition, normally when this happens in another partition like /cache you would just reformat and be on your way but you don't want to reformat bootloader, its a risky thing to do
I would suggest to be safe and make a copy of those nv flash blobs and keep it all safe, if an issue arises you can use that back up
As for fixing completely I can't say for sure, possible restoring backup now will do it, but I can't say for sure
As of now I would just stick with what you have unless you are in dire need of lollipop
Click to expand...
Click to collapse
Okey, but do you have a link to a guide that shows how to reformat the bootloader partition? I don't use the nexus that much anyway, at the moment I see it as a fun project. I have the blobs in three different locations so they are my backup.
Btw, I got an nandroid backup, if that could help?

Nandroid won't have the bootloader backed up so no there, as for a guide to reformat the bootloader I doubt you will find one as typically this is a bad idea
You may be able to reformat and run e2fsck through adb like you would with other partitions but adb may not allow just as fastboot won't allow reformating this partition.
That would leave UART or JTAG which will require special a special cable and software, you can Google around a bit and see what's out there.
As for now I would just attempt to restore blobs and hope that does the trick
Best of luck!

Thread closed

Install CM14 for OnePlus X (The Unofficial)
** How to Install TWRP for the 3.1.0 version you installed Oxygen.
B1: Starting Fastboot mode by turning off the power on. Then hold down + to the source.
Step 2: Install the driver and connect to the computer (HD drivers installed on the network to find it)
B3: Run cmd (run -> cmd) command fastboot boot attachments and enter this download Mod edit link removed
B4: boot into TWRP Self.
** The Stock 2.2.2 ROM you are using the network attempt to open up the OEM and then down Flashfy unbootloader install TWRP on CM ROMs directly or similar 13 and then into TWRP always offline.
** Note: Back up your data before doing us avoid errors arising restore offline.
** Download ROM CM 14: Mod edit link removed
** Link Download Grapps:Mod edit link removed
** Conducted into TWRP and wipe data, cache partitioning, Dalvik Cache. Flash ROM + Grapps and restart.
This is an experiment with me what errors arise not responsible. For those you love to dabble and discourage those you do not know and do not understand anything. People are already getting a bit bored Android does not dabble to dabble like new. : D
Path: Mod edit link removed
Vietnamses : Mod edit link removed

downloading, will report back soon.

Cam on
Thanks much

Post some screenshots.

failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too

Well, this is interesting.. The step-by-step guide is a bit confusing though. I will download and try the 'ol good method of flashing ROM, gapps and supersu. Hope it works!

namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app

be_are said:
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
here you go: https://drive.google.com/file/d/0B_Km0FbYnea1aDdIaTEydElhUkk/view?usp=sharing

twrp has not made it to 3 ox you have to use a downgrade to get a fresh start using unbrick method, (keep flashable backup via flashify) get twrp installed with the new (old) boot loader, flash cm14+ext. and you are done.
if you had cm13 or the likes, please confirm if you CAN upgrade to 14 before ox people start trying to install without knowing if it even has android 6 (last update i saw on the branch was from june 7 so idk)
teamwin does not have twrp for the ox 3 on oneplus x yet (on their releases anyway) so you have to follow some other process to downgrade to a twrp'able os (and a backup) before trying yo install this
if i see any info from people who have been able to update (and if it has android 7) i'll try to make a video on the process (in white, Texan english)

Please remove this page.

namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.

ksigit said:
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
Click to expand...
Click to collapse
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

namquang93 said:
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
Click to expand...
Click to collapse
Looks like a successful install to me. Could you provide twrp logs?

With whose permission did you post this build here ? Don't you think there was a reason that even after a complete build of CM14 it was still not posted to the forums ?
I am asking you, as politely as possible, to remove the links and this fake procedure, when N is ready, it will be shared, you might find phony builds or legit but non working ones on the interweebz, that doesn't mean it gives you the right to share it just because you think its cool, because its not.
Take it down.
EDIT: Sure, if you build yourself and want to share it then you're more than welcome.

And then they will cry if things are broken !! Take it down folk !
Sent from my ONE E1003 using XDA-Developers mobile app

This Build was just a test build, what made u think that i will not post it here on xda if the rom booted? We, the team are working to make it work but yeah dont post the builds from afh here, will update u all for sure when its done. I think it was my mistake to not to make that build private. -_-

It flashes successfully but doesn't boot, goes back into recovery. Still, great work.

congrats for succesfull starter build
hats off !!!!! to you guys ([/B]developers off this rom) :good:

Flashed with/without gapps. Doesn't boot - goes back 2 recovery

foster095 said:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
Click to expand...
Click to collapse
Kindly refer to the developer's post, POST #16

CAN-L01 Cust Failed

hi,
I have a problem with my huawei nova:
i wanted to root my huawei so i flashed the update supersu , and when i restart my phone i have a bootloop....
So, i wanted to do a wipe cache but it gives me :
"Failed to mount 'cust' (Invalid argument)"
But i can no find any cust.img or update.app that want to work because when i want to update my huawei with a update.app (with a recovery stock obviously), the load is only up to 5% and it gives me an error...
1 week that my huawe still does not work...

But before you had flashed twrp?

merlin21 said:
But before you had flashed twrp?
Click to expand...
Click to collapse
yes obviously....

What version phone you have, and wich software you're on?

Reflash TWRP and restore your nandroid backup.

merlin21 said:
What version phone you have, and wich software you're on?
Click to expand...
Click to collapse
I have the Huawei Nova CAN-L01 but i don't no more... And the Software is CAN-L01 C432V100

Michiel0912 said:
Reflash TWRP and restore your nandroid backup.
Click to expand...
Click to collapse
I already flashed TWRP and i not have a backup....

With me the same error in the recovery menu. I hope there is a solution to solve the problem. My mobile is dead: (, I forgot to make a backup and with the CAN-L11 backup I can unfortunately not start anything because against the conclusion at 99% restoration the following message: "Failed to mount 'cust' (Invalid argument)"
Already several attempts made recovery to flash again.
Please help

Try this;
https://mega.nz/#!B5BxmSQC!p-uVxctJxukBtO7oqW9SdTIaQ0x0dIIBeDXIHLI4ML4

Thanks, / cust I now can fix this, but it failed on the wipen the internal memory. It is successful done, but when I look back then into the recovery are the files like / superuser there, I have played the wrong SuperSU and thus my mobile phone can not start after Restore Backup, because this SuperSU does not remove the bootloop remove.
What am I doing wrong? What can I do for my mobile phone to work again and finally start normally?
Please ask for more help

TCoreXxx said:
Thanks, / cust I now can fix this, but it failed on the wipen the internal memory. It is successful done, but when I look back then into the recovery are the files like / superuser there, I have played the wrong SuperSU and thus my mobile phone can not start after Restore Backup, because this SuperSU does not remove the bootloop remove.
What am I doing wrong? What can I do for my mobile phone to work again and finally start normally?
Please ask for more help
Click to expand...
Click to collapse
You only made a backup after you installed the wrong SU?

The problem is I have the backup from here in the forum taken, the CAN-L11 and have this successfully flashing, with your help (/ cust). But the other problem is simple I can not wipe anything and erase in the recovery because I had before all the problems, the superuser had installed, another source and since bootloop.
This binary I can now however no longer delete, so my mobile phone normally starts after successful flashing of the CAN-L11.
Recovery shows that it is deleted successfully, but as soon as I reboot into the recovery are all deleted files again there, thus also superuser.
I'm desperate
How can I delete and reset everything, so that my mobile works again?

You are mounting the partitions w/r when you wipe?

Yes I did, but why does not it work?

I'm still desperate, it simply does not work, mount and superuser remains, after delete.
Please, who has a suitable step by step guide which I can still make?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Supersu must be hiding somewhere else also, allowing it to come back. Try browsing around and see if you can find any other files associated with Supersu. Also, I would check the official Supersu thread, I believe they have an uninstall zip that should work and/or can probably guide you on what you need to do.
See if this works:
https://forum.xda-developers.com/showpost.php?p=69461377&postcount=470

View attachment 4030838
Thanks, but unfortunately still the same problem
The international memory remains immediately after wipen, etc
Superuser simply does not want to disappear, it can not make my cell phone anymore.

What exactly did you flash? I am guessing you flashed system again and it still was the same? Maybe someone can give you a zip of system to flash, that should erase it.
I would also suggest again heading to the official superSU thread and asking about your problem.

TCoreXxx said:
View attachment 4030838
Thanks, but unfortunately still the same problem
The international memory remains immediately after wipen, etc
Superuser simply does not want to disappear, it can not make my cell phone anymore.
Click to expand...
Click to collapse
I recognized the same problem. And i figured out. I can delete only one file at one time and then must go back and reboot recovery again when deleting files from system partition.
@Xelfmade perhaps you can check this?
---------- Post added at 07:29 AM ---------- Previous post was at 07:27 AM ----------
wangdaning said:
What exactly did you flash? I am guessing you flashed system again and it still was the same? Maybe someone can give you a zip of system to flash, that should erase it.
I would also suggest again heading to the official superSU thread and asking about your problem.
Click to expand...
Click to collapse
exactly that was what i did... Flash via fastboot

What should I now flash over fastboot?
Can one of you make an order as I tackle the whole problem?
Mobile still does not work and there are always errors that can not be written at once / Data, though mount.
Please really help, my mobile phone is totally broken with the software.
It's no fun just to go back and forth between Recovery and Fastboot.
Please provide instructions and help.

[Recoveries]TWRP Recovery For Meizu M2 Mini

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Requirements
Root+Bootloader Unlocked
Flashing Instructions
After Unlocking Bootloader (If you dont know how to do it then go here)
[url]https://forum.xda-developers.com/meizu-m2-mini/how-to/guide-unlock-bootloaderinstall-twrp-t3390799[/URL]
Enter In fastboot.Then type.
"fastboot flash recovery recovery.img"
wait a minute turn off the phone. and enter recovery (Power + vol up until vibration)you'll Be in TWRP
Download Links
Old Recovery Version 2.8
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlMXd3YzJhTnUxeVU[/URL]
Mid Recovery 3.10 Latest
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlYnpCaXhSOUxjX0E[/URL]
New Recovery 3.1.1
[url]https://drive.google.com/file/d/0Bz6Fq2POoJTlRjh4ZkppWUJ4Qm8/view?usp=drivesdk[/URL]
Latest Recovery 3.2.1
[url]https://drive.google.com/file/d/1ftYtD2Tm0MdKBv_ZtVQHGJEcCuflb6Oe/view?usp=drivesdk[/URL]
Don't Forget To Press Thanks if you like it :good: :good:
Regards~
Murtaza Piplod

what's news bro?

ADIB27 said:
what's news bro?
Click to expand...
Click to collapse
updated with latest features of the latest recovery released by TWRP read changelogs at there TWRP site

heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.

maxisgsm said:
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
Click to expand...
Click to collapse
Try clear dalvik and cache.

adarshm4you said:
Try clear dalvik and cache.
Click to expand...
Click to collapse
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......

maxisgsm said:
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
Click to expand...
Click to collapse
I think there will be some mess in installed os reflash it after taking a backup.

adarshm4you said:
I think there will be some mess in installed os reflash it after taking a backup.
Click to expand...
Click to collapse
my phone hang while i do a format storage.

maxisgsm said:
my phone hang while i do a format storage.
Click to expand...
Click to collapse
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.

adarshm4you said:
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
Click to expand...
Click to collapse
every time the phone boot into twrp, it only go back to last state and keep fail then reboot...... it will cycle until battery die. i cannot go anywhere in twrp .....
now i at fastboot state, when i try to flash stock rom, it gave me the error
G:\adbFire>fastboot flash update update_8.zip
sending 'update' (1115283 KB)...
OKAY [ 88.153s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 88.237s

Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:

adarshm4you said:
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
Click to expand...
Click to collapse
adb cannot detect my devices ..... if i not mistake, last time i unlcock my OnePlus one without any problem, and adb can detect my phone,
now cannot detect ....

@murtaza1326
TWRP 3.2.1.0 is out!
Update the post

rushiranpise said:
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
Click to expand...
Click to collapse
post updated new latest 3.2.1 TWRP is added @Dinolek TWRP is alread there in his post so I don't think i should repost it here ??
Regards~

how to recovery install meizu m2 mini flyme 6.2.0.0g

thanks sir.. i wanna install this twrp

Pretty good!

Stuck at fastboot and can't flash rom via flash tool (sparcecrclist error)

Hey ppl
I'm not rlly new to all of this flashing..but this is getting really annoying and this is probably not achievable for me right now.
Xiaomi Devices are relatively new to me at this point
Yesterday, I wanted to Update my Mi 9t to Miui 12.5 via an official Rom.
The flash worked well but the version I flashed seemed buggy, so I wanted to revert via Flash tool.
Something went wrong and now I'm stuck at fastboot without any image, system or data whatsoever -.-
mi flash tool simply refused to work and bricked my phone..for whatever reason.
Now when I want to flash a Official stable Global Rom with Mi flash tool, I get this Error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"error: "Flash sparcecrclist error"
some kind of CRC error?
I tried to reload SEVERAL Global, EU and even China Roms to see, if it's just a corrputed download. Nope.
- I tried everything from moving the folder to simply C:/ and flashing from there.
- tried another computer and even my laptop.
- Tried several fastboot roms
etc
- XiaomiToolV2 gave me the same error.
- Also tried to flash each .img manually via fastboot commands
Has anyone an Idea what to do?
I'm gettitn rlly frustrated now
greetings
Edit:
The Image shows CLEAN ALL AND LOCK, But it's just for the sake of the picture I took of the error.
I allways used CLEAN ALL...The Bootloader is still unlocked!

The path to is maybe to long. Make like c:/rom

joke19 said:
The path to is maybe to long. Make like c:/rom
Click to expand...
Click to collapse
As you can read in my Post, I allready tried.

Aj4x3192 said:
As you can read in my Post, I allready tried.
Click to expand...
Click to collapse
Sorry I read over.
Maybe this thread have an answer for u.
MI 9T soft bricked, how to go back to Global Stable
After install to EU dev. 9.7.18 NO recovery more and no access to the System, only bootloop, just Soft bricked my phone. So I decided to install into fastboot mode the global stable 10.3.6 tgz and modified the anti rollback error. here the rom...
forum.xda-developers.com

joke19 said:
Sorry I read over.
Maybe this thread have an answer for u.
MI 9T soft bricked, how to go back to Global Stable
After install to EU dev. 9.7.18 NO recovery more and no access to the System, only bootloop, just Soft bricked my phone. So I decided to install into fastboot mode the global stable 10.3.6 tgz and modified the anti rollback error. here the rom...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much man!
The Anti Rollback Security was the culprit...can't believe it... I thought I edited the script accordingly ^^
After I edited the Flash bat correctly, I was able to flash THIS TWRP only and managed to delety my Data partition so I could decrypt the Phone.
Data is gone anyway..so thats fine
I'm now running CRDroid 11!
Thanks again!
greetings!

What edit you made in that file because i was having same crclist error in mi flash tool so
I flashed twrp through fastboot and then flashed the recovery rom through it.