Database Users

unable to root my galaxy s5 again

Model SM-G900I
Model name GALAXY S5
Version Android 5.0
i have rooted my phone earlier using odin successfully, but after unrooting my device i cannot root it again.
i tried unrooting it using kingroot and my phone was broken, i was unable to turn it on, nothing was working, so i downloaded original firmware from sammobile, i have successfully installed this firmware which is of my region(oceania)- G900I, but still i see i am unable to check firmware updates as it says it gives error of unauthorized installation.
i tried to root again using one touch root apps, also odin & one click tools using usb debugging, nothing is working, i have rooted same device successfully using ODIN but that is not working for me now.
please help me, i want to root my phone again.

Did you try to flash Twrp recovery through adb? Once this is done, any ROM and/or SuperSU for root should be possible to flash with Twrp. I don't remember if the boot loader needs unlocking. Maybe it has been locked again by hazard and needs to be unlocked again.
Edit: I did it like this: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/

Danstroem said:
Did you try to flash Twrp recovery through adb? Once this is done, any ROM and/or SuperSU for root should be possible to flash with Twrp. I don't remember if the boot loader needs unlocking. Maybe it has been locked again by hazard and needs to be unlocked again.
Click to expand...
Click to collapse
where do i get twrp file for my s5 g900i??
i downloaded one from the forum, everything goes well but when i try 8th step, "fastboot flash recovery twrp.img"
it stucks on "(waiting for device)" and nothing happens.
btw how to know if my bootloader is locked? because nothing is working here for me. i tried everything which has worked but now nothing working, need help :-/

sukhsab007 said:
where do i get twrp file for my s5 g900i??
i downloaded one from the forum, everything goes well but when i try 8th step, "fastboot flash recovery twrp.img"
it stucks on "(waiting for device)" and nothing happens.
btw how to know if my bootloader is locked? because nothing is working here for me. i tried everything which has worked but now nothing working, need help :-/
Click to expand...
Click to collapse
This is the latest official twrp binary for the Galaxy S5: https://dl.twrp.me/klte/
Unfortunately, I don't know, how a locked bootloader behaves, sorry. Can you post a photo of your bootloader screen? Something similar to this: http://media2.giga.de/2014/03/samsung-galaxy-s5-download-modus-rcm992x0.jpg
http://www.galaxys5update.com/install-twrp-recovery-australia-galaxy-s5-sm-g900i says that the Australian G900i seems NOT to be locked. It also states this:
TURN OFF the Reactivation Lock – This is only needed if you already turned-it-ON, from which you cannot modify the system when it’s turned-ON. Just tap on Settings>>Security>>Reactivation Lock and then uncheck the Turn Reactivation lock on.
Click to expand...
Click to collapse
Do you have this setting?

yes i have same setting.
i tried to install twrp recovery via fastboot but when i do "fastboot flash recovery ****.img" in cmd, than nothing much happens, it's like " <waiting for device>", left for 20mins, still the same.
bootloader screen " snag. gy/YqjXY .jpg "

sukhsab007 said:
yes i have same setting.
i tried to install twrp recovery via fastboot but when i do "fastboot flash recovery ****.img" in cmd, than nothing much happens, it's like " <waiting for device>", left for 20mins, still the same.
bootloader screen " snag. gy/YqjXY .jpg "
Click to expand...
Click to collapse
Hm, I'm puzzled. The bootloader seems OK. There doesn't seem to be a driver issue with your PC, because the command "adb reboot bootloader" works, as seen in the "screenshot".
I'm only guessing now. Maybe it helps to disconnect and reconnect USB after the bootloader has been started and reissue the flash command. If it does not respond after 20 seconds, abort with ctrl-c and retry. Or maybe, you can try the same procedure on a different machine. Or maybe try a different USB cable or a different USB port on your machine. Make sure, that you have the latest android drivers/tools installed and there are no parallel/conflicting versions installed. You are sure, that on your phone you have enabled USB debugging and disabled the reactivation lock?
What is different now, compared to the time ODIN worked? Different Windows, different cable, different USB port? Try to disconnect all other USB devices. Connect the phone directly without a USB hub.
Well, I'm running out of ideas. Maybe someone else can help out...

@Danstroem I think you've pretty much covered it.......
The only things I could add.....
Maybe try disabling antivirus and firewalls......
Also, if kies is installed/running, disable that too.....
http://i.imgur.com/rVnFwJM.jpg

Using fastboot with an samsung device will not work you have to use Odin because fastboot us not designed to work with samsung devices.
---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------
Those one click root apps never work for me. What I do is flash a custom recovery, then I flashed the supersu zip http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
Fastboot only works with some android devices such as nexus Motorola asus, etc
---------- Post added at 07:01 PM ---------- Previous post was at 06:59 PM ----------
Also if you want to get updates working again you have the do a clean flash meaning wiping all partitions from twrp and flashing the stock firmware again
---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------
Download the twrp file with the .img.tar extension and flash it in odin

Zenfone 2 Laser ZE550KL stuck a boot screen

My new Zenfone 2 Laser, purchased 4 months ago and having stock ROM and recovery is stuck at ASUS logo screen/ boot screen.
The phone is not even booting to recovery mode (power + volume down). Though in fastboot mode (power + volume up) I could erase cache but after rebooting its again the same logo screen.
Has anyone experience the same issue?

I have the same issue, do you have any solution?

preeti-defy said:
My new Zenfone 2 Laser, purchased 4 months ago and having stock ROM and recovery is stuck at ASUS logo screen/ boot screen.
The phone is not even booting to recovery mode (power + volume down). Though in fastboot mode (power + volume up) I could erase cache but after rebooting its again the same logo screen.
Has anyone experience the same issue?
Click to expand...
Click to collapse
Hello yes I had this problem and you have to install a recovery with fastboot cause even if the screen doesn't show fastboot mode i think your device is recognized by fastboot. After you could access recovery. And i restarted my phone by the cmd "fastboot boot boot.img" but when i have to do it always when i power off my phone so i not resolved all the problem

What version do you use? I tried official or unofficial rom, it does not work.
I got bootloop even I tried "fastboot boot boot.img or fastboot flash boot boot.img".

chchtono said:
What version do you use? I tried official or unofficial rom, it does not work.
I got bootloop even I tried "fastboot boot boot.img or fastboot flash boot boot.img".
Click to expand...
Click to collapse
the last version

Flash stock ROM via Side load ADB in fastboot mode.Search google or XDA u will get info how to flash stock ROM in fastboot mode.
U need to download full ROM ( or fastboot ROM) of ur device !

I'm currently facing the same problem...and though the phone goes into fastboot, and the PC device manager detects the phone as ADB Android device (even when the phone is simply attached without pressing anything or the power key), cmd ADB doesn't detect the phone, cos USB debug mode is turned off after a wipe and a new installation...even if the installation goes sideways, like this situation....so pls someoone come with a better response.
---------- Post added at 03:11 AM ---------- Previous post was at 03:05 AM ----------
RonakRonak said:
Flash stock ROM via Side load ADB in fastboot mode.Search google or XDA u will get info how to flash stock ROM in fastboot mode.
U need to download full ROM ( or fastboot ROM) of ur device !
Click to expand...
Click to collapse
That's what bricked my device! installing stock rom downloaded from Asus...The updated ROM had no effect on the previous challenges I was facing, so I downloaded this ROM instead UL-ASUS_Z00E-WW-12.8.5.222-user to try a downgrade, then I update through OTA once done, and it landed me with this problem... I can't tell if it's the Rom, or I missed something...
---------- Post added at 03:22 AM ---------- Previous post was at 03:11 AM ----------
RonakRonak said:
Flash stock ROM via Side load ADB in fastboot mode.Search google or XDA u will get info how to flash stock ROM in fastboot mode.
U need to download full ROM ( or fastboot ROM) of ur device !
Click to expand...
Click to collapse
Can u kindly provide a link to where we can get a clean, working fastboot rom for our devices??? thank u!!!
mine is a Z00ED or Z00L... will be grateful

abodan09 said:
I'm currently facing the same problem...and though the phone goes into fastboot, and the PC device manager detects the phone as ADB Android device (even when the phone is simply attached without pressing anything or the power key), cmd ADB doesn't detect the phone, cos USB debug mode is turned off after a wipe and a new installation...even if the installation goes sideways, like this situation....so pls someoone come with a better response.
---------- Post added at 03:11 AM ---------- Previous post was at 03:05 AM ----------
That's what bricked my device! installing stock rom downloaded from Asus...The updated ROM had no effect on the previous challenges I was facing, so I downloaded this ROM instead UL-ASUS_Z00E-WW-12.8.5.222-user to try a downgrade, then I update through OTA once done, and it landed me with this problem... I can't tell if it's the Rom, or I missed something...
---------- Post added at 03:22 AM ---------- Previous post was at 03:11 AM ----------
Can u kindly provide a link to where we can get a clean, working fastboot rom for our devices??? thank u!!!
mine is a Z00ED or Z00L... will be grateful
Click to expand...
Click to collapse
Hi.
Bro first you have to know what's ur exact device model and go to Asus official support page.select ur device model and download latest firmware (as ur device can boot in to fastmode u have chance to get things working again).(have u checked how to go back to stock on XDA thread.pm the thread moderater their.I think he can Help u more precisely. )

RonakRonak said:
Hi.
Bro first you have to know what's ur exact device model and go to Asus official support page.select ur device model and download latest firmware (as ur device can boot in to fastmode u have chance to get things working again).(have u checked how to go back to stock on XDA thread.pm the thread moderater their.I think he can Help u more precisely. )
Click to expand...
Click to collapse
Well, i guess u missread my previous comment since i made it clear that i downloaded both the latest firmware, and the one that came with my phone from the official site....
secondly, without usb debug mode turned on, i don't see the possibilities of flashing the roms...but also, i've come accross ppl with similar issues in a different thread, which i'm closely following and monitoring....with the hope of a breakthrough.
so, thanx for your time.

abodan09 said:
Well, i guess u missread my previous comment since i made it clear that i downloaded both the latest firmware, and the one that came with my phone from the official site....
secondly, without usb debug mode turned on, i don't see the possibilities of flashing the roms...but also, i've come accross ppl with similar issues in a different thread, which i'm closely following and monitoring....with the hope of a breakthrough.
so, thanx for your time.
Click to expand...
Click to collapse
ohh i m sorry.yes ther are threads regarding same issue.Hope u will got ur device working soon :good:

OP2 stuck in bootloop on upgrading 3.0.2 .. even after trying tons of things

First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out

Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk

Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again

Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.

Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!

Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!

Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.

OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...

ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??

No i forgot to enable...

No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?

ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.

ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.

ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?

Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).

When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings

Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android

ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help

ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

!!!help!!! Mi a1 still in edl only white led blinking and black screen

Few days ago i decide to install GCAM on my mi a1 with magisk and a patched boot...evrything is working fine but when i unistall magisk phone still rebooting many times and wifi doesnt work.
I tried to boot the original boot.img , then i flash oreo stock in many different version but nothing to do.
At this point wrongly i try to click on flash factory. bat file but i dont know if the code is work correct because the command prompt is closing in a bit.
Now i read that this file corrupt and delete the IMEI...
Only solution for me is the edl because in another try i lock bootloader and then i cant unlock, i dont know why, by fastboot command.
Then i open my phone e try edl method....my device is recognized but after few attemps to flash many stock rom from the first to the last nothing change...
my device still black with blinking led, evry buttons do not respond.
WHAT CAN I DO??? I NEED YOUR HELP

Just download latest firmware or any old and flash it in fastboot
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
Booting in fastboot?
---------- Post added at 06:13 PM ---------- Previous post was at 06:09 PM ----------
kevinperdichizzi said:
Few days ago i decide to install GCAM on my mi a1 with magisk and a patched boot...evrything is working fine but when i unistall magisk phone still rebooting many times and wifi doesnt work.
I tried to boot the original boot.img , then i flash oreo stock in many different version but nothing to do.
At this point wrongly i try to click on flash factory. bat file but i dont know if the code is work correct because the command prompt is closing in a bit.
Now i read that this file corrupt and delete the IMEI...
Only solution for me is the edl because in another try i lock bootloader and then i cant unlock, i dont know why, by fastboot command.
Then i open my phone e try edl method....my device is recognized but after few attemps to flash many stock rom from the first to the last nothing change...
my device still black with blinking led, evry buttons do not respond.
WHAT CAN I DO??? I NEED YOUR HELP
Click to expand...
Click to collapse
First download oreo firmware and boot into fastboot mode
The open cmd and hit
Fastboot oem unlock
Then open xiaomiflash software and flash it.
Note: don't lock your bootloader again when you have Installed any custom thing

hamzaag49 said:
Just download latest firmware or any old and flash it in fastboot
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
Booting in fastboot?
---------- Post added at 06:13 PM ---------- Previous post was at 06:09 PM ----------
First download oreo firmware and boot into fastboot mode
The open cmd and hit
Fastboot oem unlock
Then open xiaomiflash software and flash it.
Note: don't lock your bootloader again when you have Installed any custom thing
Click to expand...
Click to collapse
I previously tried flash in fastbooot with evry stock release from nutgat to oreo and doesnt work. this before i go in edl.
now in edl is the same , flash is succesful but nothings happen screen still black led blinking and i cant go fastboot

kevinperdichizzi said:
I previously tried flash in fastbooot with evry stock release from nutgat to oreo and doesnt work. this before i go in edl.
now in edl is the same , flash is succesful but nothings happen screen still black led blinking and i cant go fastboot
Click to expand...
Click to collapse
I have exactly the same problem tried everything but still no solution. Bad thing is that there is no service center in my country.

daveve said:
I have exactly the same problem tried everything but still no solution. Bad thing is that there is no service center in my country.
Click to expand...
Click to collapse
Me too. i'm freaking out because i think that the only solutions is change the mainboard, and no xioami centre for doing that but only an autorized .

Cannot flash stock ROM through MiFlash tool

My MiA1 got stuck on Main Menu yesterday. I couldn't power it off or restart as neither the power button nor the volume buttons were responding. After an hour it automatically powered off. When I booted it up again, it was stuck on AndroidOne logo. So I decided to reset my phone. When I booted in recovery mode, there's an error being displayed at the bottom. It says "Failed to clear BCB message: failed to sync /dev/block/bootdevice/by-name/misc: Operation not permitted". Anyway I started resetting the phone but even after 2 hours it was stuck on "Formatting /data...". Next I tried to flash stock rom using MiFlash tool but it takes too long to flash. I have seen videos in which it happens in 200-500 seconds. I ran MiFlash for more than 6000 seconds and then diconnected my phone. I don't understand what is the issue here.
Please note that I have never unlocked bootloader before. Phone was running on the stock rom.

first thing first after reading your post it seems your Nand chip is faulty but i'm not sure.
so MiFlash works only for Unlocked Bootloader.
first try unlocking bootloader with fastboot
then try flashing stock rom
or
you can try QFIL tool from QPST for flashing stock rom.

ranjodhricky said:
first thing first after reading your post it seems your Nand chip is faulty but i'm not sure.
so MiFlash works only for Unlocked Bootloader.
first try unlocking bootloader with fastboot
then try flashing stock rom
or
you can try QFIL tool from QPST for flashing stock rom.
Click to expand...
Click to collapse
I tried to unlock bootloader with fastboot but whenever i use the command "fastboot oem unlock" it reboots my phone. After again booting into fastboot mode, if i check the bootloader unlock status, it shows false. Is there anything I am doing wrong?

i think you haven't enabled oem unlocking in developer settings now i think there is no way to unlock bootloader and without unlocking you cant flash with MiFlash. you can try QFIL for flashing i think it will work with locked bootloader if not then you have to got service center and they will flash it for u
---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------
try flashing in edl mode restart in fastboot then enter
fastboot oem edl
phone screen goes black and led blinks then try flashing
---------- Post added at 08:39 PM ---------- Previous post was at 08:28 PM ----------
if all of the above not working try putting phone into edl mode by testpoint it will work here is the link for the image and tutorial for putting phone into edl with test point
http://gsmclinic.com/redmi-a1-xiaomi-mdi2-edl-pinout-edl-test-point/
after putting into edl flash it with MiFlash or Qfil.
but you have to open the back case of phone.

ranjodhricky said:
i think you haven't enabled oem unlocking in developer settings now i think there is no way to unlock bootloader and without unlocking you cant flash with MiFlash. you can try QFIL for flashing i think it will work with locked bootloader if not then you have to got service center and they will flash it for u
---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------
try flashing in edl mode restart in fastboot then enter
fastboot oem edl
phone screen goes black and led blinks then try flashing
---------- Post added at 08:39 PM ---------- Previous post was at 08:28 PM ----------
if all of the above not working try putting phone into edl mode by testpoint it will work here is the link for the image and tutorial for putting phone into edl with test point
http://gsmclinic.com/redmi-a1-xiaomi-mdi2-edl-pinout-edl-test-point/
after putting into edl flash it with MiFlash or Qfil.
but you have to open the back case of phone.
Click to expand...
Click to collapse
fastboot oem edl is not working. It shows:
OKAY [ 0.068s]
Finished. Total time: 0.073s
But my phone remains in fastboot mode only. I guess service center is the only I have.

you have to wait 10 to 15 second after entering the cmd sometime it takes some time to reboot into edl or you can use test point method it will works for you. i think even guys at service center also use test point to flash the firmware if you can remove the back cover you can try it.

ranjodhricky said:
you have to wait 10 to 15 second after entering the cmd sometime it takes some time to reboot into edl or you can use test point method it will works for you. i think even guys at service center also use test point to flash the firmware if you can remove the back cover you can try it.
Click to expand...
Click to collapse
Thanks for all the help that you have provided :angel:. For now, I have sent my phone to the service center. Lets see if they can work something out.