After I installed TWRP I wanted to flash crdroid. It would not boot into system even after multiple wipes and flashes. I tried another rom and had the same problem.
I then tried to install the stockrom with miflash. Tried different roms and got an error in the tool about not finding a .bat file. I then tried to flash the stock rom trough twrp.
Now my phone is bricked. When I turn it on it blinks for a second and shuts down. Booting to recovery does noting. And booting to fastboot gives me the fastboot logo for a second and then it shuts down.
Is there anything I can do?
tldr: cant boot into recovery and fastboot. How do I flash stock rom?
I think you charging first
dungphp said:
I think you charging first
Click to expand...
Click to collapse
The screen flickers every second when I charge.
caboman said:
The screen flickers every second when I charge.
Click to expand...
Click to collapse
You can not enter fastboot?
dungphp said:
You can not enter fastboot?
Click to expand...
Click to collapse
It flashes the fastboot logo for a second when I enter. And then flashes back to the redmi logo every second.
I figured out that I need to boot in EDL mode. Will buy some tools to open the phone.
Same problem here, how can i fix it, help please?
caboman said:
I figured out that I need to boot in EDL mode. Will buy some tools to open the phone.
Click to expand...
Click to collapse
I think you will ****ed up like mine..hahaha
I've got my redmi note 9 pro hardbrick like yours and have try to flash it via edl mode..till now i'm still ****ed up with this thing
caboman said:
I figured out that I need to boot in EDL mode. Will buy some tools to open the phone.
Click to expand...
Click to collapse
I have the same problem, if you find out how to fix it tell me how, thanks
same here. This phone is very easy to brick apparently. I tried using a DIY Deep Flash cable to no avail. I will research how to enter EDL mode. If I find anything useful, I will post a thread somewhere around here.
Well the only chance for you to revive it is (1) flashing without battery, (2) or thru EDL Mode, which requires you to find the test points so you could flash stock firmware.
Next time you do custom ROM flashing be sure that your battery is atleast full charged or beyond 50%.
And also, please be careful in removing the back glass, insert the thin film or the adhesive separator not more than 4-5mm or you might mess up with the power button flex.
You dont need shorted wires or JTAG cables something like that to boot into EDL. Just use your stock cable and use a tweezers to short the test points, and before that, install Qualcomm HS-USB QDLoader 9008 drivers first so that MiFlashTool can read your phone.
How can i unbrick, my phone is note 9 pro
Related
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..
anyone can help me? I've tried to root my cherry mobile flare s play, I've flash twrp on it but it always boot in recovery it doesn't boot in system partition so I tried wiping the cache and dalvik cache, still doesn't boot so I tried flashing another recovery/rom and it just get worst it's now stuck in boot loop I've already tried the abd reboot-bootloader and always fall in error: device not found., I hope someone notice my case. thanks
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
TheShadowMC said:
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
Click to expand...
Click to collapse
but how can I boot it on bootloader? key combinations like vol+ and power or any combo doesn't work, only if someone can teach me how to boot it on bootloader or fastboot then there would be no problem for me, I don't know what to do now
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
TheShadowMC said:
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
Click to expand...
Click to collapse
will it work even if my device don't have battery on it?
kiltot24 said:
will it work even if my device don't have battery on it?
Click to expand...
Click to collapse
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
-Hope- said:
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
Click to expand...
Click to collapse
in my case I can't flash even a recovery image using sp flash tool. any help? sorry if I look like an ignorant any way thanks for your help guys, I really appreciate
no no problem, however what's the problem ?
I'm trying to flash a custom recovery on it but it doesn't work, I'm trying to flash twrp, the one I've flash before, because I don't have the stock rom of my device so I'm doing the process partially. I'm aiming to flash twrp and then restore my saved back up.
Hello,
i think your device stock frimware is there on google, however when you try to flash what error does it give or what happens ?
It doesn't show any error message and not showing any progress at all. my device just blink showing that the battery is charging though the battery is not present.
if it didnt detect it try pressing the volume up or volume down to make sure while connected ( and download button is pressed
just blink until it reaches time out.
I'm sure that my cable is working, it works on other device. I already install all the drivers I need.
is there a way to stop my device from simultaneous booting? it appears to be detected on device manager but just for a few sec, then reboot and appear again.
ensure the ROM is loaded properly in the flash tool.
Switch off the phone and remove battery.
press the start button in the flash tool to initiate the ROM flashing process. The process will be in hold, waiting for the phone to accept the new firmware.
Now connect the phone to computer.
Try these. Press and hold VOLUME DOWN OR VOLUME UP OR POWER+VOLUME UP OR POWER+VOLUME DOWN. One of these should work and the flashing process should start.
can I obtain the stock rom from the same device? I have the same model and it works properly. I can't download the stock rom from mediafire it always fail due to poor internet connection so I'm looking for another way.
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
kiltot24 said:
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
Click to expand...
Click to collapse
are you using the latest sp flash tool ?
yes thanks my device works fine now thank you for your help, the only problem now is how will I restore my device imei, it can be changed in engineer mode using at+ command but it be deleted again once conduct a factory reset in short it just set a temporary imei for my device, is there a way to change my device imei permanently?
I replaced the broken screen on my Kenzo and now it's stuck at the Mi logo. Funny thing is the technician said when he disconnects the touch ribbon it boots normally (but obviously with no touch) and locks up with Mi logo when it's connected. I've read that the mtk and sd screens are interchangeable so I don't think that's the issue. I don't have access to another screen so I have to make do with this one anyway.
I bought the phone from Gearbest two years ago and it came with the vendor rom which I never changed. I'm suspecting the vendor rom has something to do with it and now is the perfect time to flash a new rom before I sell it. Only problem is I have no clue how to flash a rom. I can get it to the fastboot screen but that's it.
Could someone please help me but in plain laymans English? Flashing for Dummies kind of thing. I've been a member here a while but haven't grasped the lingo or their meanings yet.
Thanks in advance.
Hooow?! said:
Google miflash
And download it.
Also download the latest miui developer rom
http://bigota.d.miui.com/8.1.25/miui_HMNote3ProGlobal_8.1.25_16348801ef_6.0.zip
Search for EDL.zip from xda itself and follow the instructions to get to edl mode from fastboot mode( to see if it's in edl mode check for the red blinking status LED when connected to the pc)
Now open miflash as administrator connect your phone to the PC.
Miflash should see it as something like COM..
Now extract the developer rom and in miflash browse for the extracted direvtory
At the bottom right select clean_all lock.bat and then press flash..
After few minutes the flashing should get completed and then hold the power button on the phone until u see the mi logo.
Wait for the booting to get completed and then setup the phone..
Congratulations you bow have a working phone again.
Click to expand...
Click to collapse
Thanks for the help. Well I got it all the way to flash in edl and around 9% it gave an error message "Object reference not set to an instance of an object" or something similar. So it basically failed. What can I do? I'm almost there
Hooow?! said:
Google some fastboot commands to erase partitions...
It should be something like this
fastboot erase boot
fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
First go to fastboot mode by holding vol down and power together .
Then connect to PC and then install minimal adb and fastboot kit. Then open the shortcut in desktop and then type fastboot devices and check if u device is there or not. If yes then copy and paste the commands above and then repeat the EDL flash procedure.
Click to expand...
Click to collapse
This is depressing. I followed your instructions and used the command "fastboot format partition" as that's the only one that would work and was suggested in options. The result was "failed device locked". :crying::crying::crying:
Yep. Same result. Does the bootloader have anything to do with all this?
Any ideas why it would boot normally with the touch ribbon disconnected but bootloop when connected? I'm beginning to wonder if flashing will even work.
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Twotems said:
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Click to expand...
Click to collapse
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Androbots said:
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Click to expand...
Click to collapse
Lol. Nah, I already have a Mi Mix 2 which I'm loving. This old faithful has to go.
Hello everyone !
I have a rooted, unlocked mi A3 with magisk and twrp everything worked fine but when i wanted to restart it, it goes to fastboot mode automatically...
I tried to fastboot reboot recovery, it boot in fastboot
If i type fastboot reboot, it goes to fastboot mode
If i press the power off button for 15 second it reboot to fastboot...
Do you have an idea how to repair this ? I don't car about loosing what is on my phone if necessary
EDIT: got some news if I set fastboot --setactive=a the phone boot correctly i can use it normally with no bug even reboot it without any problem
EDIT 2 : I solved the problem, i uninstalled magisk and everything was solved, I can get to recovery etc... Somehow magisk did something that my phone did not like
if I write fastboot setactive=b it bootloop
Thank you
it says unknown --setactive=a command
I also tried this method but system is says unknown --setactive=a command
I can't boot my mi a3.
Please help, me service center says motherboard is damaged.
It's cost 5600 Rs.
Help me please please..?????
Can you boot into twrp recovery? Turning off phone and doing power + volume up button. If yes you can try doing a factory reset.
vinod gupta said:
I also tried this method but system is says unknown --setactive=a command
I can't boot my mi a3.
Please help, me service center says motherboard is damaged.
It's cost 5600 Rs.
Help me please please..
Click to expand...
Click to collapse
Update your fastboot on the PC https://developer.android.com/studio/releases/platform-tools
I have this problem some days ago, i just change the active partition and every works as usual.
--Sorry for my bad English
vinod gupta said:
I also tried this method but system is says unknown --setactive=a command
I can't boot my mi a3.
Please help, me service center says motherboard is damaged.
It's cost 5600 Rs.
Help me please please..
Click to expand...
Click to collapse
Please read carefully: https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489
stuck on fastboot screen
I got a notification saying update to android 10 then I clicked ok it started to download and later installed after i cliked reboot i got a screen of fast boot and i cant do anything for it, i cant even reboot with volume up and power if i do anything i get same screen of fast boot
Kindly assist.
Mohsin
tikuff said:
Hello everyone !
I have a rooted, unlocked mi A3 with magisk and twrp everything worked fine but when i wanted to restart it, it goes to fastboot mode automatically...
I tried to fastboot reboot recovery, it boot in fastboot
If i type fastboot reboot, it goes to fastboot mode
If i press the power off button for 15 second it reboot to fastboot...
Do you have an idea how to repair this ? I don't car about loosing what is on my phone if necessary
EDIT: got some news if I set fastboot --setactive=a the phone boot correctly i can use it normally with no bug even reboot it without any problem
EDIT 2 : I solved the problem, i uninstalled magisk and everything was solved, I can get to recovery etc... Somehow magisk did something that my phone did not like
if I write fastboot setactive=b it bootloop
Thank you
Click to expand...
Click to collapse
mohsin.saboowala said:
I got a notification saying update to android 10 then I clicked ok it started to download and later installed after i cliked reboot i got a screen of fast boot and i cant do anything for it, i cant even reboot with volume up and power if i do anything i get same screen of fast boot
Kindly assist.
Mohsin
Click to expand...
Click to collapse
Are you bootloader unlocked?
stuck on fastboot screen
Sir to be honest i am not a software person and possibly wont understand what you said, but ill explain in detail what exactly happened.
First I had purchased Mi a3 with android 9 and later i got an update saying android 10 the phone was working absolutely fine.
Today i received another update which mentioned android 10 and as usual i updated it and when i restarted the phone i directly got that fast boot screen.
I went thru so many websites regarding this issue but did not find any solution and almost everywhere it said to flash the phone.
So i tried to flash the phone, I downloaded firmware, miflash tool, abd drivers, after doing all this my phone is not being detected on my pc, i checked device manager and even i got links from XDA as well i followed that as well but still no luck on detection.
Upon finding the query on detection issue i found solutions to debug from my device but my device is not starting up so i even cant do debugging as well.
Please help.
fabio_faria_23 said:
Are you bootloader unlocked?
Click to expand...
Click to collapse
mohsin.saboowala said:
Sir to be honest i am not a software person and possibly wont understand what you said, but ill explain in detail what exactly happened.
First I had purchased Mi a3 with android 9 and later i got an update saying android 10 the phone was working absolutely fine.
Today i received another update which mentioned android 10 and as usual i updated it and when i restarted the phone i directly got that fast boot screen.
I went thru so many websites regarding this issue but did not find any solution and almost everywhere it said to flash the phone.
So i tried to flash the phone, I downloaded firmware, miflash tool, abd drivers, after doing all this my phone is not being detected on my pc, i checked device manager and even i got links from XDA as well i followed that as well but still no luck on detection.
Upon finding the query on detection issue i found solutions to debug from my device but my device is not starting up so i even cant do debugging as well.
Please help.
Click to expand...
Click to collapse
Did you try to reset the phone using the recovery mode?
From switch off, press simultaneously for a few moments the Volume Up and Power Button.
you should enter in recovery mode and apply a factory reset.
this works for me
stuck on fastboot screen
I cannot enter the recovery mode when i press the buttons you said it again comes at fast boot screen and i tried to flash with mi flash tool but that flash process continuesly goes on and no changes in phone.
posy said:
Did you try to reset the phone using the recovery mode?
From switch off, press simultaneously for a few moments the Volume Up and Power Button.
you should enter in recovery mode and apply a factory reset.
this works for me
Click to expand...
Click to collapse
fastboot stuck
posy said:
Did you try to reset the phone using the recovery mode?
From switch off, press simultaneously for a few moments the Volume Up and Power Button.
you should enter in recovery mode and apply a factory reset.
hellow sir,
I have a rooted, unlocked mi A3 with magisk and twrp everything worked fine but when i wanted to restart it, it goes to fastboot mode automatically...
I tried to fastboot reboot recovery, it boot in fastboot
If i type fastboot reboot, it goes to fastboot mode
If i press the power off button for 15 second it reboot to fastboot...
Do you have an idea how to repair this ?
Click to expand...
Click to collapse
my mi a3 is stuck in the fastboot in the slot a, what should i do ?
swaraj123123 said:
my mi a3 is stuck in the fastboot in the slot a, what should i do ?
Click to expand...
Click to collapse
Unstuck it..?
But seriously, what kind of help do you expect? You haven't provided a single piece of information.
Hi Guys, so the things I was using the official AOSP extended rom on my Redmi Note 9 Pro after but after ccouple of days changed my mind wanted to revert back to the official MiUi rom. So used the Miflash Tool to flash "joyeuse_global_images_V12.5.4.0.RJZMIXM_20220215.0000.00_11.0_global" after flashing it reported a failed error and the fastboot screen started flashing on and off. After turning off the phone and pressing the power button to turn the phone flashes the redmi logo for less than a second and turns off. Plugging in the charger makes the phone flash Redmi logo and then turn off again repeatedly. I can neither get into fastboot mode nor into recovery. Is there any solution to this problem? Any help will be much appreciated. Below is a short clip of the problem.
Abir172 said:
Hi Guys, so the things I was using the official AOSP extended rom on my Redmi Note 9 Pro after but after ccouple of days changed my mind wanted to revert back to the official MiUi rom. So used the Miflash Tool to flash "joyeuse_global_images_V12.5.4.0.RJZMIXM_20220215.0000.00_11.0_global" after flashing it reported a failed error and the fastboot screen started flashing on and off. After turning off the phone and pressing the power button to turn the phone flashes the redmi logo for less than a second and turns off. Plugging in the charger makes the phone flash Redmi logo and then turn off again repeatedly. I can neither get into fastboot mode nor into recovery. Is there any solution to this problem? Any help will be much appreciated. Below is a short clip of the problem.
Click to expand...
Click to collapse
Can you post the log of Miflash?
Here's the log of the flash.
NOSS8 said:
Can you post the log of Miflash?
Click to expand...
Click to collapse
According to the log, the flash was successful, the error is normal (6:02:45 PM 9f886790]:error:Not catch
checkpoint (\$fastboot -s .* lock),flash is not done) since you did not lock the bootloader (flash_all.bat).
After the flash the phone reboots automatically, did you interrupt it?
First try to see if a button is not defective, a bit of WD40 product for example and operate it several times.
But if it worked well before it would be a strange coincidence but it is possible.
(I had this case on one of my phones by dint of flashing).
Hi sir I have this problem too
elinajafi said:
Hi sir I have this problem too
Click to expand...
Click to collapse
Can you post the log of Miflash?
It seems like a common issue happens with me when I try to flash stock rom via fastboot, if you ever been able to enter fastboot flash custom recovery (like twrp) and use it to flash the stock rom zip (recovery method), it should work..