Related
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
Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?
Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.
Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?
1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?
trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode
Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.
So, I tried unlocking ZE520KL with ASUS Flash Tool, and after 25 mins of flashing image I disconnected the device. Now, the device only boots into factory mode and recovery mode. Bootloader doesn't work and internal storage isn't mounted when I use the option Install update from SD card, but MicroSD works.
I had the latest update installed before this happened. I tried the latest firmware from the site and installed it via recovery but it shows signature verification failed. The same thing happens if I try to delete the first few lines of the updater script in the META-INF folder.
So help me guys, which firmware should I use and how should I use it? Even ADB sideload didn't work.
Try fastboot flash 'recovery.img', the same version from a firmware you're about to flash than flash the zip from recovery
sanctitude888 said:
Try fastboot flash 'recovery.img', the same version from a firmware you're about to flash than flash the zip from recovery
Click to expand...
Click to collapse
Thanks man. I figured it out though. I flashed the stock MM ROM and it worked. BTW, are there any ports of the stock camera? I really need the stock camera
Hi, my Zenfone 3 is stuck on bootloader screen and reboots again and again ... unable to use my fone
ruchikapoor said:
Hi, my Zenfone 3 is stuck on bootloader screen and reboots again and again ... unable to use my fone
Click to expand...
Click to collapse
Can you enter and stay on fastboot steadily? You need to obtain the whole stock ROM along with fastboot and recovery image from the very same package. Fastboot flash the fastboot and recovery image then flash the ROM from recovery.
Hello and thanks for inteterest to help. (My phone Redmi 2 Prime)
So to the point, i have my phone installed custom ROM. And today when i try to reset factory, it stuck in the MI Logo (Show and then turned off). So i forgot to flashing the twrp again last time, so i left it without any recovery. The only way is repairing it with Fastboot and installing TWRP. So i start installing all driver and flashing. But, when i want to flash twrp to my phone, it keep showing me this
fastboot flash recovery recovery.img
flashing 'recovery.img'
FAILED (Data Transfer Failure(unknown error)
DONE! 5.8 sec
But it doesnt installing any recovery. I have installing MiFlash driver. Is there any driver that i should install again? Or anything that i can do? Also my PC doesnt read my phone storage at all, it doesnt show in the explorer, but can read "my phone" and my phone model. And I'm using USB 2.0. I also have try USB 3.0 but it doesnt work too.
Any help would be appreciated. Sorry for the long post, eh?
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
dabakale said:
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
Click to expand...
Click to collapse
Thank you for replying
So i've try it, but why its stuck at 'downloading boot.img' for 2 hours?
Can i download the boot.img manually? If yes, what should i download?
Can you share a photo of error.
Or you can try miflash to flash stock rom. Then you try to flash twrp. I suspect there would be something wrong with your recovery partition.(i also had similar problem while flashing different roms.)
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Egalito Rieans said:
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Click to expand...
Click to collapse
Try this method
[No More Errors] [Fastboot Rom Flashing] [Direct Method]
Hi all, Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error ;). I tried many things but no luck. Then i followed direct method and that worked...
forum.xda-developers.com
So long story short I recently decided to install stock kernel on my Nexus 6P. I flashed boot.img from oreo firmware using twrp. Accidentally I flashed it into system instead of boot. Now system is corrupted stuck on google logo. But USB debuging is enabled. so I tried to activate OEM using fastboot but it says unknown command. Later on I try to format, wipe all partitions, repair file system using twrp still no success.
Did I break my phone completely?
vu1ture said:
So long story short I recently decided to install stock kernel on my Nexus 6P. I flashed boot.img from oreo firmware using twrp. Accidentally I flashed it into system instead of boot. Now system is corrupted stuck on google logo. But USB debuging is enabled. so I tried to activate OEM using fastboot but it says unknown command. Later on I try to format, wipe all partitions, repair file system using twrp still no success.
Did I break my phone completely?
Click to expand...
Click to collapse
No, I don't think you completely broke your phone. I would try reflashing using fastboot. Or you could try an OTA update to return it to stock.
No. You just need to reflash stock system.img using stock flashing application for your fone and nothing else. Just do this in edl mode.
To get there, turn fone off completely while unplugged from pc. start your stock flashing application, and load your stock rom, once it verify's, you should be able to select system.img ONLY, dont flash any other img you see for now.
Hit start in this application, then plug fone into usb, watch what happens
Write back ?
Edit The No is to the OP, not to disagree with above post
Pachacouti said:
No. You just need to reflash stock system.img using stock flashing application for your fone and nothing else. Just do this in edl mode.
To get there, turn fone off completely while unplugged from pc. start your stock flashing application, and load your stock rom, once it verify's, you should be able to select system.img ONLY, dont flash any other img you see for now.
Hit start in this application, then plug fone into usb, watch what happens
Write back ?
Edit The No is to the OP, not to disagree with above post
Click to expand...
Click to collapse
you are genius. thank you so much