Related
Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix
slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..
carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.
Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.
You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.
I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?
I don't recommend using CWM, only TWRP.
After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.
Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.
Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Molex69 said:
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Click to expand...
Click to collapse
I guess you didn't read the OP of Oxygen Os correctly,he clearly mentioned that this 'Tuga Power Recovery' is patched to work with Oxygen Os's firmware and one should not flash any other recovery.Now,what you can do is this,
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view?usp=drive_web
> Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Avoid using any Antivirus program while doing this as they might give false alarms.After this you'll be restored to TWRP then you can flash any rom you want.The reason due to which you weren't able to find 'TugaPower Recovery' on TWRP page is because this is an Unofficial Recovery.
Question
What does the program do with the OPO?
If you are familiar with fastboot commands, this method should work. Had my OnePlus in the same situation last night messing around with Efidroid. Phone was bootlooping. Efidroid boot menu as well as recovery mode were both inaccessible. I had tried several other things but none worked for me. *CAUTION: this method did ERASE my userdata.* I downloaded a fastboot-able stock full firmware zip, then manually reflashed device. My beloved OnePlus is no longer my daily driver but still my fave device to experiment with so I just used COS 13.1 file. After full reboot, I downloaded and flashed official TWRP. Device is fully functional again, but without OOS installed.
Molex69 said:
What does the program do with the OPO?
Click to expand...
Click to collapse
It'll change your firmware and alter your recovery to a functional TWRP.You'll lose Oxygen Os after doing this.Though you can use this anytime when not being able to flash TWRP.
What should i do
Thanks a lot thanks to the method you told me my OPO has recovery again really thanks, but I have a question, I still in the TugaPower recovery, should I flash the stock recovery or the newest version of TWRP?
Because I do not know if flashing again the TWRP will happen the same
I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .