Its a 64 gb A1 variant. Everything was stock. It was on stock pie (update via OTA). I never tried unlocking bootloader as well as flashing custom rom.
3 day ago when i using it,suddenly it turn off and stuck at android one logo. I can go fastboot mode by pressing power+volume down.
I try to flash stock rom using mi flash tool,but as my bootloader is locked it show error. :crying:
Please help me out,it is my daily driver. :crying:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
punktnet said:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
Click to expand...
Click to collapse
I found this thread after i post this. Hope this will help me, though i am not try yet. I will update what happen. https://forum.xda-developers.com/showpost.php?p=78378088&postcount=43
use miunlock tool to unlock bootloader if you're not familiar with fastboot commands and as punktnet said unlocking bootloader will reset your device and erase your userdata and internal storage then maybe your device works fine if not then reboot it again in fastboot mode and flash stock firmware.
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
WORKMEISTER said:
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
Click to expand...
Click to collapse
This occurred to me today aswell :c I tried wiping all the data from recovery but the phone couldn't even end to wipe all. My phone went into a "erasing" screen for almost 1 hour when I decided trying to hold the power button, it rebooted but I still got into the bootloop :l my Xiaomi Mi A1 is not unlocked for bootloader so I can't flash it. I also tried with the mi unlocking but didn't go past 50% when it launched an error. Guess I'll die.
Related
I rooted my oneplus 2 some time ago to install the Screencast.app that there was on the oneplus one. I then after a while noticed that it started to perform worse than before i rooted it, so i decided to try to unroot it to fix the performance. But when i rebooted to fastboot and tried to flash the stock recovery, it said that the bootloader was locked. I then tried doing the unlock command (fastboot oem unlock), and it seemed to work (although - it didnt - in cmd it said finish but when i booted into bootloader again it was still locked) but when my phone tried to reboot, there was i quick flash of the oneplus logo and then the screen went blank. When i tried turning it off, i just rebooted and did the same thing. I could not boot into recovery either. The only thing i could do was booting into fastboot and from there i managed to use the command fastboot continue and restart my phone properly. So now i cant use my recovery to factory reset, i cant install a new recovery because the bootloader is locked, and now every time my phones powers off, i have to do the same thing with booting into fastboot and do the fastboot continue command to start it.
Can anyone tell me what the issues is here and how i can solve it?
I have the same problem, but once I got the phone to boot, I did a factory reset. Now I'm unable to even boot, literally the only thing that works is fastboot.
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Stop experimenting.
Does fastboot work? Do a full flash with miflash(erasing all storage)(firmware should be of your model itself)
If fastboot doesnt work,try putting in the charger with battery in,if there is any vibration,you have a chance of reviving your r2
#fingerscrossed
Ezio95 said:
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Click to expand...
Click to collapse
Yup actually download the latest version of miui fastboot files..paste them in the fastboot folder... Dont bother erasing you phn again(as it does erase at the time of writing new files...)And most importantly flashing only 3 files is more than enough. Flash them in the order boot.img, system.img, recovery.img and thats it. If your problem is actually not booting into fastboot then....press the volume down button and insert your usb while keeping it pressed.
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Ezio95 said:
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Click to expand...
Click to collapse
If you can get the fastboot to work, you can flash recovery on your phone for good or temporarily to flash zips.
How to do it?
1.Get into fastboot on phone
2.Install minimal adb and fastboot in your computer
3.Run adb and install drivers
4.Connect your phone which should be in fastboot to computer
5.Check for devices by using "fastboot devices", if a device is listed, proceed
6.Download a custom recovery, rename the recovery img to something easy than using the full name and copy the img into the folder where minimal adb and fastboot is installed
7.Type in "fastboot flash recovery <name you gave to recovery img>.img" (img for the image format) to flash recovery permanently
OR
7.Type in "fastboot boot <recovery name>.img" to use it temporarily, this method will erase the recovery on reboot so flash whatever you want before rebooting if you're following this method.
8.Flash in your ROM zip, try stock and custom ROMs, see if you can get your phone to work
GOOD LUCK
Same error with my yureka plus (error "remote: failed to write partition"). I'm planning to buy redmi 2 prime.. . Scared if this will happen to redmi 2 prime
please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.
you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.
U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.
not worked
Bhavesh_khatri said:
you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.
Click to expand...
Click to collapse
I have done clean install And everything already.But not Working and now phone is not going into fastboot mode also and also not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".
Done already before writing this thread.
raymond_bqg said:
U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.
Click to expand...
Click to collapse
i tried to flash TWRP and CWM recovery By Adb and fatboot method using commands (command prompt method) amd on giving commands all executed properly but not resulted.
From now phone is not going into fastboot mode also and not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".sometimes it is detected as Qualcomm Device on connecting.
In that case your device is hard bricked. You need professional help.
But check if your device is listed or not in device manager if it shows an exclamation mark try to update the drivers and though your device doesn't boots into fast boot mi-flash would probably detect your phone and than flash hope it would recover your device up-to certain extent.
I only understand your problem why because I too same thing as you did.
Lavnish said:
please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.
Click to expand...
Click to collapse
Simply flash twrp recovery n your phone through adb drivers or contact me. I can't give you video tutorial because I don't want you make that mistake again. my mail id: [email protected]
Alrighty I think praveen66542 is not wrong.
I have actually a redmi 2 and I had exactly the same problem a year ago; I've tried all the methods but it didn't work
So i've do is :
I installed Android SDK + ADB Drivers
I Turned my phone into fastboot mode
And I wiped all data from ADB But if you don't want to loose your data you can always do a backup from ADB and then wipe device's data
I think that's the one and only working solution.
hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance
@dgadelha any help ?
What are the specs of your Zen 5?
dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks
Hey jaabax, were you able to fix your device ?
Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.
same issue, anyone got any update on fix?
jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution
Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?
Оh man.. I have the same issue, and can't fix it...
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
AgustinPatatas said:
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
Click to expand...
Click to collapse
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
WhatzIt2Ya said:
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
Click to expand...
Click to collapse
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
AgustinPatatas said:
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
Click to expand...
Click to collapse
When I updated it. I uninstalled magisk, relock the bootloader, and reboot the phone a couple of times (to chack for corruption and stuff). Then I installed the update. Try flash pie rom with mi flash tool.