Hello,
Me and a friend (who I by chance met on irc with exact same phone & issue), have been trying to install a Custom Recovery mod for him to be able to flash 4.4.4 and 4.4.2, while I have been trying to install Cyanogenmod 12.1. I can confirm that Cyanogenmod 12.1 has worked on my friend's previos S4 Mini.
Details:
Samsung Galaxy S4 Mini LTE i9515 with KNOX Bootloader
The Problem:
The flashing of the Recovery ROM is successful through both Heimdall and Odin, but when rebooting the phones go back to stock KNOX bootloader/recovery.
What we Have Tried:
Different ROM versions (many)
Using different Odin-like programs (Heimdall, Odin)
Different Operating Systems (Linux, Win7, Win8, Win10, Mac)
Different USB Ports (USB1.1, USB2, USB3)
Different recovery ROM's (CWM - All versions, twrp, openrecovery)
Hello guys, I'm the Friend from the messsage above. Any help would be highly appreciated!
Related
Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
FYI;
Just flashed Phils modification of CWM which works successfully on the N7105T without the glitch. However the phone still cannot boot into a custom N7105 ROM successfully.
I tried to do the below to no avail;
Using Phils Recovery, flashed Paranoid Android & applicable GAPPS. After this I flashed the N7105T Telstra Modem using Phils Recovery. Rebooted phone and the phone turns on and screen 'glitches' as described earlier.
I also have the same problem
Note2-CWM-6.0.4.1-GT-N7105t
Jonnit said:
Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
Click to expand...
Click to collapse
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
slysurfer said:
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
Click to expand...
Click to collapse
Follow all steps. - http://androidxda.com/root-samsung-galaxy-note-2-n7100t.
Now I updated to stock telstra 4.3, using odin v3.09. Firmware from samsmobile. worked first go and many times since
Then I flashed philz recovery - ( philz_touch_6.15.4-t0lte.tar) with odin v1.85 - untick auto-reboot and once installed just hold vol up/home and power to get to philz recovery - Then to root, download and extract saferoot = http://forum.xda-developers.com/showthread.php?t=2565758 - it works on GT-N7105T ( just a N7105 really once you get a message on your phone about allowing USB ADB debugging / SU permision, all is good. I started the bat file again after i got the su message prior attempt and it completed. Then I updated supersu in play store then opened and updated binary in supersu and restarted phone. Just installed CWM and installed cm touch recovery app granted permissions, like on 4.1.2. phone is free now. will install roms tonight. any issues i will update this.
Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop
An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.
Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.
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?
Hi there
I'm hoping someone can help me out with a few questions as it's been a while since I've played around with a samsung device. I have a rooted s4 mini (i9195) (I rooted it a long while ago), on Android 4.4.2. I want to do a clean flash. Do I need to do an odin flash of anything before flashing to Resurrection Remix? (As this rom is Android 7, and last I remember, when upgrading android versions there's a few extra steps?)
Speaking of Odin, will the standard Samsung USB drivers be fine for using odin?
Also I noted it said in the install instructions for Resurrection Remix to flash TWRP from this thread but it says in that thread please do not use Nougat roms with TWRP at the moment? Surely I shouldn't be flashing that TWRP if it literally says dont flash it to use with Nougat roms?
Thanks
Hi there. I made exactly your same steps time ago (from stock KitKat 4.4.2 to CM13), so it's simple: you just have to prepare 1) TWRP; 2) The ROM you'd like to flash. 3) Odin for flashing TWRP. Old Samsung drivers are more than good, this is all you'll need.
1 - go here and download the 3.1.1-0 TWRP for LTE (don't worry, it works flawlessly even if said that it doesn't on Nougat, this because OP should be updated by the developer but it'll be done when he'll have some free time, i used it for everything and i ensure its efficient).
2 - extract from the zip file the twrp.img file, then flash the twrp.img by Odin; open Odin, click on recovery on low-left corner and browse to the img file, then flash it.
3 - reboot to TWRP, do a stock rom backup and backup even all your data that you'd like to keep, TWRP backups keeps everything except the various documents, MP3s, images, ecc. and if someone should go wrong while flashing a custom rom, let's have a way to restore the actual situation. Then to have a clean flash, be sure to wipe data by TWRP menu (the 3 selected partitions are enough, don't wipe nothing else).
4 - to install a custom rom, now that you're ready to start, follow instructions that you'll find in rom's thread in OP
Happy flashing!
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