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.
Related
I've been reading the 4.3 release thread in the "general" forum, and the other relevant threads over there, and am confused after reading thru' 50+ pages of experiences...
I'm on the stock MF9 ROM, rooted, with hotspot mod installed, and camera shutter sound disabled in xml file), and TWRP custom recovery.
I'd like to get to MJA, rooted, with hotspot mod installed, and TWRP custom recovery. (if possible, I'd like to get there without tripping the KNOX counter, but if that is not possible, so be it)
From what I've read, it looks like I need to
Nandroid backup (optional)
Install stock MF9 tar file using ODIN (recovery, ROM, Modem, kernel) - http://forum.xda-developers.com/showthread.php?t=2485502
Take OTA (or use update file from google server link on http://forum.xda-developers.com/showthread.php?t=2504349)
Reboot (Don't install any apps at this time)
Use CF Auto to root using ODIN - http://forum.xda-developers.com/showpost.php?p=41743640&postcount=3
Factory reset just in case
Install goo manager, and flash custom recovery TWRP
Reboot
Reinstall apps
Install new MJA odexed hotspot mod http://forum.xda-developers.com/showthread.php?t=2256950
Nandroid backup
Is this about right? (and are the links to the right files/posts?)
Is there an easier/safer way of doing this?
Is there any way to not trip the knox counter? Or does the flash of CF Auto to root always trip it?
Any other troubleshooting steps in case things go wrong?
Example:
If phone gets stuck in bootloop at any step - what steps should be attempted before pulling battery, and trying to reflash in ODIN?
If phone shows android lying down with red exclamation mark, what should be attempted?
If root doesn't stick after reboot, what should be attempted?
If custom recovery doesn't stick, what should be attempted?
Hopefully, this will help others like me as well.
Thanks!
looks good, sounds right...
jj14 said:
I've been reading the 4.3 release thread in the "general" forum, and the other relevant threads over there, and am confused after reading thru' 50+ pages of experiences...
I'm on the stock MF9 ROM, rooted, with hotspot mod installed, and camera shutter sound disabled in xml file), and TWRP custom recovery.
I'd like to get to MJA, rooted, with hotspot mod installed, and TWRP custom recovery. (if possible, I'd like to get there without tripping the KNOX counter, but if that is not possible, so be it)
From what I've read, it looks like I need to
Nandroid backup (optional)
Install stock MF9 tar file using ODIN (recovery, ROM, Modem, kernel) - http://forum.xda-developers.com/showthread.php?t=2485502
Take OTA (or use update file from google server link on http://forum.xda-developers.com/showthread.php?t=2504349)
Reboot (Don't install any apps at this time)
Use CF Auto to root using ODIN - http://forum.xda-developers.com/showpost.php?p=41743640&postcount=3
Factory reset just in case
Install goo manager, and flash custom recovery TWRP
Reboot
Reinstall apps
Install new MJA odexed hotspot mod http://forum.xda-developers.com/showthread.php?t=2256950
Nandroid backup
Is this about right? (and are the links to the right files/posts?)
Is there an easier/safer way of doing this?
Is there any way to not trip the knox counter? Or does the flash of CF Auto to root always trip it?
Any other troubleshooting steps in case things go wrong?
Example:
If phone gets stuck in bootloop at any step - what steps should be attempted before pulling battery, and trying to reflash in ODIN?
If phone shows android lying down with red exclamation mark, what should be attempted?
If root doesn't stick after reboot, what should be attempted?
If custom recovery doesn't stick, what should be attempted?
Hopefully, this will help others like me as well.
Thanks!
Click to expand...
Click to collapse
Hi,
It'll be awhile, I live on my boat & Connectivity can be slow this time of day, but I'm dwnldg & will let you know how it goes. I'm praying this is it I'm going on13=14 hrs screwing around with it. Thanks for your style of posting,too, very user friendly.
ms.samsprung said:
Hi,
It'll be awhile, I live on my boat & Connectivity can be slow this time of day, but I'm dwnldg & will let you know how it goes. I'm praying this is it I'm going on13=14 hrs screwing around with it. Thanks for your style of posting,too, very user friendly.
Click to expand...
Click to collapse
Thank you
Is this how it's supposed to be done?
http://forum.xda-developers.com/showthread.php?t=2509605
Ok so I started out on 4.2.2 & never took the 4.3 update in light of all the backtalk about the knox BS... I do my research first lol
But to install a 4.3 ROM I needed to odin the firmware/baseband to mk2... Soft bricked it... Every time I odined that mk2 firmware it would soft brick...
Odined back to 4.2.2 did everything all over again(root & philz touch CWM) & still soft bricked it when I tried to odin the mk2 firmware...
Realized that odin'ing to the mk2 firmware forever ruined any chances of going back to No Knox Stock pre-mk2.
I did however get past the "firmware update FC everything" with a simple factory reset from the devices settings menu!!! Needless to say it wasn't easy between all the FC's lol, but...... Yay no more FC!!!
So, now I'm stuck at stock rooted OTA mk2 with Philz Touch CWM(the only way I could safely get the proper firmware & cant seem to flash a single thing whatsoever...)
I'm a seasoned vet here, ex ACS themer, well over 5000 flashes on my belt & I NEEDS MY FIX!!! Someone please tell me theres a way to flash a ROM after all the BS I've been thru here...
If you were trying to flash the MK2 firmware (modem) by Unknownforce one of the things metioned was
NOTE: With MJA/MK2 Firmware, some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot.
Click to expand...
Click to collapse
Also installing that firmware does NOT put knox bootloader on your system.
Taking the OTA however does!
IF you do have the latest Philz (philz_touch_6.08.9-jfltespr) you should be able to flash most ROMs.
In the last week there have been three or four ROMs that have been updated/released and they all run well. Big thing with flashing is that some builds require different recoveries and/or flashing instructions (as per the dev's OP). Some require rebooting of recovery etc.
leaderbuilder said:
If you were trying to flash the MK2 firmware (modem) by Unknownforce one of the things metioned was
Also installing that firmware does NOT put knox bootloader on your system.
Taking the OTA however does!
IF you do have the latest Philz (philz_touch_6.08.9-jfltespr) you should be able to flash most ROMs.
In the last week there have been three or four ROMs that have been updated/released and they all run well. Big thing with flashing is that some builds require different recoveries and/or flashing instructions (as per the dev's OP). Some require rebooting of recovery etc.
Click to expand...
Click to collapse
Tried this also no luck... although im running Philz v6.0.4.5
& once you install firmware that has knox you cant go back to no-knox versions...
try flashing the latest twrp from Philz, reboot recovery then in TWRP goto advanced and 'fix permissions. Then reboot.
Then back to recovery, flash Philz, reboot recovery and try install from again.
Either way... I still cant get anything to flash lol
I just need to flash something lol
I'm stuck at stock rooted OTA mk2 with Philz Touch CWM
what to do from there?
leaderbuilder said:
try flashing the latest twrp from Philz, reboot recovery then in TWRP goto advanced and 'fix permissions. Then reboot.
Then back to recovery, flash Philz, reboot recovery and try install from again.
Click to expand...
Click to collapse
never tried that lol
i only odined Philz
greenmuggy said:
never tried that lol
i only odined Philz
Click to expand...
Click to collapse
I keep zips of both recoveries on my externalSD card for just that.
leaderbuilder said:
I keep zips of both recoveries on my externalSD card for just that.
Click to expand...
Click to collapse
i didnt bc it didnt work at the time...
greenmuggy said:
i didnt bc it didnt work at the time...
Click to expand...
Click to collapse
leaderbuilder said:
I keep zips of both recoveries on my externalSD card for just that.
Click to expand...
Click to collapse
Both downloaded just gonna back up my backups on my sd & ill give it a try
BRB
7gb... ugh... this might take awhile
Ok as soon as i boot into TWRP & try to flash the newest Philz CWM it wont take...
Yeah... I'm stuck at v6.0.4.6 PhilZ Touch
Is there an odin for this 6.0.8???
I give up for now, its bed time too many beers lol...
Philz PC Odinable .tar
TWRP Odinable .tar
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
Thanks, I will try when I get home from work.
Sent from my SPH-L720 using xda app-developers app
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
If I can finish my homework 2nite ill give this a try... been busy as hell with my work & 3rd semester college they are kicking my ass this semester lol
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
Yeah it still won't flash or odin to the newest Philz... What am i missing i need some major help
If i odin TWRP & then flash the newest Philz, it just goes back to the v6.0.4.6 Philz... Why>>> Ahhh!!!
Try just to PC Odin Philz. Use Odin 3.09 see if that works.
leaderbuilder said:
Try just to PC Odin Philz. Use Odin 3.09 see if that works.
Click to expand...
Click to collapse
Didn't work it wont go away, unless i odin TWRP, but that wont flash any roms either, & from twrp if i odin or flash philz it just goes back to the old version of philz
I think the partition that holds the recovery.img might have gotten corrupted or something that is causing your problems. I would try using odin 3.09 to flash the MK2 full stock tar to bring your phone back to an unaltered state. Then re root using safe root or cf autoroot. Then try to install the recovery you want. Might be less of a headache then fighting this problem you keep having getting a recovery to work.
i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?
You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.
all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.
Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.
Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?
That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?
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