I actually managed to fix it by flashing cf-autoroot in odin and it booted up fine after that
Hi,
I tried to flash a Lollipop ROM on my N2, but TWRP (2.6) only says "FAILED". Also wiping/formating everything doesn't help so I tried to flash TWRP 2.8.6 as a .tar with Odin. It succeeded and reboot but showed only the TWRP startscreen. Installing a 5.1 PA zip with odin (unzipped and zipped to .tar) also doesn't work, it just failed. And trying to install TWRP again only loads a long time and then failes.
Anybody any suggestion? It's just my second device, so it's not that neccessary, but it could be nice if I crashed my Note 4 to have a backup device^^
To Admin: Please move this thread into the Q&A section of the international Note 2. Accidentally posted here.
Hi. I have problem with TWRP installation on Samsung Galaxy Tab 3 10.1 (GT-P5210, soft: SAMSUNG Official). I tried to install TWRP, but when I flash it with Odin, I have stock recovery. I found somewhere that auto-reboot should be unchecked, so I tried once again and... still the same problem.
1. Should I root my tablet before install TWRP?
2. How I can solve this?
TWRP source: http://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-12-1-t3100789
Sorry, for my English.
Dear all,
I would like to know how I can install TWRP on a samsung galaxy s4 mini?
- S4 mini 4G LTE (international version serranoltexx)
- Odin latest version
- I use the serranoltexx variant of TWRP .md5
I use Odin latest version and the TWRP version of XDA: But every time I try to get into TWRP get stock recovery, with FAIL:
First I still had the set of warrenty bit recovery fail. But that is now gone.
Someone who can help me? This is because it wants to install LOS on it, so it works better than the stock ROM.
Flash TWRP
I also had the same problem, but i solved it by flashing CWM first, and then, using CWM, i flashed TWRP (custom-twrp-3.2.0-1-serranoltexx-STABLE-signed.zip). With it i flashed LineageOS 15.1 (lineage-15.1-20180222-UNOFFICIAL-serranoltexx.zip) with no problem.
Root with Kingoroot and flash .img file with Flashify
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Similar problem
-- sorry, wrong device, please disregard. I can't seem to find a delete button. Newby passing through.--
I have not previously installed custom ROMs on my devices. Now I am also trying to install Lineage 17.1 on my Galaxy Tab Pro 12.2 and thus far have been unable. Maybe your experience is similar to mine:
I used ODIN to flash the latest TWRP to the boot loader and booted to recovery (so Samsung system boot would not replace TWRP with stock recovery) and TWRP recovery is stable. In TWRP, I installed SuperSU from a zip file on the extSD. After booting into the stock system, I was prompted to finish rooting, which I did using TWRP. Once I was able to reliably boot into recovery or normally (stock system), I booted to recovery and made a backup of my stock image. I have reliably flashed Samsung stock image, which boots to the initial setup process, and restored by backed up image, which boots to the previously configured state.
At this point I downloaded the Lineage 17.1 image zip file onto the extSD card and tried flashing it from recovery. While unzipping the image, the recovery screen shows a couple of error messages, along the lines of image is 'for device v1awifi but this device is .' and flashing fails. I believe at this point rebooting hangs with the Samsung logo animation, but I have been able to boot recovery and restore my previous rooted Samsung stock state. Custom ROM Manager confirms my device Codename is v1awifi.
Is this what you experienced? If not, how is your experience different? Can you describe your approach, what steps you've taken, and where the process does not go as expected?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
where did you find 17.1 for tab pro 12.2?
ScrooLoose said:
Hi all,
While I have successfully installed Lineage 14.1 and the GApps 7.1 on my Tab Pro 12.2, I can't get it to install Lineage 17.1. I had issues getting 14.1 onto it until I loaded a new bootloader file through Odin (BL_T900XARBOJ1), but I can't seem to find a bootloader that will let me install Lineage 17.1. Does anyone have any suggestions?
Click to expand...
Click to collapse
So you are on TWRP 3.4.0-0?
Although I own a P900 I had problems flashing 17.1 before updating to 3.4.0-0.
And for 17.1 I used BiTGapps instead of opengapps for the last didn't like it.
Does anyone know how to modify this note 12.2 LOS 17 zip so it can be flashed on tab 12.2? https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20201221.4152395/
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Dusterrr said:
I was able to get it installed on my Tab pro 12.2 T900. It gets stuck on the bootup lineage logo screen. I guess android 10 on this device is too good to be true.
Click to expand...
Click to collapse
I had the same issue. You need to flash 17.1 over 14.1.
rojorojorojo said:
I had the same issue. You need to flash 17.1 over 14.1.
Click to expand...
Click to collapse
I tried this and it isn't working. Any suggestions? Can you help me out? Nevermind, its working this time! I tried many times, but the final time I didn't clear cache and it worked .
NVM not working again...
I clean flashed lollipop with odin, then twrp, then lineageos14.1, configure it, and dirty flashed 17.1, and at the moment it's working. No root installed.