Develop Bugs

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3

@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.

noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.

I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

S4 mini plus patching system image unconditionally error while upgrading rom

So I had my S4 mini with custom 12.1 rom . Danil_E71 the developer updated to a new version. When I downloaded it and tried to install no wipes no anything coming from same rom I get a message in twrp saying patching system image unconditionally and then it freezes. If I remove the battery and reboot twrp the /system is unmounted and can be mounted only via restoring backup . Since this hasn't happened to anyone else using this rom might this be something wrong in my model ? So far I tested Cm12.1 --> Cm12.1 rom update failed
Stock rom --> Cm12.1 through wipes etc failed again what can I do ? My model is the plus quad core version but I think its irrelevant in my case

I have a problem with flashing Lineage OS nightly 14.1

Sorry for my bad english
I had installed CWM custom recovery and I had rooted LG D-722 on android KK.
I downloaded zip file with Lineage OS nightly 14.1 from 2017-03-29 09, version from 2017-04-05 09 didn't work: error status 7.
I flashed the Lineage OS (before that I wiped data and I created backup)
The software was successfuly flashed but I didn't installed gapps (error: You don't have android 6.X.X).
I rebooted my LG and it stuck in boot with a error booting error boot certification verify. I flashed android KK by LG Flash Tool and phone is working.
My question: Where I made a mistake? How install the lineage OS for my phone?
Please help

Hey
First if all you need to be asure that your bootloader can boot android N or v7.
After flashing Lineage, you have to flasht the proper gapps. Before rebooting the device

Can´t install TWRP / Lineage on Lg G Pad 8.3 V500

So a couple of months ago, I installed the official, yet korean, firmware (Android Version 5.0.2) on my Lg G Pad V500.
Now I wan´t to install Lineage OS but I always fail to install TWRP.
I followed this guide and also tried the guide from lienage os. I flashed the proper TWRP version with the official TWRP App and the app claimed that it was successfully.
Here comes the problem:
I can´t boot into recovery mode.
I tried it with adb "adb reboot recovery" but ended up by the LG Logo and a message in the upper left corner telling:
secure booting error! cause: boot certification verify
Click to expand...
Click to collapse
I also tried the key combination while booting (POWER + volUP + volDOWN) but that didn´t work either.
Here are some Specs:
Android version: 5.0.2
Kernel version: 3.4.0
Build Number: LRX22G
Software version: V50030a

Which TWRP Version did you use? I have a v500 too and was running fine with twrp 3.2.2.0. I yesterday updated to twrp 3.2.3.0 and get the same error while trying to boot into twrp. I guess 3.2.3.0 is the problem.

I'm also getting that since latest updates... Spent 3 hours trying to boot into recovery only managed it once and clearing cache didn't fix it. Haven't been able to get in again...

Tried with TWRP 3.2.2-0
meistadieb said:
Which TWRP Version did you use? I have a v500 too and was running fine with twrp 3.2.2.0. I yesterday updated to twrp 3.2.3.0 and get the same error while trying to boot into twrp. I guess 3.2.3.0 is the problem.
Click to expand...
Click to collapse
I tried version 3.2.2-0 but go the same message when trying to reset.

Which rooting method did you use? I bought mine v500 used and twrp was already installed, so I hadn't to deal with rooting and all that stuff. I recently read a lot about and think I will have to try different method to get twrp running again. But if you have hints for me, I would be thankfull.

I vaguely remember that you had to use 4.4 kitkat base for root & TWRP, not 5.x. Don't know if this still apply.

meistadieb said:
Which rooting method did you use? I bought mine v500 used and twrp was already installed, so I hadn't to deal with rooting and all that stuff. I recently read a lot about and think I will have to try different method to get twrp running again. But if you have hints for me, I would be thankfull.
Click to expand...
Click to collapse
I used KingoRoot

Can't install any rom

Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"

shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.

If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.

Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.