Database Users

Help with bricked xiaomi redmi 2 prime

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

LS997 rebooting into yellow Rpm crash screen

Hey guys I'm in need of some help..I replaced my V20 screen and when I turned my phone on it booted into a yellow screen that's says Rpm crash...Lge crash handler etc etc..Says something about a system dump..I can boot into TWRP..I wipe the device clean..Even installed a new rom..Still won't get past this yellow screen can you guys help.

flymalikcool said:
Hey guys I'm in need of some help..I replaced my V20 screen and when I turned my phone on it booted into a yellow screen that's says Rpm crash...Lge crash handler etc etc..Says something about a system dump..I can boot into TWRP..I wipe the device clean..Even installed a new rom..Still won't get past this yellow screen can you guys help.
Click to expand...
Click to collapse
can you take a photo and post.
push a new boot.img to your phone
depending on model if you have fastboot access you can try to do this
Fastboot erase cache
fastboot erase fota
fastboot erase misc
fastboot erase system
fastboot erase data
then reboot the device back into twrp, re-flash a rom and make sure the kernel is included.
sounds like you flashed a bad boot.img causing the phone not to boot. Or your new screen is causing a issue

Team DevDigitel said:
can you take a photo and post.
push a new boot.img to your phone
depending on model if you have fastboot access you can try to do this
Fastboot erase cache
fastboot erase fota
fastboot erase misc
fastboot erase system
fastboot erase data
then reboot the device back into twrp, re-flash a rom and make sure the kernel is included.
sounds like you flashed a bad boot.img causing the phone not to boot. Or your new screen is causing a issue
Click to expand...
Click to collapse
Here goes a picture

flymalikcool said:
Here goes a picture
Click to expand...
Click to collapse
Yeah its a bad boot.img
Get a boot.img for ur device..
Flash it with twrp or
Fastboot flash boot.img and reboot
Or rerun dirty santa step 3 and reboot.

Team DevDigitel said:
Yeah its a bad boot.img
Get a boot.img for ur device..
Flash it with twrp or
Fastboot flash boot.img and reboot
Or rerun dirty santa step 3 and reboot.
Click to expand...
Click to collapse
Thanks for the help I downloaded the Sprint boot image for my phone flash through TWRP..Same results..TWRP gave me options for partitions I choose boot..

flymalikcool said:
Thanks for the help I downloaded the Sprint boot image for my phone flash through TWRP..Same results..TWRP gave me options for partitions I choose boot..
Click to expand...
Click to collapse
it didn't work went right back to yellow screen

flymalikcool said:
it didn't work went right back to yellow screen
Click to expand...
Click to collapse
Humm.. Try the wipe commands. Then flash my Rom if ur on ls997.
Can you mount all ur stuff with twrp?
Does it show 0byte free space?

Team DevDigitel said:
Humm.. Try the wipe commands. Then flash my Rom if ur on ls997.
Can you mount all ur stuff with twrp?
Does it show 0byte free space?
Click to expand...
Click to collapse
Thanks for the concern and speedy response..Yes I can mount all my stuff..As far as the wipe commands are you speaking about the fastboot commands you posted earlier..

flymalikcool said:
Thanks for the concern and speedy response..Yes I can mount all my stuff..As far as the wipe commands are you speaking about the fastboot commands you posted earlier..
Click to expand...
Click to collapse
Yeah..
Put into fasboot and wipe everything
Fasboot erase
Misc
Fota
Cache
Dalvik
System
Data
Boot
Then boot back into twrp.. Mount everything and flash a stock ls997 rom.
I had this happen before to me. I believe i had to fix partitions on my device using advanced wipe and ext4 wipe options 1 by 1. But it showed free space 0 for everuthing also.
Do you have a backup on twrp that has ur efs?

Yes I have my efs backup

After fastboot commands im having a problem mounting system

flymalikcool said:
After fastboot commands im having a problem mounting system
Click to expand...
Click to collapse
need to wipe the phone using twrp now to mount system again,
if not if it shows 0 bytes the repair system to ext4 and flash a rom..
lastly, if this repair was done with a knock off screen thats your issue, the oem screen and the 3rd party
probably dont spec the same, and the drops in voltage cause the phone to kernel panic and fail, this is a common issue across many phones after
doing a little digging Via google.

flymalikcool said:
After fastboot commands im having a problem mounting system
Click to expand...
Click to collapse
any luck yet?

please helpe me

i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead

leroilion02 said:
i try instaling cortex 7.00( 7.1.2) after al is ok after the phone reboot evry time when i using i try wipe data with twrp
after reboot the phon don t rebot just bootloop i try unstaling stock image with toolkit evry think is ok but the same brob just bootloop i can enter in fastboot mode but not in stock recovery
samone know the solution ?or my fhone is dead
Click to expand...
Click to collapse
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.

v12xke said:
Since your phone is unlocked, I would try to flash a full Google image using the included flash-all.bat (instructions are on the same page as the image downloads). Not being able to access recovery mode may indicate a more serious problem.
Click to expand...
Click to collapse
do you think my phone still alive

leroilion02 said:
do you think my phone still alive
Click to expand...
Click to collapse
Too early to tell. Google intended the image files to be a foolproof way to "reset" the phone to factory stock. This is the first thing you have to try. Set up ADB/Fastboot on your PC and use it to communicate with, and send commands to your phone.

I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.

jhs39 said:
I've gotten myself into the same situation a few times and flashing the full stock image with flash-all.bat command has always gotten me out of it so far. After I'm back on stock I just start from scratch again and flash recovery, custom rom and root.
Click to expand...
Click to collapse
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme

leroilion02 said:
i flash the full factory image with fastboot all is ok after fishing just bootloop i don t know what is the probleme
Click to expand...
Click to collapse
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?

v12xke said:
fastboot FORMAT (not erase or wipe) userdata, cache and system capturing the screen (or text from each command). Try flash-all.bat again. Which image are you flashing?
Click to expand...
Click to collapse
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond

leroilion02 said:
the last android 7.1.1
when i flash with flash-all.bat the note progresse he stop with message fichier not fond
Click to expand...
Click to collapse
do you think my phone can reboot

leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Can you enter recovery mode after all you have tried? Or do you only have access to fastboot in broader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
just fastboot

leroilion02 said:
do you think my phone can reboot
Click to expand...
Click to collapse
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?

v12xke said:
I don't know, you're providing conflicting information. What happened when you fastboot formatted each of the 3 partitions?
Click to expand...
Click to collapse
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist

leroilion02 said:
when i flash the phon on fastboot al is ok the bootloader after the radio after the system after vendor all ok the phon just bootloop
when i try flash with flash-all.bat the procedur don t progress just the radio and bootlaoder after just error message files don t exist
Click to expand...
Click to collapse
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system

v12xke said:
No. Fastboot FORMAT the 3 partitions (for the 3rd time). Capture the response from each of these commands:
fastboot format userdata
fastboot format cache
fastboot format system
Click to expand...
Click to collapse
ok i try tomorow and i tell you the Result

mi a1 bricked

i got bricked my mi a1
i unbricked via test point after that ohone reboot in wizard
i read flashung persist fix..but i cant do it..phone dont accept that command
so i decide to erase system vua fastboot erase system_a and _b
after that i flash many rom and i only get m i logo and reboot..
i try edl and fastboot method both with same result
any idea how can i unbricked and get it wqorking back again..its new phone
just work for 2 days and 3 turned off lol
please help me to recover

I have the same problem, did you find a solution?

AgustinPatatas said:
I have the same problem, did you find a solution?
Click to expand...
Click to collapse
did you try to get into fastboot mode and use the MiFlash to install a new rom on it? often works

erickxd said:
did you try to get into fastboot mode and use the MiFlash to install a new rom on it? often works
Click to expand...
Click to collapse
I try flash with Mi Flash the last update but the screen of "Android One" is displayed and it is restarted, without being able to enter in the system. It stays in a restart loop.

AgustinPatatas said:
I try flash with Mi Flash the last update but the screen of "Android One" is displayed and it is restarted, without being able to enter in the system. It stays in a restart loop.
Click to expand...
Click to collapse
you don't need enter in the system's phone to do this. just use mi flash on your pc with your phone connected in fastboot mode. search about using MiFlash, it's simple

erickxd said:
you don't need enter in the system's phone to do this. just use mi flash on your pc with your phone connected in fastboot mode. search about using MiFlash, it's simple
Click to expand...
Click to collapse
That's just what I did, what I mean is that when I finish flashing the most recent rom, the phone turns on after finishing the process Mi Flash and the phone starts to restart itself without being able to enter the system and I have to resort to flashing the rom "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" to be able to enter the system again, however does not recognize the sim and if I try to update from the option offered by Android the phone starts to restart itself, same as the aforementioned

Moto g4 plus recovery boot loop...

Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...

Eduadc said:
Hi guys. Few days ago I unlocked the bootloader of my Moto G4 plus, install twrp recovery and root the phone. Then I made the mistake of trying to install an update from OTA and since that day it is impossible to start the phone normally. It always starts in recovery mode, then I must go to restart to start in fastboot mode and next, select start to be able to use it. I reinstall the latest version of the recovery twrp and the ROM of LineageOS but nothing changes. Can someone tell me if there is any console command I can execute in the phone to start normally?
Thanks for your time...
Click to expand...
Click to collapse
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

strongst said:
Please refer here, you bricked your device by taking ota while on custom recovery https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.

Eduadc said:
Thanks for your answer. I don't understand the reference. I can flash any firmware without problem.
I looking for a commands to repair the boot because I have a boot loop with recovery mode.
I can use the phone but only across: recovery > restart > bootloader this restart in fastboot mode, next I select "start" And the phone boot with Android....
I whant to start in Android directly... I whant (if exists) any console command or any solution to fix the boot problem.
Click to expand...
Click to collapse
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear

strongst said:
Oh, then you can try using these commands through fastboot:
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
Thanks for your reply again. I tried the commands but nothing changes....

Eduadc said:
Thanks for your reply again. I tried the commands but nothing changes....
Click to expand...
Click to collapse
If your Issue resolved..then tell me ...how you did it....i am also stuck on that bootloop on recovery mode