Related
As the title says, I am currently unable to boot into Philz recovery. I bricked somehow trying to flash sacs 4.3 by stupidly restoring the wrong part of my nandroid backup. Flashed the stock OEM 4.3 MJA and did a factory reset right after. Anyway, when I try to boot into recovery it says "Recovery not seandroid enforcing" and "see warranty bit : recovery" then just reboots into the rom. Can anybody help me out?
Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk
frostedunit said:
Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I did both of those. I currently have root access and flashed the recovery twice to make sure I didn't do it wrong the first time. I am beginning to wonder if the bootloader changed from MF9 to MJA when I flashed the OEM, which won't allow Philz to boot properly.
Bump.
Still stuck without a working recovery...
l0udude said:
Bump.
Still stuck without a working recovery...
Click to expand...
Click to collapse
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?
ParkerParker said:
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?
Click to expand...
Click to collapse
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.
l0udude said:
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.
Click to expand...
Click to collapse
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce? @leaderbuilder you have any input man?
Sent from my SPH-L720 using Tapatalk
ParkerParker said:
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.
l0udude said:
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.
Click to expand...
Click to collapse
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.
leaderbuilder said:
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.
Click to expand...
Click to collapse
Yeah I'll check around and see if I come up with anything. I'm not particularly new to this if you can't tell. I've rooted and customized 2 different phones, as well as jailbroke, themed, and flashed stuff to my ps3 back when it was possible. I rooted and flashed sacs v4 rom and ktoonsez kernel easily almost immediately after getting the phone a few months ago. I'm currently running a rooted, stable, stock 4.3 MJA everything so I guess I'm gonna wait and see if anything new surfaces. I have a suspicion that something is writing over CWM with the stock recovery when I boot into the rom but I don't know what to do about it. GooManager won't install openrecovery for some reason either, I already tried that. Just stalls at the download page. Thanks for the help anyway guys.
If you can get into download mode there is no reason that a custom recovery shouldn't install via PC Odin.
You can try this.
Grab the recovery .tar Launch Odin (make sure to 'Run As Administrator') place the .tar in the PDA slot and make sure you un-check "Auto Reboot".
Once it installs (Pass) take phone off PC, remove battery.
Put battery back in and then boot straight to recovery - Home button, Volume Up and Power button till you see the very little blue 'entering recovery' at the top left. If you get into recovery just choose the 'restart phone option. Or you might want to step through the Philz menus then back out to the Power Options then Reboot system and then 'fix root' and let it reboot.
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
rdxdha said:
*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
Click to expand...
Click to collapse
Download Free version of Rom Manager and after install see if it will not install which ever you want through it CWM or TWRP. Way I do it. You are Rooted???? Here is link https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en After install open and click on "Flash ClockworkMod Recovery" then it gives you choice of CWM or TRWP
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
You can't install custom recoveries. Our bootloader is locked. Your only option is using safestrap
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
U can't install a traditional recover. Since U are on NB1, your baseband is locked and your only option is Safestrap (TWRP). Read the instructions carefully at least once all the way thru and then proceed. Pay close attention because it's not like most phones. It works just fine. U can have a heavily modified Touch Wiz Rom or even now a AOSP based Google Play Edition Rom.
Proceed here:
[INDEX] All things AT&T MK2, NB1, and NC1 (including ROMs
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
What are you looking for in CWM recovery that is different for Stock recovery????
tailgunner9 said:
What are you looking for in CWM recovery that is different for Stock recovery????
Click to expand...
Click to collapse
I am trying to install custom rom , without safestrap. As bootloader is locked on my phone , I cant use CWM.
Using safestrap , I was able to install [AOSP] Official 4.4.3 - S4 Google Edition. but now I am not able to encrypt my phone.
Any idea on how to encrypt phone now ?
I am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app
@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:
Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)
EDIT: I have successfully installed the Alliance ROM. Here's how i did it.
Prerequisites:
Your phone at at least 50% battery
A charge cable
MicroSD card that you can plug into your computer
Odin 3.09
SafeStrap, version 3.75 APK on your MicroSD card
Alliance ROM on your MicroSD card
NCG tar.md5 (the big file, not the kernel)
I started off on a rooted 5.0 VZW Galaxy S5. After some confusion, I downgraded to NCG (4.4.2) using Odin. After doing that, I went to Towelroot, got the APK, rooted, downloaded SuperSU from the play store (I had to sign into google at this point), installed it's binaries (NORMALLY! Don't choose the TWRP method), rebooted when it asked me to. From there, I installed BusyBox from the play store and installed it within the app. Then I installed Safestrap (version 3.75), which I had on my MicroSD card. I used the app My Files to navigate to my MicroSD and installed the APK. Then I installed it within the app, and when the "reboot to recovery" button worked, I rebooted into SafeStrap recovery mode. At this point, the Alliance ROM zip file should ALREADY BE ON YOUR MICROSD CARD, WHICH SHOULD BE IN YOUR PHONE. Now, you're going to press the INSTALL button to the top right in Safestrap recovery, and you're going to navigate to your MicroSD card. It might be already opened to that. Then you're gonna select the Alliance ROM and flash it. After it successfully flashes, reboot into download mode (if for some reason you aren't able to do it immediately, you get into download mode by holding volume down, home button, and power button at the same time). Now, using Odin, you're gonna flash the firmware that the instructions in the Alliance thread tells you to (here's the thread: http://forum.xda-developers.com/ver.../rom-alliancerom-build-3-rom-control-t2818632). If everything works, it's gonna take a couple of minutes, optimize apps, and boot.
Huge thanks to Beans and his team for creating the Alliance mod, and huge thanks to Tulsadiver for helping me get through the process during my confusion.
Original thread below
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.
israphial said:
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.
Click to expand...
Click to collapse
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.
Tulsadiver said:
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.
Click to expand...
Click to collapse
Wait, so I don't need to downgrade my phone? Keep in mind I'm on stock rooted 5.0, which just got factory reset so I got nothing except for the root. Also, what full firmware odin tar are you referring to? NE9? This one: https://www.androidfilehost.com/?fid=23610159112652201
Or this one: https://www.androidfilehost.com/?fid=23622183712472727
I'm getting these links from here: http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
I really appreciate you replying. Thank you.
The first one. That firmware will downgrade you to NE9.
Tulsadiver said:
The first one. That firmware will downgrade you to NE9.
Click to expand...
Click to collapse
Ok, so I don't need to downgrade to install the ROM. Got it. Thank you. Is there anything else I should know?
Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.
Tulsadiver said:
Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.
Click to expand...
Click to collapse
So, I installed Safestrap and did all that, but when I press the reboot into recovery button, it just reboots the phone normally. It doesn't go into safestrap recovery. Am I supposed to hold some buttons or something?
Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.
Tulsadiver said:
Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.
Click to expand...
Click to collapse
Yes, I've installed BusyBox and given SS root permissions. I installed the APK 3.75 Safestrap that I used to get into SS recovery when I was getting to rooted 5.0 a while back, so I know that the APK isn't corrupt or anything like that.
I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.
Tulsadiver said:
I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.
Click to expand...
Click to collapse
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
israphial said:
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
Click to expand...
Click to collapse
That is it.
Tulsadiver said:
That is it.
Click to expand...
Click to collapse
Thank you. I'm going to flash the kernel then, then I'll get back to you if anything comes up. Again, I really appreciate you helping me. Thank you.
Tulsadiver said:
That is it.
Click to expand...
Click to collapse
It booted into stock recovery mode after odin successfully flashed NE9. Now do I install the ROM from stock recovery, or do I boot the phone and get to Safestrap to install the ROM from Safestrap recovery? I am currently in recovery mode.
You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.
Tulsadiver said:
You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.
Click to expand...
Click to collapse
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?
israphial said:
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?
Click to expand...
Click to collapse
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.
Tulsadiver said:
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.
Click to expand...
Click to collapse
I can get into download mode perfectly fine. I'm going to kernel back to 5.0 then...
But what do I do now? Should I downgrade to 4.4.2 with the stock firmware once I successfully boot 5.0?
EDIT: Yup, booted 5.0 perfectly fine. Now what? Downgrade to 4.4.2 and flash the NE9 Kernel?
Proof that Safestrap is on my phone:
http://imgur.com/cGa1v1n