So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.
DaltonMplz said:
So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.
Click to expand...
Click to collapse
A ROM using ODIN? Which one? If it's Lollipop...and you are on the T-Mobile logo screen, how long did you wait? It takes ~10 minutes to boot. But, if you are on the Samsung screen, there is a problem. So, I'm currently thinking you are not waiting long enough?
Try putting your rom in the extsd or internal and flash from there.
I would grab the stock firmware and flash that using Odin. Don't forget to factory reset using stock recovery after flashing stock firmware.
Just start over.
Then root and install twrp, once your back at square one, then put your rom of choice on either of the SD locations and flash using twrp.
A bootloop after flashing a rom is usually, in my experience, a kernel issue. So it couldn't hurt to have an alternate compatible kernel to flash if you need it.
If you have TWRP all is not lost. If you flashed the stock ROM then you probably don't have TWRP anymore. Its just about impossible to wreck this phone by flashing ROMs. I would ODIN to the stock COD6 build. I believe there is a thread with all the files you need in one zip. Follow those instructions and it should get you back to stock rooted and you can go from there with flashing ROMs again.
Sent from my SM-T900 using XDA Free mobile app
No the rom doesn't use Odin. But I imagine the person had to root and flash a custom recovery as well. The rom of course had to be flashed in recovery.
I can't seem to find out how to fix this problem. and was wondering if someone was able to help me. I updated to stock lollipop and changed roms to DomPop 2.2.3 and wanted to flash a different lollipop rom, but ss wont boot anymore once I use the NC2 flasher app. It just boots to a black screen, and wont do anything else. I have try using Odin and flashing the NC2 kernel that way, but it doesn't help. Once I reboot the phone in download mode I can flash back to OC1 no problem and use the current installed rom, but can't get ss to work. I have uninstalled busybox and ss a couple times, and it gives me the same thing. Would Flashfire be an easier alternative? Otherwise, would I use odin to flash a different rom/files, and get ss working that way?
I would just Odin back to NC2 and use @walterwhite's lollipop rooted Rom just make sure you install Supersu, busybox, an SafeStrap before upgrading to his lollipop an you should be goldin'..
GoldieSlayer said:
I would just Odin back to NC2 and use @walterwhite's lollipop rooted Rom just make sure you install Supersu, busybox, an SafeStrap before upgrading to his lollipop an you should be goldin'..
Click to expand...
Click to collapse
I got it to work using that method. Thank you for the help.
Galaxy Note 3 AT&T. Can't boot to ROM-Safestrap boots straight to stock recovery mode
Hello guys, for some reason I'm not able to boot to my rooted stock 5.0 ROM (Galaxy NOTE 3, AT&T, Lollipop 5.0). Everything was working fine, then I booted to safestrap to backup my stock ROM (which went succesfully) as I wanted to tweak some things in my phone afterwards. I dont really know what happened but since then I cant boot normally to the ROM, but my phone goes straight to the stock recovery mode. I've tried everything to my knowledge already, from the stock recovery the boot option just sends me back again to the same recovery mode. If I press the "continue" button on safestrap initial screen it also sends me to the stock recovery mode, same If I just wait 10 seconds, same if I try rebooting from within the safestrap options. I can't get pass the recovery mode to the normal ROM booting. Not sure what's going on here as I just performed a backup, didnt install nor restore any ROM before having this problem...The backup seems to be there in my external card so I guess I could restore it to the stock slot hoping this could send me to boot normally to the ROM.....Is there anything I'm missing here???...Does any body know what may be happening??....any advise is greatly appreciated!!...Many thanks!!
@momo909
Safestrap does not work with the lollipop oc1 kernel... in order to use safestrap with lollipop, you have to flash the nc2 kit kat kernel first, then boot into safestrap. There is a tool called the nc2 flasher you can use use - you should read the following thread for tips and tricks.
http://forum.xda-developers.com/showthread.php?t=2989141
Kernel Flasher
What you would have needed to do after backing up your rom... before you left safestrap you would have needed to flash the recovery flashable oc1 kernel, then reboot. There is a recovery flash able oc1 kernel around here on the forums in several places... here is a link I found
https://www.androidfilehost.com/?fid=95916177934551552
But since it seems like you didn't reflash the oc1 kernel before leaving safestrap you will need to use odin to reflash the oc1 kernel...
If you go to this thread, you can download the odin flashable oc1 kernel and then use odin to flash the kernel to your device. Then you should be able to reboot your phone normally.
http://forum.xda-developers.com/showthread.php?t=3168341
OC1 Kernel odin flashable
*** disclaimer... I'm not a developer, but I flashed numerous roms on this n900a and this is the struggle we currently face with our locked bootloader. Things can go wrong, but if I we're having the issue you described, this is how I would try to get my device back up and running.
Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse
Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse
ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse
ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse
http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe
ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?
You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse
Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse
I know this is not an issue forum but I CANNOT find one for the SM-i757M so this is where I'm going to put my question. One of the mods can move it if they want.
So, I tried to install CF-Auto-Root using Odin V 3.07 on my Samsung Galaxy S II i757M phone. Odin PASSes it, but it gets stuck on the red Chainfire logo with CF-Auto-Root and various info on the bottom sitting solid. It flashes every couple seconds indicating it keeps trying to run the script but it's not working. Upon going to recovery, which isn't custom, it displays the "Firmware upgrade encountered an issue" message. At the top, it's clearly in Download Mode because it says "ODIN MODE" in red. I can even connect to Odin and re-flash CF-Auto-Root again. But it won't work. Can anyone help me either get it to work, or stop it from trying to run so I can boot my phone back into the firmware without having to wipe anything?
Thank you in advance.
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
diabolicalprophecy said:
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
Click to expand...
Click to collapse
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
superluig164 said:
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
Click to expand...
Click to collapse
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
diabolicalprophecy said:
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
Click to expand...
Click to collapse
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
superluig164 said:
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
Click to expand...
Click to collapse
You don't need CF to root after flashing a custom recovery.
Just download supersu.zip and flash from philz or Twpr recovery. (download link is in supersu thread)
Flashing recovery without factory wipe will not cause any loss of data.
Yes you can boot into stock rom with philz touch or twpr as both of them support stock firmware.