Database Info

Tested method to repair bricked Honor 6

Some time ago I bought a Honor 6 bricked by a firmware upgrade.
I done some reading, I asked friends but I couldn't fix it. I opened a topic here and many people tried to help me. Nothing worked... I contacted some experienced people from this, and a Romanian forum, but no success. I was trying to fix it for 2 months now.
Eventually, I came across a solution made by DC-Unlocker Team.
I bought some credits to be able to run the solution and with a few mouse clicks my phone was repaired. Now it works perfectly. I do have some questions to ask about several issues in Honor 6, but let me describe how I fixed my phone with this solution.
I would like to underline that I am in no way related to the DC-unlocker Team.
The software can repair most of the Honor firmware problems:
Bricked phones, bootloop, stuck in fastboot mode
It can write full firmware update.app in fastboot mode
Can flash phones with locked bootloader or FRP. (No need to get the bootloader unlock code)
The whole procedure is detailed here, but let me describe the steps which I took. I also attach few screenshots of the process.
1. Make sure, that you install Huawei Hisuite (for drivers), or Universal ADB driver.
2 Enter fastboot mode on the phone and connect it to your computer. Remove the SD card if there is one installed in the phone.
3. Check if computer detects the phone is fastboot mode, run fastboot devices command
4. The firmware repair process will need 15 credits (which will cost 15 euro). You can buy the credits here
Credits are deducted immediately, but you can flash the same phone any time you want for 72 hours.
5. After you buy the credits, download the software client here
Supported models and features here
6. Start the program. It will ask your credentials for the DC-unlocker server. You receive those credentials when you buy the first time credits.
7. In the DC Phoenix software, select fastboot mode, select "App files" tab.
8. Carefully chose the update.app for recovery. Be careful, not to flash a different hardware variant (in a H60-L12 flash only H60-L12 firmware and so on). Not doing so will probably break your phone forever. The program does not check compatibility, nor the phone in this mode.
9. Open the update app by clicking right end of the line "Update file".
10 Click "Update". Program will unpack the update.app and will start to flash all the chosen img packs.
Here I got really scared, because first write was unscuccessful, I got this message: "PTABLE partition UPDATE ... FAILED
I thought that I threw away my money. But program managed really well: "Activating Backdoor: DONE"
After this step, everything went well: "Writing device finished OK"
11. Power cycle your phone. It should start normally.
12. On the dc-unlocker site they say: "Then you need to repeat flashing, but now in upgrade mode". I did not ran this step. I made a full factory reset and started OTA upgrades. Phone is now version: EMUI4.0.1_H-60-L12_6.11.1.
It has Android 6, EMUI 4.0.1.
At one moment I thought that is better to go back to a previous version and flashed an older tested firmware, it worked without any problems..
Although my experience is limited to this phone only, I recommend this solution. Please feel free to ask, I will try to answer any questions.

So the software deactivates itself after 72h?

zinko_pt said:
So the software deactivates itself after 72h?
Click to expand...
Click to collapse
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.

janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
But is there any refund in case it doesn't work?

zinko_pt said:
But is there any refund in case it doesn't work?
Click to expand...
Click to collapse
No, there are no refunds, but if you have a phone with only firmware error and you chose the right firmware, there are big chances that the program will recover your phone.
But if security damaged, you will need factory file.
method 2 can help in 99% cases, but only if there 100% compatible file.
They have only H60-L04 factory file.
Repairing by this method, will erase phone security data (simlock, IMEI and other numbers)
You will lose all numbers!, IMEI will be 0000000000000000
You can repair missing numbers with third party software, like HCU client
You can use DC-unlocker credits on HCU client, software will require 8 credits for repair service.

Thanks. When there's no other solution it might be handy.

i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?

Split74 said:
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Click to expand...
Click to collapse
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos

janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
U shouldn't need to do this to flash back to stock. Sounds like a scam

Tmobilefan906 said:
U shouldn't need to do this to flash back to stock. Sounds like a scam
Click to expand...
Click to collapse
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.

janos666 said:
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
Click to expand...
Click to collapse
It was my OPINION dude. Didn't mean to offend.

Tmobilefan906 said:
It was my OPINION dude. Didn't mean to offend.
Click to expand...
Click to collapse
Yep, the SW works OK ..
First it extracts the IMG files from the UPDATE.APP - same as Huawei Update Extractor. Then it flashes all IMG files (+-) using fastboot - but here is the catch.. it uses an undocumented feature of fastboot:
fastboot.exe oem backdoor get
And then generates the necessary unlock file/sequence which it then feeds to the phone using:
fastboot.exe flash slock XXX_Unlockcode.bin
So indeed it does work - I've used it, you can go between EMUI3.1 and 4.0/0.1 no problem - if we knew how to generate the unlock file for the "backdoor" - we would be all set However we don't and the generated file changes with every "oem backdoor get" request..
But 15EUR seems almost reasonable for this (I'd prefer 10EUR hehe) - otherwise, we would need to use parted and dd the necessary partitions which is more dangerous and we don't have a large enough community of users to dump the necessary partitions..

janos666 said:
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
Click to expand...
Click to collapse
It worked! Fail on normal flash the It issued that damn BACKDOOR install and now i'm back!
Got only 2 "problems":
1. I got 2 IMEI CODES
2.I can't see all my internal storage:
I tried a wipe internal storage + factory reset with emui rec and with twrp, but nothing. TWRP say something like: Can't wipe ..data/... No such directory
Inviato dal mio PE-UL00 utilizzando Tapatalk

I will think about this issue, but a quick idea is: you could try a full firmware update from SD card with the 3 button method and a factory restore after.

Happy to hear that buddy... I threw away a honor 6 about two months ago, was stuck in fastboot for more than a month, if had it, I am sure, this would have fixed it.:crying:

Another Honor 6 saved with this method, this time a H60-L02

I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app

I can confirm i fix my Honor 6 hard brick with Dc Phoenix
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Lukalion said:
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It was impossible for my L02 to be fixed using unbrick fuction of multi tool

You did not do the step i said in Edit
Sent from my H60-L04 using XDA-Developers Legacy app

Stuck in ERROR MODE

I already wrote something like this in a similar thread, but for another device (read the device name wrong), so I thought i should post it in the right place.
I have been playing too much with stuff that i probably shouldn't have been so hasty about. So i have finally arrived here on the ERROR MODE (with unstoppable boot loop), which looks exactly like the bootloader only it says ERROR MODE instead of whatever, where i can't get into any other type of recovery or fastboot mode, no matter what button combinations i do. I previously could get to the fastboot mode, but i was still stuck so..... I made the very wise choice of relocking (since i hadn't tried that) my device, and now I can't even access fastboot (nothing. tried every button combination i can think of). So I am sitting here wondering if this is the end of the journey with my... relatively new phone... So, yes. No way of accessing anything and my phone is in a reboot loop i can't stop. Only thing is the error code i get "ERROR!":
"Func NO : 16 (lpm3 image)"
"Error NO : 1 (security verify failed!)"
Is there hope? or no?
Also noticed the light flashes green 3 times then red 1, then continues this pattern. Idk if that's useful or not.

Here's a pic.
It doesn't seem to have fastboot connection here, either.

OP were you ever able to fix this issue?

@Kimuchuu its not clear from OP had you relocked your bootloader if yes then you cant modify your system you need to have unlocked bootloader inorder to perform system modifications.

Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.

You can be really happy that they sent you a new one, but it's not a unique case, in CZ there were few people who had same or similar issue and Repair service gave them new phone too.

Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
You got lucky they sent you a new one considering that you messed up the previous one. Take good care this time.
Sent from my Honor 8 using XDA Labs

Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
thats nice to hear ,man you are lucky

How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.

oberfeldwedler said:
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
Click to expand...
Click to collapse
In which country do you live? Just go to the nearest authorized Huawei service center. You can find them in Google.
Sent from my Honor 8 using XDA Labs

I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!

BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
A guide how you solved your problem would help others who screwed their device to solve their problem

Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
But your bootloader wasn't locked i guess...

oberfeldwedler said:
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
Click to expand...
Click to collapse
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs

adriansticoid said:
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.

oberfeldwedler said:
No success
Click to expand...
Click to collapse
Then dload is your next choice.
Sent from my Honor 8 using XDA Labs

oberfeldwedler said:
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
Click to expand...
Click to collapse
Recovery is the one which installs ota updates . Erecovery is an emergency recovery. It can help u restore ur phone to previous version by flashing full original firmware

I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLOADER

oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
Well , great that unbricked and your last line , it is to be in bold . Thanks for it. Headsup:victory:

oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
yup thats the main point if you are not fully stock and soft bricked you are not advised to lock your bootloader. Once you locked your bootloader you can no more modify your system.

Bricked Honor 8 FRD L19

Hello guys, I'm so sorry for having to bug you all eventhough there already has been many threats regarding a bricked Honor 8.
But however, i'm really stuck because apparently my Honor 8 model is FRD-L19C636 B380 currently running emui 5.0
This phone was bought in Malaysia. Due to my retardness, i tried rooting this phone but accidently wiped the entire system with my backup of twrp.
This phone is unlocked, its having stock recovery now, phone works as in, there are many apps missing and theres no keyboard and camera does not work.
I seem to have downloaded the update.app for the latest version but it does not include CUST.IMG which then doesnt allow me to fully flash the rom.
When I'm thinking about downgrading, it didnt work either because i cannot find the correct version for the downgrade. (I randomly picked a FRD L19 emui 4.1 from the website and flash it, it failed at CUST.IMG and further bricked my device but now its back to the state where theres no keyboard and apps are missing)
Bootloader is unlocked
I can access fastboot and stock recovery. Please I really need help D: I would never want to mess with my phone ever again, my mom bought me this phone and it was hard for her, I feel really bad for not taking care of it properly.

Rommco05 said:
Hi, your build number is NRDtestkeys?
Click to expand...
Click to collapse
Im not sure what that is, but when i open "About Phone", it says Build NUmber : FRD-L19C636B380

Rommco05 said:
In settings u see update phone (updater) ?
Click to expand...
Click to collapse
No there isn't. Wow I didnt even realize that. At the bottom, theres only advanced settings and developer options and about phone
Is there anyway to fix this? D: I've tried so many ways already. I spent the entire day trying by downloading update.zips. But the internet service here in Malaysia really sucks. Down to 500kbps/s

Rommco05 said:
hm, what about factory reset in twrp? This can be a risk, but u have full build number anyway it is a risk because phone no must boot - or this can be a quick solution...
Click to expand...
Click to collapse
I've tried this before, the first time, it just factory reset then same. No keyboard , no apps. The 2nd time, "there is no OS do you really want to reboot?"
Is it possible to use a different region with FRD-L19?

Rommco05 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v73884/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...ll/hw/spcseas/update_data_full_hw_spcseas.zip
---------- Post added at 16:06 ---------- Previous post was at 16:03 ----------
This is B360 classic update witch I flashed xx times (but I have C432) I think if u flash in twrp first region.zip and after update.zip, problem will done. Download this two zips and I wrote u steps after some moment
Click to expand...
Click to collapse
What is region.zip? U gave me 2 links
1) update.zip
2)Update data full hw
I guess I will have to flash twrp first

Rommco05 said:
Region is number 2)Update data full hw, I think u alredy have twrp, yes flash latest twrp
Click to expand...
Click to collapse
Okay, now i have twrp 3.1.1-1
Downloading those 2 links still

I did it! Thanks to you! Camera works, apps restored but the keyboard isnt there. What can i do
Edit: NVM I changed the keyboard it works now. OMG THANKS. Truly the KING OF HONOR

off topic did this FRD L19 supports Volte calling ?

Good to see members still helping out..
Operating make sure you do a full. Backup of your device and safe a copy on SD card or HH as well as you phone..

Rommco05 said:
It's ok, factory reset u do after install?
---------- Post added at 18:02 ---------- Previous post was at 17:58 ----------
You are new on xda I think, so if somebody help you or some post is for you helpful feel free to tap on thanks button, just for the future
Click to expand...
Click to collapse
Factory reset not needed

friends competes an honor 8 FRL-L19 did not do any procedure on it just downloaded an app in the play store called firmware finder and installed the stock rom 380 but my device went into loop it goes into the recovery mode already downloaded some roms and tried to install by the card but not always sure of the error ... Someone can help me

Honor 8 bricked after failed unroot attempt. Please help!

Hey everyone. I rooted my Honor 8 yesterday using the following guide: https://www.xda-developers.com/honor-8-root-twrp-and-xposed/. Everything seemed to work fine at first, but soon my Bluetooth refused to turn on at random and apps constantly crashed (either on startup or when switching between them). It got annoying very quickly and after searching for hours and not finding any real solution, I decided root wasn't that important to me and I'd just unroot my phone and then hard reset. After using SuperSU's unroot function, my phone turned off and rebooted. But when it got to the blue screen with the honor logo, it froze. Nothing does anything. No matter which buttons I press/hold down. It's just stuck on that screen. I'd love to take out the battery, but with these new phones, it's sadly built in (who ever thought that was a good idea?). It's been this way for close to an hour. ADB doesn't recognize it anymore. The only way my PC seems to recognize it at this point is through the Device Manager, where it shows the yellow warning sign. Under Properties > General it reads "This device cannot start. (Code 10)". I've tried a few different things but none of them have worked. So this is where I'm at now. I'd hate to lose this phone since I just got it three months ago. I would really appreciate any sort of help, because I'm grasping at straws.

Rommco05 said:
Have you still access to twrp? When u trun on phone still is in bootloop. Which is your model and which was system last working?
Click to expand...
Click to collapse
Sorry, I might not have made this clear, but I can't even turn my phone off. It's literally stuck on the blue screen (how fitting). The model should be 51090QMF, but I don't know what you mean with the last part.

Rommco05 said:
51090QMF...??? Model must something like FRD-LxxCxxxBxxx
---------- Post added at 21:08 ---------- Previous post was at 21:08 ----------
Try reboot phone and hold vol +
Click to expand...
Click to collapse
My bad, I just looked it up on Amazon (where I bought it) and it said model number. This should be the real one: FRD-L09. The reboot worked, but it's still stuck on the honor logo. At least we know it's not hard-bricked now.
EDIT: I was able to get into eRecovery. Should I just press "Download latest version and reecovery"?

Rommco05 said:
Which system works last one? and for which region is your phone? Cxxx
Click to expand...
Click to collapse
I bought my phone from the German amazon site, so whichever one that is. I'm sorry, but I don't quite understand your system question. I used 7.0 if that's what you're referring to.

Rommco05 said:
Now understand so your model is FRD-L09?(32Gb ROM)/L19?(64Gb ROM)C432(EU)
So when phone rebooting u still se message your device is unlocked nad cat be trusted?
Click to expand...
Click to collapse
Yes, the 32GB one. And as I said, I was able to get into the Huawei eRecovery. I'm guessing I should just hit "Download latest version and recovery" at this point, but I was waiting just to be sure.

Rommco05 said:
You have still unlocked bootloader?
Try this:
1.create dload folder on inter. storage or sdcard
2.unzip zips which I here posted
3.put uziped separately to float
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73856/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3856/f1/full/hw/eu/update_data_full_hw_eu.zip
Click to expand...
Click to collapse
I do still have unlocked Bootloader, but at the moment I have no way to use it. My PC (ADB included) doesn't recognize the phone.

Rommco05 said:
What about two is still in your phone? Unplug phone from usb and reboot, + hold vol up but must be unluged after try dload method with sdcard
Click to expand...
Click to collapse
holding vol up just brings me to the eRecovery menu, where I can't do much. I'm not sure how much of twrp is still on my phone. Before I tried to unroot, all of it was.
EDIT: Sorry, never mind. I got into TWRP.

Rommco05 said:
Try dload method with zips which I posted
---------- Post added at 09:00 PM ---------- Previous post was at 08:56 PM ----------
Bootloader is still unlocked? If yes I tomorrow extract update app send you all parties which u nees to flash over fastboot if dload dont work for you
Click to expand...
Click to collapse
I'm currently downloading your files, my bootloader is unlocked. After I have the files unzipped, do I just flash them? If so, in what order?
Edit: Welp, he went offline. Can someone else tell me what to do with these files?

Rommco05 said:
How wrote before, unzip this files and separately put each unzipped to dload on sdcard, first bigger one
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
If are this files in dload folder turn phone or reboot + hold vol down together with vol up
Click to expand...
Click to collapse
Thank god, it booted. Thank you so much. What would be the best way to go about getting rid of root now? I'm willing to do a factory data reset at this point for everything to work again.

Rommco05 said:
Good job man for properly root go to developer section and twrp 3.1.1-1 by OpenKirin all steps is there
Click to expand...
Click to collapse
I'm just gonna go back to not having root after this, haha. It was just something I wanted to try, I don't need it that much. I did a factory reset and will now get my most important data back on my phone (thankfully I have a backup). Still, thank you so much for your help. I don't know what I would've done without you. I "Thanked" all your posts here, which is the least I can do.

help,your device is corrupte,will shutdown

My phone is nokia3.1plus,ta1104

i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again

did u unlock the bootloader or root your phone?
if yes then its normal just wait for the countdown to end

thisbearisdrunk said:
did u unlock the bootloader or root your phone?
if yes then its normal just wait for the countdown to end
Click to expand...
Click to collapse
It's not the root warning, it's the fdp partition damaged warning!

dugu1248 said:
It's not the root warning, it's the fdp partition damaged warning!
Click to expand...
Click to collapse
I don't really know what's that but usually these kinds of warning appear if u unlocked bootloader or root Ur device

thisbearisdrunk said:
I don't really know what's that but usually these kinds of warning appear if u unlocked bootloader or root Ur device
Click to expand...
Click to collapse
If the warning doesn't have "g.co/ABH" URL displayed, but "please check lock status", then your FDP (not FRP) partition is corrupted, and you may have to replace the motherboard. Understand?

dugu1248 said:
If the warning doesn't have "g.co/ABH" URL displayed, but "please check lock status", then your FDP (not FRP) partition is corrupted, and you may have to replace the motherboard. Understand?
Click to expand...
Click to collapse
After 30 seconds, what happens? Does the phone boot? I think I agree with @thisbearisdrunk...that it's normal if the bootloader is unlocked. Where are you getting "g.co/ABH", FDP,and FRP from? I don't see those anywhere in your screenshot. Not that I am capable of helping you in any way, but I am curious.
If the phone boots and runs fine after the 30 second warning , then it's just the manufacturer covering his butt since you unlocked the bootloader.
If it, in fact, doesn't boot like the screen says, then you need help beyond what I can offer. Find the correct firmware and reinstall it, I guess.

mn1968 said:
After 30 seconds, what happens? Does the phone boot? I think I agree with @thisbearisdrunk...that it's normal if the bootloader is unlocked. Where are you getting "g.co/ABH", FDP,and FRP from? I don't see those anywhere in your screenshot. Not that I am capable of helping you in any way, but I am curious.
If the phone boots and runs fine after the 30 second warning , then it's just the manufacturer covering his butt since you unlocked the bootloader.
If it, in fact, doesn't boot like the screen says, then you need help beyond what I can offer. Find the correct firmware and reinstall it, I guess.
Click to expand...
Click to collapse
It just shutdown all the time, cannot boot. Reinstall stock firmware already,all passed, but the phone still shows that warning, after 30s it just shutdown, cannot load system.

How did it get to that state? Did you unlock the bootoader? Try rooting somehow? If under warranty, get it fixed/replaced.

mn1968 said:
How did it get to that state? Did you unlock the bootoader? Try rooting somehow? If under warranty, get it fixed/replaced.
Click to expand...
Click to collapse
Unlock failed ,the fdp partition damaged. Now it cannot boot.

dugu1248 said:
Unlock failed ,the fdp partition damaged. Now it cannot boot.
Click to expand...
Click to collapse
I don't know what's FDP partition I tried googling but still didn't find
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
dugu1248 said:
Unlock failed ,the fdp partition damaged. Now it cannot boot.
Click to expand...
Click to collapse
But what I was able to find was if u tried to flash something and something went wrong then there can be problem with partition getting corrupt

thisbearisdrunk said:
I don't know what's FDP partition I tried googling but still didn't find
---------- Post added at 06:27 AM ---------- Previous post was at 06:24 AM ----------
But what I was able to find was if u tried to flash something and something went wrong then there can be problem with partition getting corrupt
Click to expand...
Click to collapse
Yes, downgrade from andoid 9 to android 8.1,it happens. The fdp.img must be ta-1104's. No one backup and release it.

dugu1248 said:
Yes, downgrade from andoid 9 to android 8.1,it happens. The fdp.img must be ta-1104's. No one backup and release it.
Click to expand...
Click to collapse
https://www.blogthetech.com/flash-file-nokia-3-1-plus-firmware-download-stock-rom/
This website has the android 8.1 firmware and tutorial on how to flash it
See if it helps

thisbearisdrunk said:
https://www.blogthetech.com/flash-file-nokia-3-1-plus-firmware-download-stock-rom/
This website has the android 8.1 firmware and tutorial on how to flash it
See if it helps
Click to expand...
Click to collapse
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.

dugu1248 said:
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.
Click to expand...
Click to collapse
I tried searching but I was not able to find ta-1104 firmware and I have the same model
I will try asking Nokia chat support
---------- Post added at 08:34 AM ---------- Previous post was at 07:59 AM ----------
dugu1248 said:
Helpless. I have tried all the rom from android 8.1 to 9, flashed all the firmware, all passed (successful),but that warning still shows, the phone shutdown after 30's , never boot.
Click to expand...
Click to collapse
r u able to boot into recovery or fastboot?

thisbearisdrunk said:
I tried searching but I was not able to find ta-1104 firmware and I have the same model
I will try asking Nokia chat support
---------- Post added at 08:34 AM ---------- Previous post was at 07:59 AM ----------
r u able to boot into recovery or fastboot?
Click to expand...
Click to collapse
Fastboot must be,or you can't flash rom. Recovery, never to be

dugu1248 said:
Fastboot must be,or you can't flash rom. Recovery, never to be
Click to expand...
Click to collapse
I asked in Nokia chat support they said that the device must be taken to nearby service centre

thisbearisdrunk said:
I asked in Nokia chat support they said that the device must be taken to nearby service centre
Click to expand...
Click to collapse
They said you must change the motherboard, yes? It can be fixed, but the nokia support won't release the solution.

dugu1248 said:
They said you must change the motherboard, yes? It can be fixed, but the nokia support won't release the solution.
Click to expand...
Click to collapse
They didn't say motherboard but yea it can be fixed all we need is the firmware but they won't give it

Does Ur pc recognise the device in fastboot mode?
Because when I connect my phone to pc in fastboot mode it doest recognise and the device does not show up in CMD when I type fastboot devices