I have a new i9305(about a month old, from tmobile if that matters). It came running 4.1.2 which I updated OTA to 4.3 official. I recently rooted, using CF via Odin. I tried to boot phone into recovery but the screen went blank. Phone doesn't cut off but it's blank as if is off. I reinstall stock recovery and it runs. I've tried to install 3 different recoveries via Odin(CWM, TWRP, forgot 3rd) but they all have the same problem. Rom Manager doesn't help and it also says I have CWM 5.x.x.x installed even when I flash stock recovery.
I've searched for a solution on here and other sites and this problem seems to be unique. I would like to know if there's a way I can either install a custom ROM without custom recovery or if I can solve this problem
Install cf root with odin .
Boot ur phone.
Go to play store and get supersu update it.
Get ROM manager from play store install it and install custom recovery from there.
Choose your model in ROM manager.
Search for cwm-recovery-6045-i9305.zip if you install a kitkat ROM flash that first.
Sent from my GT-I9305 using xda app-developers app
toeterbaas said:
Install cf root with odin .
Boot ur phone.
Go to play store and get supersu update it.
Get ROM manager from play store install it and install custom recovery from there.
Choose your model in ROM manager.
Search for cwm-recovery-6045-i9305.zip if you install a kitkat ROM flash that first.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
So it's working now, I first unrooted my phone and reflashed cfroot via odin. and I tried ROM manager again but chose the gs3(metro pcs)... and it worked... maybe i messed up somewhere when i first rooted it, idk.
Now that there is a root for kitkat, I was interested in upgrading. Problem is, I stayed on jellybean rooted (LS995 - SPRINT) and installed TWRP recovery and therefore could not install the OTA. Is it possible to remove TWRP, install factory recovery and UNROOT, then accept the OTA or do I have to use the brick recovery method with the .tot files although I'm not bricked and phone is running fine?
Have to uproot completely using LG Flash tool with .tot files then upgrade to KK, but there is no custom recovery (as far as I know I think)
Sent from my LG-LS995 using XDA Premium 4 mobile app
I was on stock touchwiz android kitkat on my s4 acrive int .. then i installed cwm and rooted using cwm recovery .. when i updated to official touchwiz lollipop via odin i tried to reinstall the cwm but for some reason it can't be accessed whenever i boot into recovery the stock recovery appears instead .. also i tried to use cf auto root (which worked for me before the update too ) but it doesn't work too . Also when flashing both the recovery and the root using odin it says pass but none of them is installed though .. is their any other way to install cwm or at least root the phone while on lollipop
Sent from my GT-I9295 using XDA Free mobile app
Here's all you need
http://forum.xda-developers.com/showthread.php?p=56955843
Working method for Kitkat 4.4x or Lollipop 5.0.x
[emoji6]
Pay attention to what you need to do immediately after flash custom recovery over stock.
I'm having a bit of trouble trying to get a Custom recovery working in my phone. It's a SM-N920C International (UAE) version. If I flash Arther's Philz Recovery or TWRP both of them get stuck in "Samsung Galaxy Note 5, Recovery is not SEandroid enforcing". Usually it should start right away but even waiting like 10 minutes it doesn't start. I can use the phone normally and even flash stock roms with ODIN. It just doesn't want to start any Custom Recover I throw into it. Any thoughts?
galaxynote2 said:
I'm having a bit of trouble trying to get a Custom recovery working in my phone. It's a SM-N920C International (UAE) version. If I flash Arther's Philz Recovery or TWRP both of them get stuck in "Samsung Galaxy Note 5, Recovery is not SEandroid enforcing". Usually it should start right away but even waiting like 10 minutes it doesn't start. I can use the phone normally and even flash stock roms with ODIN. It just doesn't want to start any Custom Recover I throw into it. Any thoughts?
Click to expand...
Click to collapse
Provide info which OS are you on mm or ll?
Sent from my SM-G935F using Tapatalk
I have the same issue on a 920G with MM N920GUBU2BPC2_N920GUUB2BPC2_TPA installed TWRP 3.0.0.0 with ODIN but it will nto load just stuck on Note 5 logo if i reboot the phone starts normally.
aukhan said:
Provide info which OS are you on mm or ll?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Oops, I've forgot that! I'm on Marshmallow
Btw I realized that I was installing LP recoveries in MM so I flashed the lastest TWRP build and now it works. The new problem is that I managed to root it but even if SuperSU works I can't manage to modify system files and busybox doesn't work either. I've flashed Dr.Ketan experimental MM root over Supersu 2.67 (Systemless root) because it didn't worked.. so maybe there's a conflict there. I'll report tomorrow.
Fixed with a beta of twrp
Sent from my SM-N920G using Tapatalk
galaxynote2 said:
Oops, I've forgot that! I'm on Marshmallow
Btw I realized that I was installing LP recoveries in MM so I flashed the lastest TWRP build and now it works. The new problem is that I managed to root it but even if SuperSU works I can't manage to modify system files and busybox doesn't work either. I've flashed Dr.Ketan experimental MM root over Supersu 2.67 (Systemless root) because it didn't worked.. so maybe there's a conflict there. I'll report tomorrow.
Click to expand...
Click to collapse
Flash SuperSU Beta 2.68.
Ok, so here is an explanation of what I have going on here. My ultimate goal is to install Magisk on my phone (Running Kitkat 4.4) . I have learned that in order to do that, I need to install a custom recovery on my phone. I have learned that normal custom recoveries cannot be installed on AT&T phones because they have double locked bootloaders or something of that nature, but that Safestrap can work around it. So after finding all that out I successfully installed Safestrap then went on to install Magisk, but when I tried to install the zip, I was told that it is only compatible with Android 5.0 minimum. Fast-forward, I install Lollipop 5.0 on my phone successfully. I then go back and install safestrap, however it appears that it is now not compatible with my upgraded kernel and will not show me the custom recovery on startup... So it seems as if Safestrap will only work for me on Kitkat, but what I need it to do I can only do on Lollipop. Am I simply out of luck, or is there some cleaver way around this?
I appreciate any help I can get on the matter.
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
johnkirchner said:
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
Click to expand...
Click to collapse
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Unfortunately I am not sure why SS isn't working for you, not sure if the lollipop Rom you installed is having issues with it or what? As for the locked boot loader, these phones are like fort Knox. SS is merely a bypass that does not replace an unlocked boot loader.
Justhere4GO said:
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Click to expand...
Click to collapse
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Click to expand...
Click to collapse
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Justhere4GO said:
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Click to expand...
Click to collapse
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, thanks. I successfully booted up into SS mode. I made a backup just in case I need it, then did a factory reset. I chose my Magisk file through the install option, and confirmed it for installation. But now is shows that it is flashing the file, but I have been stuck on the same screen for roughly 20 minutes so far, with no progress on the status bar. From all of the videos I've seen, it looks like this flashing procedure shouldn't take longer than a minute or so, and I fear that something has gone wrong. I know I need to flash my Lollipop kernal back prior to leaving SS, but if my phone is indeed frozen, if I take out the battery and power it up, will I still get a SS Recovery prompt prior to my Samsung logo popping up so I can restore the backup and my correct kernel, or am I on the path to bricksville?
captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Click to expand...
Click to collapse
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Justhere4GO said:
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Click to expand...
Click to collapse
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
captivated1971 said:
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, good to know. I retried booting into SS, reinstalling lollipop kernel, then installing Magisk, but it still froze without any progress. I think the problem is that I the phone is rooted, and Magisk may only be able to be installed on an unrooted phone (It is meant to replace traditional root with a systemless version that can be toggled on and off). But like you said, I cannot get into my custom recovery unless I'm rooted, so that is the predicament I currently find myself in. I actually tried to uninstall root via SuperUser, but that also froze from me when it showed it was supposed to be uninstalling. I'm not sure if that is due to my phone being rooted on KitKat, and that carrying it over into Lollipop ingrained it to the point where I cannot easily take it out. Anyways, it's looking pretty grim for me being able to install this on my device, but I think I may have to go lurking around in a Magisk forum for my next lead.
Anyways, I really appreciate your help in the matter leading me to how to run SS on Lollipop; I'm sure it will come in hand in the future!