Used odin and installed magisk. Its fully rooted.
Any atempt of installing twrp with odin( installing on AP option) makes all rom to be erased.
Installed twrp cant use backup or flash anything because of errors.
Installation through fastboot is impossible because it gets stuck in "entering fastboot mode"
Help me guys
Related
I've used numerous guides and attempted to flash EITHER TWRP or CWM using fastboot. The process appears to work without any issue, but when I try to reboot to recovery, I get the lovely droid with the red icon.
For some reason, TWRP manager crashes immediately when I attempt to initiate an install of the recovery from within the app (I'm now on the rooted ROM from Bad Boyz).
Am I missing something obvious?
Thanks
I got the same problem.... solutions, tips ?...thank you
#parked
I had the same problem. What you need to do is download the TWRP image and use the Nexus Root Toolkit to flash it (or fastboot commands if you're familiar with them) . First launch Advanced Utilities and then select Recovery under Fastboot Flash. In Other... you select your downloaded TWRP image, making sure the option Also flash "perm-recovery-signed.zip" is activated.
I have a Samsung Galaxy Note 3 with Android 5.0 (Lollipop) and Rooted.
I've been trying to flash CWM and also TWRP without success.
I've used all sorts of methods, Odin, ROM Manager, Nandroid Mgr, Flashify, ADB, ... with the same results:
The flashing always seems to be successful but when rebooting into the custom recovery mode, the custom interface doesn't appear but instead, the system tries to boot into what it appears to be the stock recovery's three first colored text lines for a few seconds and it reboots into a loop until I remove the battery.
Then the only way to get back to the system is boot in download mode, flash either CWM or TWRP with Odin (although I know they won't actually work) and it then reboots into system.
Then I restore a backup of the stock recovery that I luckily made with Flashify and at least the stock recovery works.
(BTW, when the stock recovery has been restored, if I go to ROM Manager both CWM and TWRP are listed as "Already Installed" ... I thought that when you flash the stock recovery, any previous custom recovery is removed )
Any help would be appreciated
Backgrond: Fresh new device. I unlocked bootloader through the all in one toolbox here (http://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711) to unlock bootlaoder successfully and install twrp ( I chose this version TWRP 3.2.1 Blu Spark OP5T).
I unlock my bootloader successfully and then tried to install superSU through twrp. I realized at the time of TWRP installation, that I didnt have SUPERsu on my device so I booted up my phone, downloaded Super SU from (http://www.supersu.com/download) and then went back into recovery mode. I was able to install the file through twrp but now I'm stuck on the OnePlus Screen.
On the toolkit screen there was a message saying
"if you flash a modified recovery and you dont root your stock rom (or flash another rom) you will brick you phone.
Is that what I did? Should I flash a custom rom?
I can access fastboot, recovery, etc and use adb sideload. I thought maybe I installed the wrong super user file so I flashed a new one through adb sideload (this file SR5-SuperSU-v2.82-SR5-20171001224502) but that didnt do anything either.
What should I do?
So, I successfully unlocked the bootloader, then followed the instructions to install TWRP (which worked initially because I was able to access TWRP immediately after flashing). But how to I access it again once I'm back in the OS? When I click reboot to recovery it always reverts back to the stock recovery. I'm still on the stock OS, but I just assumed once TWRP was installed I could boot into it from there. What am I missing?
Solved the problem by getting Magisk installed and using Flashify app to flash the downloaded TWRP img.
@brGabriel just use the fastboot commands as mentioned by manojpawarsj12;
fastboot flash recovery twrp.img
Don't mess around with Flashify, it's dated and a good way to brick your phone...
I have an ATT LG V40 on android 8.1. The phone is already rooted and has magisk installed. I have been unable to get TWRP installed so I can flash a custom rom. It seems that being on android 8.1 is causing issues, but I am not really sure. I followed this guide: https://forum.xda-developers.com/t/twrp-lg-v40-judypn.3970111/ and when I send the comand to flash TWRP in the command window is says the flash is finished and my phone boots up, but it doesn't seem to do anything. Any help would be greatly appreciated, thanks.
You need to use LGUP to get to 9
Noob question but did you installed and tried magisk manager(I bet you already have) and flashify(searchable on Google) (magisk manager grants root to flashify and flashify installs twrp from storage)?
Are you certain that you're booting in to recovery? Many phones have an advanced reboot menu option on the developer settings. If yours doesn't I recommend an app like Simple Reboot.
If you're not certain that it's installing the recovery correctly have you just tried installing TWRP.zip from Magisk?
dn.34 said:
I have an ATT LG V40 on android 8.1. The phone is already rooted and has magisk installed. I have been unable to get TWRP installed so I can flash a custom rom. It seems that being on android 8.1 is causing issues, but I am not really sure. I followed this guide: https://forum.xda-developers.com/t/twrp-lg-v40-judypn.3970111/ and when I send the comand to flash TWRP in the command window is says the flash is finished and my phone boots up, but it doesn't seem to do anything. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Which 'command', specifically, are you typing in when you say you are 'when I send the command to flash twrp'? The only command in those directions are to boot twrp, not flash it.
After you boot it, then you need the advanced section so you can recovery ramdisk, which will inject twrp into the current boot partition (and it keeps boot intact).
If you want to use current aosp roms, then follow the 'metadata' sections as you'll need that version of twrp for those roms.
cheers