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?

Unbricking after a hard brick not working out.

So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.

yawarkhalid said:
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
Click to expand...
Click to collapse
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.

tnsmani said:
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
Click to expand...
Click to collapse
Gave this a shot. Not booting up again. Goes to blank screen with white notification light.

Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.

yawarkhalid said:
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
Click to expand...
Click to collapse
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.

tnsmani said:
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
Click to expand...
Click to collapse
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.

yawarkhalid said:
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
Click to expand...
Click to collapse
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.

tnsmani said:
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
Click to expand...
Click to collapse
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:

yawarkhalid said:
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
Click to expand...
Click to collapse
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.

Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/

jeffrey268 said:
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Click to expand...
Click to collapse
ummm thanks jeffery. But that tool is exactly what i've been using and what isn't working for me in ways i mentioned above. Thanks though.

tnsmani said:
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Click to expand...
Click to collapse
Gives me the error, "Unlock device to use this command"
I am able to flash rom via MSMTool, it even dash charges and all. But I can't boot into the system. It gets stuck in OOS animation while booting. Been at it for 3 days. Can it really be a hardware issue if my bootloader and recovery both are working?
Lastly, do you have any way I could unlock the bootloader without system permissions?

Putting an end to this madness. after 4 days in front of my laptop. Had a remote session with a OnePlus tech support team. Discarding my phone unfortunately. Thinking of shifting to a Xiaomi Redmi Note 5 Pro since I can't afford a OnePlus 5T anymore. Thanks to everyone who helped. This thread can be closed now.

Unable to Install any custom rom.

So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?

So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?

JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?

SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.

JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.

SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.

JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.

SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.

hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:

stuck in bootloader/recovery, can't flash ROMs.

Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?

You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?

Custom Rom Flashing Error: to flash additional zips please reboot recovery to switch.

So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.

i face the same problem

I have oneplus 7 and have the same issue

flvckoo said:
So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.
Click to expand...
Click to collapse
same problem here im wasting so much time triying to figure out how to repait the partitions or something, because somehow I had a partition B and now doesnt exist lol.

Hey, mates!
Anyone able to solve this?
I flashed TWRP and Magisk successfully, but every time I try to flash a custom rom it gives me the message "to flash additional zips, please reboot recovery to switch to the updated slot".
I'm on a Xiaomi Mi A2 Lite, btw.
Thanks in advance for any help!

ATTENTION!
I found a solution to the problem, all you need is just to install another recovery, I installed Orange FOX. And you know what? Everything worked. So just install via SD card Orange FOX and be happy!
Thank you, your Yasude!
My phone: XIAOMI Redmi note 10

OF does slot switching automatically? I managed once boot and install OF, wipe, flash SYberia, change slot, anti encryption and magisk, reboot to system. Unfortunately never work with lineage. But OF has options disable encryption and some measures against (i dont like them - own ota recoveries which always make a mess)
LOS dmesg complaints about damaged GPT and cant find many files even after edl flashing with original FW.

just install orange fox