Database Users

[Defy] Stuck at Bootloader 09.10 - Err:A5,69,4E,00,41

I think the title kinda explains for itself!
From what I started and where I got?
Well, firstly, I tried to install 3.4.3-11 Motorola SBF with fixed Blur provided this link:
"Here you are, buddy
Fixed.SBF plus Nandroid of 3.4.3-11
http://www.multiupload.com/PB10JC9NQV"
(http://forum.xda-developers.com/showthread.php?t=966537&page=7)
I moved to the older PC still running Windows XP to manage RSD Lite 4.9 to work and recognize my Defy. (it apparently worked)
After wiping all data and cache, I started the phone in boot loader mode and tried to use RSD to load the SBF.
Everything seemed to be fine. But.....After RSD finished the update, it said for me to "turn on my Device". Well, it was already on and stuck at Motorola Logo.
I waited for quite some time, took a shower, smoke a cigar.... And, when I came back, nothing, phone was still on moto logo.
I force restarted the phone removing the battery. Still got stuck at moto logo for quite some time.
Sooooo, I decided to wipe everything again and try to install the SBF again, this time with the one provided by "Pays Rom" thread.
That was when stuff got bad.
After that, I got stuck at Bootloader with a "error code" indication.
Alright, it was time to read some more cause I realized I fked something up! Then, I find out I could load a Devtree SBF and that would unbrick the phone being able to install another SBF.
No succecs, eventhoug I tried to load those previous SBF, I still got problems either with RSD Lite or got stuck at bootloader with a that "error code" problem.
As I didnt know what else to do, I loadead back the devtree and got that different error code on the phone. (one mentioned on the thread title).
And, this is pretty much my whole problem! lol
Any Ideas what should I do?
My Defy is from Brazil - Claro and was running 2.1 android at the beggining!
Tyvm!

it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.

oct307 said:
it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.
Click to expand...
Click to collapse
Nothing yet.
Still trying to boot anything in it. If I ever find something, I'll let you know!
I'm getting this error now on RSD Lite when trying to load the SBF 3.4.3-11
Failed Flashing process. Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Adress: 0xB2383000 Command: ADDR (0xE023203F), phone conected
New error code prompted on Bootloarder:
Err:A5,70,39,00,27
Now it shows Motorola logo for a few seccconds.
Stuck at code 39 or smthing while trying to install another SBF (the one with PAys Rom)
Ok, it unstucked, now RSD shows "restarting" and the motorola logo is on screen.
Finally, it loaded.
I used Pays Rom after a few tries with the first fixed SBF and jumping to the Pays Rom SBF.
After sometime, it installed!!!!!
The phone just started!!!!!
How about your problem mate, wich point are u at?

To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.

pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
Thank you!
I managed to find that out by myself, but thanks for the help!!
I noticed it was a not downgradable version, but I don't really care as it fits what I was aiming and I don't have any intetions of going back to 2.1!

pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode

hello,
I also have a similar problem, stuck on the bootloader but I have the "low battery cannot program" error. When I try to charge the battery, the battery appears with a "?" inside...
Does anyone already get this problem ? Battery out of order ? software problem ?

Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk

lanfearxt said:
Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
this is the post: http://forum.xda-developers.com/showthread.php?t=892026&highlight=battery+charge

thanks for the link
it will help me saving my defy....

oct307 said:
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?

try this
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.

slayps said:
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.
Click to expand...
Click to collapse
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files

renatojf said:
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?

neozhu said:
I'm having this same problem.. anyone successfully fixed this?
Click to expand...
Click to collapse
1) Try flashing on different PC to start fresh.
2) If you'd flashed so many sbf. You might not be able to remember them all. My guess is that you might be at froyo state(corrupted/failed system code), thus flashing another Eclair 2.1 sbf would not solve your issue. You must try on Froyo sbf only starting from bootloader mode and rsdlite 4.9 or 5.0.
3) Take note of your battery level as it might draining down while you attempting to put some resuraction on the device.
4) Try relax and take a bath and smoke a bigger cigar just like the OP of this thread did...

i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.

JDM-Bb said:
i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.
Click to expand...
Click to collapse
no signal..? have you try baseband switcher application..?

yes ive try that with no luck.

hELLO
Please, tell me how to solve that problem with bootloader error A5, 70, 39,00 27 in my defy?? You have said you solved it. please help

you need to be calm and cool with lot of patience. It takes upto 10 - 15 Minutes...
the flashing happens at the speed of your computer.
try to use original cables and use USB ports of your desktop motherboard or laptop without any extension cables.
keep your pc in NO SLEEP mode. Batter should be almost full before flashing ...these are some tips...

Bricked, code error, 9.10

I am using Mc Gyvers method to charge my defy.
In the middle of flashing , my phone got switched off and now its bricked
It shows the following through sbf_flash
Data cable ok, battery ok!,
And i m currently on Bl4 .. ive never moved out of froyo sbfs for defy (Nordic beblur)
" >> verifying CG33
usb_bulk_read -110
!! failed
>> verifying CG34
usb_bulk_read -110
!! failed
>> verifying CG35
usb_bulk_write -110
!! failed
>> verifying CG39
usb_bulk_write -110
!! failed
>> verifying CG42
usb_bulk_write -110
!! failed
>> verifying CG45
usb_bulk_write -110
!! failed
>> verifying CG47
usb_bulk_write -110
!! failed
>> verifying CG53
usb_bulk_write -110
!! failed
>> verifying CG61
usb_bulk_write -110
!! failed
>> verifying CG64
usb_bulk_write -110
!! failed
>> verifying CG65
udb_bulk_write-110
Failed!!
Rebooting!
Any solutions?
I ve tried using SEA deblur..Didnt work.

Seen this error in many questions, probably hardware failure is the cause. You can try the bl7 sbf( dfp 231) and also enable the ti omap blank flash option.
Sent from my MB526 using xda premium

thekguy said:
Seen this error in many questions, probably hardware failure is the cause. You can try the bl7 sbf( dfp 231) and also enable the ti omap blank flash option.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
hardware is perfect and battery wont work if i flash bl7 (red lense)

If hardware was perfect, you should not have got those errors. And if you have a green lens, yes camera will work only in cm10 with a bl7 sbf, so you can try a bl6 sbf with ti blank flash option, and then try the bl7 sbf
Sent from my MB526 using xda premium

thekguy said:
If hardware was perfect, you should not have got those errors. And if you have a green lens, yes camera will work only in cm10 with a bl7 sbf, so you can try a bl6 sbf with ti blank flash option, and then try the bl7 sbf
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
i tried eclair builds, checksum for cg31.smg verification failed!
I tried bl5, didnt work (gingerbread builds for defy)
And i tried bl6 and bl7, all gave cg31 checksum error
Only the froyo bl4 of defy doesnt give cg31 checksum error

pjgowtham said:
i tried eclair builds, checksum for cg31.smg verification failed!
I tried bl5, didnt work (gingerbread builds for defy)
i tried bl6 and bl7. All sbfs other than the bl4 froyo gives me cg31 checksum error
Click to expand...
Click to collapse
what shuld i do?

Sorry, but then it's a hardware problem
Sent from my MB526 using xda premium

Im gonno give up defy and move to xperia z. Enough of locked bl s . and i ll really miss u guys.!! Its with defy i learnt the art of romming and mods. Thank you so much guys. i ll be in touch with these forums.

pjgowtham said:
Im gonno give up defy and move to xperia z. Enough of locked bl s . and i ll really miss u guys.!! Its with defy i learnt the art of romming and mods. Thank you so much guys. i ll be in touch with these forums.
Click to expand...
Click to collapse
you can try a fixed sbf after you keep the battery out of the phone for 2-3 hours.

pgreed said:
you can try a fixed sbf after you keep the battery out of the phone for 2-3 hours.
Click to expand...
Click to collapse
I ll try it, thanks
Hey u ve heard of SCout motorola flashing utility which can master reset/master clear phone and will allow us install sbf cleanly...it supports defy and theres some dongle needed i guess..so if anyone has windows 7 ,can u check if the flash just works without the dongle?...it may help millions of bricked defy s
http://www.scoutdongle.com/
and what is this ? https://www.boot-loader.com/

While it's true I'm not aware of how it works, the problem I think lies with the nand chip which cannot be "repaired" that way.
SBF flashing by rsd also "clears" the phone
Sent from my MB526 using xda premium

Your phone is not bricked.Defy cannot be bricked that easily.all the error shows that writing is failed.that's because your usb cable disconnect while the flashing process so it cant write (flash) the sbf. Dont use the method which you mentioned to charge your battery.Get a charger which can charge your battery directly.
Picture of the charger can be seen in the below link.the charge the battery for 3 hours.then flash the correct sbf.if you provide which version of defy you are using i can point out the correct sbf. kindly find the version of defy by checking the lense.Red or green.and dont forget the main thing after flashing the correct sbf you have to wipe data and cache from stock recovery then only you phone will boot or else you will stuck at boot screen.
The charger cost around 100rs.
http://forum.xda-developers.com/showpost.php?p=30085619&postcount=11
Just use rsd lite its enough for flashing.

I flashed cg31 and cg32 only by creating custom sbf. so im getting motorola bootlogo and bootanimation runs in bootloop...
Still cg 33 + are not flashable in my defy

mothy1025 said:
Your phone is not bricked.Defy cannot be bricked that easily.all the error shows that writing is failed.that's because your usb cable disconnect while the flashing process so it cant write (flash) the sbf. Dont use the method which you mentioned to charge your battery.Get a charger which can charge your battery directly.
Picture of the charger can be seen in the below link.the charge the battery for 3 hours.then flash the correct sbf.if you provide which version of defy you are using i can point out the correct sbf. kindly find the version of defy by checking the lense.Red or green.and dont forget the main thing after flashing the correct sbf you have to wipe data and cache from stock recovery then only you phone will boot or else you will stuck at boot screen.
The charger cost around 100rs.
http://forum.xda-developers.com/showpost.php?p=30085619&postcount=11
Just use rsd lite its enough for flashing.
Click to expand...
Click to collapse
Mine is red lense , bl4,froyo (nordic)
ok i ll try a different usb cable
so i tried using a different usb cable.. same result.
and what do you think will be the reason for cg31 checksum error during upgrade!!!???

Checksum error means the data wasn't written successfully
Since you're unable to revive using bl7, it cannot be revived by any other sbf as per what I know
Sent from my MB526 using xda premium

pjgowtham said:
Mine is red lense , bl4,froyo (nordic)
ok i ll try a different usb cable
so i tried using a different usb cable.. same result.
and what do you think will be the reason for cg31 checksum error during upgrade!!!???
Click to expand...
Click to collapse
Kindly try flashing this sbf http://sbf.droid-developers.org/umt...JRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz.let it boot it will stuck at boot animation(boot loop).Remove the battery and replace it then press power button and volume down key at the same time after 2 sec you will see Android with a triangle and exclamation mark now release the keys and press both volume up and down at the same time you will enter stock recovery now wipe data and cache and reboot the system wait for 10min it will boot.Kindly charge your battery by the method i said then try do not try kick start method it will spoil your device.Check your pm.

any progress

mothy1025 said:
any progress
Click to expand...
Click to collapse
I have downloaded the above said bl7 firmware.. i tried it
This time it was weird.
As usual cg 31 verification failed,
cg32 passed
cg33 (It said expected error)
cg34 (passed!!!) WEIRD!
and i bought that universal charger for 60rs..its perfect and easier than mcgyver

So it's working?
Sent from my MB526 using xda premium

thekguy said:
So it's working?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Nope.not working..!
Now cg34 checksum verification failed...( in all sbf flashes)

[Bricked] How to unbrick Droid 2 A953

Hello people.
My problem is the following:
The phone was working, but it was too much slow, so that was almost impossible to access its menu.
Tried reseting it, but after reseting it all the apps and the slowdowns stays the same.
So I tried flashing this file, from a video on youtube:
1 º 1FF-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_DR4-51-120117-release-keys-signed-Verizon-US.sbf
Didn't work, it says my phone doesn't support the file.
2º MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_USXMILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf (2.3.4 brazilian retail)
Bricked the phone. RSD Lite says " Phone [0000] Error veryfing Code Group 35 checksums. File 0x1A13 . Phone 0x8ACA.
3º M2L_U6_4.5.2_51-27_SIGNED_US1MILA2GBRETBRB125LA001.0R_STABLE45LAMILETRETBR_P007_A019_M001_HWp2a_Service1FF.sbf (2.3.6 brazilian retail)
Same error on RSD Lite. Now phone turns up on BL saiying
"70.12
Code corrupt
... ... ..."
Is there any way to restore it?
While I wait a response I'll try ezSBF.
Thank for your time.

you have a 70.12 bootloader, that is a Milestone 2 bootloader
only use Milestone 2 (A953) firmware see http://sbf.droid-developers.org/phone.php?device=29
make sure you verify md5 check sum https://sites.google.com/site/sdshadowscollection/home/hash-checksums
use RSD Lite 5.6 or newer

sd_shadow said:
you have a 70.12 bootloader, that is a Milestone 2 bootloader
only use Milestone 2 (A953) firmware see http://sbf.droid-developers.org/phone.php?device=29
make sure you verify md5 check sum https://sites.google.com/site/sdshadowscollection/home/hash-checksums
use RSD Lite 5.6 or newer
Click to expand...
Click to collapse
Thank you, I did what you told and haven't got results. Anyway, I discovered phone has damaged touchscreen and its useless now (at least it stay cool over my desk when using the dock , no matter)

MB526 Slim-mb526-4.4.2.build.3-UNOFFICIAL-20140215-2305 DEAD for no reason?! HELP

On its Defy installed the following files listed below. One day, for unknown reasons, the phone turned off , after restarting all the settings were gone , I decided to install the latest Slim- mb526 - 4.4.2.build.3.85 - UNOFFICIAL - 20140323 -0023 but encountered a problem with the wipe . I decided to use it again DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF but have failed to complete the installation. I have also tried other SBF but nothing helps . Please advice , the phone after inserting the battery shows a message Code Corrupt , Battery ok
PLEASE HELP ANYONE
I can not find any solution on the web, already sifted through forums and websites . I'm afraid I can not help yourself in saving my phone without your help . Please interest. I will answer any of your questions , I really like this phone , I do not want to lose him !
I'm using the latest rsd lite 6.1.6 . The phone is unlocked. I no longer have warranty.
Files installed on your phone:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF
Slim- mb526 - 4.4.2.build.3 - UNOFFICIAL - 20140215 - 2305
minimal_Slim_AIO_gapps.4.4.2.build.3
Framaroot - 1.9.1
SndInitDefy_2.3
defy_twrp_recovery_2.6.3.0

If you get code corrupt with dfp 231, then it unfortunately would imply eMMC issues, because it cannot happen in theory. Although i have never seen anyone fix this error, you can try with the ti blank flash option enabled
Sent from my MB526 using Tapatalk

Is RSD recognizing your phone?

Yes RSD show my phone and flashing then give me replay "error verifying code group 33 checksums...."
Where I can find the ti blank flash option?

keny1992 said:
Yes RSD show my phone and flashing then give me replay "error verifying code group 33 checksums...."
Where I can find the ti blank flash option?
Click to expand...
Click to collapse
Try stock 231 sbf without root included.

Can You give me full name of this rom? I don't want to get a mistake...

Anyone else have some ideas?

keny1992 said:
Anyone else have some ideas?
Click to expand...
Click to collapse
I don't think anything else can be done. You can still try different SBFs from - http://sbf.droid-developers.org/phone.php?device=28 (try retail Taiwanese).

Nokia 6 T-1000 official rom desperately needed

Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?

aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/

kanakarkku said:
Try download the file from below. Follow the steps.
Click to expand...
Click to collapse
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.

aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.

nokia stuck in recovery mode
aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
aNorthernSoul said:
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.
Click to expand...
Click to collapse
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do

kafeel3186 said:
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do
Click to expand...
Click to collapse
I am still trying to figure it out. Based on where you live, you might be able to contact Nokia via online chat and they could direct you to a service centre to flash the phone. They don't have any in Canada though.
I am trying to get the legit firmware but I am not sure if it is the one I have or the modified one my phone came with causing me to be able to unsuccessfully install it.
How did yours wind up in that state?

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Just a side note, I am able to sideload the update via the PC. It quits at 54% (failed to read command * no error) after showing those same parse errors on the screen though. Weirdly, then it reboots with a differently styled logo screen and tried (and fails) to update. Then the logo screen is normal again.

Just in case anyone is wondering, I spoke to the seller I purchased from on Amazon. Whether advertised or not, most China suppliers are installing a custom ROM on all China variants of the Nokia 6. When buying from a more local third party, you have no access to this ROM. I just bought this phone last week and knew about the update from Nokia so had confirmed with them that it currently didn't support Google Services. I didn't want a custom rom.
I have asked for either the rom installed or the official firmware that should have came with the phone and a means to install it or I will take action with Amazon tomorrow. I don't really want to return the phone, I'd likely wait for someone to release an official rom but I could barely afford this phone as it was and it is currently useless.
I just wanted to warn anyone else thinking about buying the Chinese model.

kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I had the same result after method 1 via sd

Quixote78 said:
I had the same result after method 1 via sd
Click to expand...
Click to collapse
And after method 2 via ADB)))
As result device stuck in bootloop mode.
I've managed to bring it back with MiFlash only.

kanakarkku said:
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
Click to expand...
Click to collapse
IMO the file that you download is to update the existing working ROM and the op has somehow ended up with one that doesn't work. So I think he would need the entire ROM the exact version that he last had to get back into the phone and then update.