Database Users

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode

You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it

Don't do what rosswaa said

Why not?

What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).

I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now

Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Obviously try what green says first, if it works then happy days

first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx

SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

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

Soft-bricked P9 Lite (VNS-L21)

Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad

shxtov said:
Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad
Click to expand...
Click to collapse
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best

vdp1nnab said:
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best
Click to expand...
Click to collapse
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.

shxtov said:
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.
Click to expand...
Click to collapse
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?

vdp1nnab said:
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?
Click to expand...
Click to collapse
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.

shxtov said:
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.
Click to expand...
Click to collapse
Okay that helps a huge load. What you need to do is flash the nougat ROM again. You need to put the rom files into the root of ADB install location (program files/ Minimal ADB and Fastboot) in zip format. If I'm not mistaken you have update.zip and vnsXXX_Full_data (or something similar).
Then flash the firmware using this command once your connected in fastboot. I'm not sure the command. But I did some googling and can't find a solid answer. I remember doing it but I don't remember the command line.

Phone bricked

I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening

advanced_gamerBR said:
I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening
Click to expand...
Click to collapse
Just copy the ZIP file of the ROM and flash, as you dos when you first installed. Maybe just wipe caches

advanced_gamerBR said:
I was a running my Redmi note 7 with DerpFest rom and with Ofox custom recovery
The phone suddenly got into a bootloop and now I can only access the fastboot screen (not even the Custom recovery screen)
How can I proceed to reinstall the sistem and the Custom Recovery?
I've already downloaded Minimal ADB and fastboot ulitily to make things faster
Edit: Also, I couldn't get the MiFlash program working, some errors are happening
Click to expand...
Click to collapse
Try to reflash the recovery with fastboot first. Need to have xiaomi usb drivers installed to can use adb/fastboot connection. When the phone is in fastboot mode connect with a good (original) USB cable and check the connection with "fastboot devices" command in cmd/powershell window. Extract and use "recovery.img" from latest orangefox zip file. Flash to phone using "fastboot flash recovery recovery.img" command then reboot holding together "Volume Up + Power" until you see the MI logo, release "Power" button but keep pressing "Volume Up" until you see the recovery. When you have working orangefox recovery, try to flash new rom. More information about driver/fastboot/recovery here (skip "unlock the bootloader" part): https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
The MiFlash program issue can be caused by missing/wrong xiaomi usb driver, if you will have answer from "fastboot devices" command (phone detected), can try the MiFlash again, just be careful: DON'T LOCK the BOOTLOADER. Good luck.

Trying to flash TWRP but no success (stuck on Fastboot mode)

I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.

You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.

Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.

How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader

Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?

Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there

Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?

Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.

smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then

Curious did you have the twrp file in same folder as adb and fastboot?

smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply