Database Develop

[Q] Won't boot up!

Hi
Just used the CyanogenMod Wiki tutorial to try and install ClockworkMod, however after downloading the kernel onto the device, it doesn't start up now. Doesn't flash into recovery or boot up at all, just keeps flashing the first "Galaxy S GT-I900" screen until you pull the battery. Any ideas on how to get my phone working again? Or at least what I might've done wrong?
Thanks!

I guess u flashed the wrong file. Try getting to recovery. Keep holding vol-up +home+ power till screen lights up. Then reflash ur ROM.
Else reflash a GB ROM with ticking partition via Odin.
Let me know if it helped
Sent from my GT-I9000 using Tapatalk 2

I can't actually get to recovery at all, I was trying to install recovery in the first place. I am only able to access the download via USB part.

Flash latest GB ROM via Odin, preferably pre-rooted, so that it has CWM recovery.
And when you flash, make sure u tick re-partition in Odin and use 512.pit file.
Hit thanks if helpful
Sent from my GT-I9000 using Tapatalk 2

jay_ingale said:
Flash latest GB ROM via Odin, preferably pre-rooted, so that it has CWM recovery.
Click to expand...
Click to collapse
Where can I get this? Sorry, I'm a bit of a noob with this stuff.

SlightlyJack said:
Where can I get this? Sorry, I'm a bit of a noob with this stuff.
Click to expand...
Click to collapse
^^ What he said, I just got an i9000 from a friend that is having the boot problem and I'm trying to fix it, but almost all of the links are outdated.

here is a recovery kit containing ezodin, ezbase rom, root kernel and .txt instructions, download, unzip, read and fash....any problems/queries post back here
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip
you will end up with a stripped rooted gb rom from which you can then go on to flash a custom rom

slaphead20 said:
here is a recovery kit containing ezodin, ezbase rom, root kernel and .txt instructions, download, unzip, read and fash....any problems/queries post back here
https://www.dropbox.com/s/d382m2kyorzum16/ezbase recovery kit gb.zip
you will end up with a stripped rooted gb rom from which you can then go on to flash a custom rom
Click to expand...
Click to collapse
Hrm, still having the same issue, any suggestions?

SGT_Watkins said:
Hrm, still having the same issue, any suggestions?
Click to expand...
Click to collapse
Did the flash go ok, did it boot up after initial room flash, and then did it bit after kernel flash?
Sent from my GT-I9000 using xda premium

The flash went well, it didn't boot up fully after the flash, it just rebooted and went to the battery charging screen
---------- Post added at 12:29 AM ---------- Previous post was at 12:21 AM ----------
I've done everything in the guide, now I'm in the CWM 3.0.0.5 screen, what should I flash now?

SGT_Watkins said:
The flash went well, it didn't boot up fully after the flash, it just rebooted and went to the battery charging screen
---------- Post added at 12:29 AM ---------- Previous post was at 12:21 AM ----------
I've done everything in the guide, now I'm in the CWM 3.0.0.5 screen, what should I flash now?
Click to expand...
Click to collapse
What do you want to flash? If you want to flash slim go to website and follow instructions, you will need to get a Cm9 nightly also, then base, essentials, and gapps, and get them onto your sd card, then do the flashing as per instructions on the website
Sent from my GT-I9000 using xda premium

i did the same thing when i flashed my first kernel. Your just bootlooping, this is no biggie. Also the CWM is packaged witht the kernel so thats why you cant get into it. Just flash CF root first this is the guide to get to CM9
1. root w/super1click OR Go and straight flash a kernel such as CF root via ODIN
2. flash ICS via CWM
3. Flash new Kernel like Devil from CWM
4. Sucess!

[Q] How to UnBrick galaxy n7000

Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards

ahmedmasu said:
Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards
Click to expand...
Click to collapse
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?

what rom were you on? if JB, try a factory reset.

nokiamodeln91 said:
what rom were you on? if JB, try a factory reset.
Click to expand...
Click to collapse
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck

lionelia said:
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?
Click to expand...
Click to collapse
Thank for your reply.
I tried flashing the stock rom with Odin but the error remained there
Can you please give me a link from where I can get PIT file?

ahmedmasu said:
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck
Click to expand...
Click to collapse
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?

nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
Is there any guide\link to do this ?

http://forum.xda-developers.com/showthread.php?t=1901191

nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
I have successfully flashed rom on my phone which is : N7000ZSLPF_N7000OZSLPF_OZS
My phone is now out of bootloop but now I face a different issue that I cant get my sim card work, it gives no signal and I noticed one more thing that IMEI of my phone is blank.
I went into recovery mode and it is still showing that efs error as it was showing before...
Any suggestion what should I try to fix this ?

So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.

nokiamodeln91 said:
So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.
Click to expand...
Click to collapse
I followed the instructions provided by the manual ... after step 2 I get imei but after step 3 it get empty again.
Signals do come after step 2 but when I try to make some call it says "Not registered on network".
Looking forward to your reply.

i cannot help you in this case if there is no efs backup.. so.. you on your own..

nokiamodeln91 said:
i cannot help you in this case if there is no efs backup.. so.. you on your own..
Click to expand...
Click to collapse
Thanks for your help so far...
I currently have an imei but it is some random number starting with "004999" and I do get signals but cant make a call .. Do you know if there is some hope for me or not .. and what else I can try.

This is the developer imei. You may be able to make calls of you try a GB rom. Or there is one rom by ThaiDai which had some work around built into it. I don't know which one.
Else the site I mentioned earlier has contact info of cvxcvx. He can fix your phone remotely but by charging about 10 euros.

Need help for a bricked N7000
Hi guys,Im a complete newbie to the whole custom rom scenario. Yet, after being fed up of touchwiz on my N7000 i decided i wanted to taste some KitKat on my phone. After seeing many videos with positive reviews I thought it would be a rather easy process. But somehow I seem to have made a mistake and now my phone is stuck on Samsung Galaxy Note N7000 logo. I cant get into recovery mode as suggested on most places. As of now I only have access to the download mode but dont know what to do with it.
Here's what I tried doing :
1) I was on stock OS, and these are my specifics : Galaxy Note N-7000 running JB 4.1.2
Baseband version : N7000DDLS6
Kernel version: 3.3.31-906407
BUild number:JZO54K.N7000DDLSC
2) As I was following the procedure from Omnirom's official website, I first rooted my phone using Framaroot's single click root app. This gave me SuperSU app.
3) Then I tried installing TWRP recovery (recommended by Omni) but they dont support the N7000. I read a few other tutorials where it was stated the CWM recovery and that too Philz CWM recovery is the best to go with. Apparently it is just stock kernel with CWM recovery. Since the latest one(philz_touch_6.07.9-n7000) was not being installed, I installed the one before that which worked (PhilZ-cwm6-DDLSC-ODD-5.11.2-signed).
4) I even installed the ROM Manager as per the tutorial. However, uptil now I could access recovery mode ( Vol UP+Home+Power) and i saw the touch enabled philz recovery mode once. Then i did system reboot.
5)After reboot, this is where I did a mistake in my opinion. I opened ROM Manger and clicked on "open in recovery mode" option. Since then the phone is stuck on the Galaxy Note N7000 logo. Please help me revive the phone. Thanks in advance. Again, Im doing this for the first time and most terms are new to me. So please explain the procedure as other tutorials are not very clear.

You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.

nokiamodeln91 said:
You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.
Click to expand...
Click to collapse
How do I do i install the kernel using ODIN? I can only access download mode and nothing else. I cant access recovery mode. Please help.

PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.

ANDROID-000 said:
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.
Click to expand...
Click to collapse
http://www.mediafire.com/?ep82ku4c6...o6dtlx8lbc3xz,ob3q9g36b9b3w22,d3v1gys7cbckiet

[ROM] Stock rom kitkat 4.4.2 for T210R

Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster

chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.

hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place

bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.

---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.

bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.

chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?

RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:

andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338

RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.

Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.

RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!

andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes

[Q] boot looping like no other

hey everyone.
really just want to make sure im flashing this rom correct.
mainly because after i wipe everything. data system, exc.
when i go to reboot the device reboots, goes to Samsung galaxy note 4.
then turns off.. vibrates twice then goes back to the samsung galaxy note 4.
rom i am trying to flash is alliance v1.1
the rom i am coming from is the alliance tmobile beta
any info would help
thanks!!!

holt3113 said:
hey everyone.
really just want to make sure im flashing this rom correct.
mainly because after i wipe everything. data system, exc.
when i go to reboot the device reboots, goes to Samsung galaxy note 4.
then turns off.. vibrates twice then goes back to the samsung galaxy note 4.
rom i am trying to flash is alliance v1.1
the rom i am coming from is the alliance tmobile beta
any info would help
thanks!!!
Click to expand...
Click to collapse
Dont wipe system after you flash the ROM. Only wipe cache. If you wipe system you are earasing the ROM.
Sent from my SM-N910T using XDA Free mobile app

Help!
Did you end up figuring this out? I've just had the same thing happen to me!

This build is a COD6..
have you folks updated your bootloader and modem???
If your flashing the partial firmware using odin.. then you need to boot directly into recovery and flash the Rom.
Please post a screen shot of "about device" so i can see your baseband..
Sent from my SM-N910T using Tapatalk

Flashvetrin said:
This build is a COD6..
have you folks updated your bootloader and modem???
If your flashing the partial firmware using odin.. then you need to boot directly into recovery and flash the Rom.
Please post a screen shot of "about device" so i can see your baseband..
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.

AaronBG said:
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.
Click to expand...
Click to collapse
So you have twrp installed..
Ok. Do you have a nandroid back on your ext sd by chance?? If so reboot recovery under advanced wipe sys/data/dal/cache.. then navigate to your ext were your restore is and flash it..
If not follow these steps.[emoji16]
Step #1 download either a stock rom of your choice or something like This
And a copy of the bioshock kernal. If you decide to use the rom i provided the link for. Check the md5 sums from the download source after you download the files to make sure they match. Download them onto your ext sd card.
Step#2 reboot recovery go to wipe advanced and check/ system/data/dalvik/cache/and internal.. ×3
Then factory data reset x3
Then nav to ext sd and flash the rom.
Note: if you flash the link i provided you have to flash the kernel in the same session... READ THE OP..
Note: #2 when you wipe internal your internal sd card will be wiped so if you need to save pics or whatever do so prior..
You can try skipping the internal once but if it loops then you prob should wipe it like i said and flash kernal such as bioshock.
Ok thats it for now please follow and read what i wrote carefully..
And for now stay away from COD6 for now.. unless you understand the procedure... its all about the kernal flashing in the same session before you boot up..[emoji41]
One last thing.. its dangerous to be
"NEW AT THIS" and just start flashing stuff you need to be carefull and read read read.. in your case W8 you need to flash a kernel 90% of the time same setting..
Sent from my SM-N910T using Tapatalk

@Flashvetrin, +1 on the post, also, this guy may need and must start here.....
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
AaronBG said:
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.
Click to expand...
Click to collapse
And did you happen to back up before making those changes? Anytime you do ANYTHING including sneezing, MAKE A BACKUP!

AxAtAx said:
@Flashvetrin, +1 on the post, also, this guy may need and must start here.....
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
And did you happen to back up before making those changes? Anytime you do ANYTHING including sneezing, MAKE A BACKUP!
Click to expand...
Click to collapse
Hes on W8 so unless im mistakin COD6 bootloader and modem will not work.
He can flash the builds but needs a kern to complete the boot... like bio..
And doesnt need the COD6 firmware..
He prob can flash the rom he wanted he just needs to follow it with the kern before he booted...
Easypeasy..[emoji3]
Sent from my SM-N910T using Tapatalk

i just ended up, starting over, doing a stock odin 5.0.2 then re rooting and re installing twrp.
and now it works fine!!

Installing Magisk on Lollipop 5.0 - Paradox?

Ok, so here is an explanation of what I have going on here. My ultimate goal is to install Magisk on my phone (Running Kitkat 4.4) . I have learned that in order to do that, I need to install a custom recovery on my phone. I have learned that normal custom recoveries cannot be installed on AT&T phones because they have double locked bootloaders or something of that nature, but that Safestrap can work around it. So after finding all that out I successfully installed Safestrap then went on to install Magisk, but when I tried to install the zip, I was told that it is only compatible with Android 5.0 minimum. Fast-forward, I install Lollipop 5.0 on my phone successfully. I then go back and install safestrap, however it appears that it is now not compatible with my upgraded kernel and will not show me the custom recovery on startup... So it seems as if Safestrap will only work for me on Kitkat, but what I need it to do I can only do on Lollipop. Am I simply out of luck, or is there some cleaver way around this?
I appreciate any help I can get on the matter.

Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.

johnkirchner said:
Did you root your phone while on KK? If not, you may be out of luck now. There are a few lollipop rooted rooms that will work and you can keep using SS but you must already be rooted. Mine is still rooted with SS, I am not upgrading for the foreseeable future.
Click to expand...
Click to collapse
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.

Unfortunately I am not sure why SS isn't working for you, not sure if the lollipop Rom you installed is having issues with it or what? As for the locked boot loader, these phones are like fort Knox. SS is merely a bypass that does not replace an unlocked boot loader.

Justhere4GO said:
Yes, I rooted my phone while still on KK, then I used Flashfire to upgrade to LP which allowed me to still keep root.
Click to expand...
Click to collapse
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Ok so if you have three of these four things it should work for you depending if your running a g900a or 870a ,1. you will need the kernel flasher ,900a takes nce kernel flasher , 870a requires ng3 kernal flasher , these are model specific. 2. Busybox installed . 3. Safestrap. 4 safetrap flashable kernels.zips. install busybox, install whichever specific kernel flasher you have per your model, install safetrap. Make sure you have the flashable kernel zip for lollipop on external sd for safe keeping. Cuz if you wipe internal sd for any reason and the zip you will have to resort to the odin flashable versions and odin. Then flash kk kernel with flasher apk then you should enter ss ,flash install magisk then install again the recovery flashable kernel .zip for lollipop and then reboot back into lollipop. All good.
Click to expand...
Click to collapse
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?

Justhere4GO said:
Alright, now we're getting somewhere. So I downloaded NCE Kernel Flasher (I have 900a), along with the G900A_OC4_Stock_KERNEL_Recovery-Flashable.zip file. So is that file the stock kernel for Lollipop to bring me back after using the program? From what the instructions say, it looks like the NCE Kernel Flasher already comes with the Kitkat kernel in it, but I am still not certain I am reading this correctly.
My second question is about the Magisk program itself if you have any insight on that which you could offer. It is recommended that it be installed on a stock rom, and I believe I need to be unrooted when I put it on to make it work correctly. So while I'm in the safestrap recovery via NCE Flasher, should I do a factory reset first, then flash magisk, then flash the stock kernel zip?
Click to expand...
Click to collapse
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, thanks. I successfully booted up into SS mode. I made a backup just in case I need it, then did a factory reset. I chose my Magisk file through the install option, and confirmed it for installation. But now is shows that it is flashing the file, but I have been stuck on the same screen for roughly 20 minutes so far, with no progress on the status bar. From all of the videos I've seen, it looks like this flashing procedure shouldn't take longer than a minute or so, and I fear that something has gone wrong. I know I need to flash my Lollipop kernal back prior to leaving SS, but if my phone is indeed frozen, if I take out the battery and power it up, will I still get a SS Recovery prompt prior to my Samsung logo popping up so I can restore the backup and my correct kernel, or am I on the path to bricksville?

captivated1971 said:
Really i havent messed with magisk at all so i cant say anything about that . But yes after you flash it or install it just go back to the install button and install the kernel zip to get you back to lollipop. Then reboot. And yes they are only stock kernels because the bootloader wont let us use custom kernels
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
But on your second question i dont see how you can install it and not be rooted . Because you have to be rooted to have ss running.
Click to expand...
Click to collapse
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).

Justhere4GO said:
So I did just take out the battery, and was able to get back into custom recovery and restore my backup. I tried to install magisk a few more times to no avail. (Kept saying installing but never progressed) My only thought is that maybe because Magisk is not compatible with Kitkat, I would need to update the kernel back to lollipop first before installing magisk. My concern though is, if that is not what the issue is, then restoring my kernel will keep me from being able to re-enter custom recovery to restore my data if I need to. Does that sound like it could be a plausible reason that the file will not install?
Also, if I do attempt to update the kernel in SS, should I still be able to use Odin to restore a stock rom if I have to pull the battery on my device again due to it freezing during installaion? (I've only used Odin twice, so I'm not 100% sure of it's capabilities).
Click to expand...
Click to collapse
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app

captivated1971 said:
Hows it goin? Sorry i dont pop in all the time here . Yes odin will work fine everytime as long as its all stock .but it will wipe everything again except external sd card . So if you saved a backup to internal sd it will be wiped . If you saved to ext sd it will still be there if you have to odin . And everything else will be gone also like ss and kernal flasher and all itll be pure stock again also will erase root.
Sent from my SM-G900F using XDA-Developers mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Everything is returnable from on these phones unless you update the bootloader past oc1. Then no root . Even if you hardbrick where it will hardly do nothing but make a sound when plug it to your computer is fixable . But it is a lengthy process and hope you two of them to be able to fix the other or do the right method and be able to flash an image to an sdcard to get you into download mode .lol unless you brick it and just sell it to me for 5 bucks lol.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, good to know. I retried booting into SS, reinstalling lollipop kernel, then installing Magisk, but it still froze without any progress. I think the problem is that I the phone is rooted, and Magisk may only be able to be installed on an unrooted phone (It is meant to replace traditional root with a systemless version that can be toggled on and off). But like you said, I cannot get into my custom recovery unless I'm rooted, so that is the predicament I currently find myself in. I actually tried to uninstall root via SuperUser, but that also froze from me when it showed it was supposed to be uninstalling. I'm not sure if that is due to my phone being rooted on KitKat, and that carrying it over into Lollipop ingrained it to the point where I cannot easily take it out. Anyways, it's looking pretty grim for me being able to install this on my device, but I think I may have to go lurking around in a Magisk forum for my next lead.
Anyways, I really appreciate your help in the matter leading me to how to run SS on Lollipop; I'm sure it will come in hand in the future!