Develop Bugs

[Kernel] Insecure/Rooted, CWM-Flashable MVLALH1 [ADB][init.d][Custom Bootanimation]

Hey everyone,
This is a modified stock kernel based on the Canadian stock kernel MVLALH1 and is ONLY compatible with stock-based ICS roms from the i747m. I haven't seen this around so I decided to make it myself for all to use and assist in development and was contacted to make this for all you Canadian folks without much dev help. The root application of choice is Chainfire's SuperSU. Remember that the first boot takes longer than usual after you clear the cache.
Features:
•Insecure rooted kernel
•init.d script support
•ADB support
•Custom bootanimation.zip support
Instructions:
1.Download the recovery-flashable zip to your phone's SD card
2.Flash in recovery
3.Wipe cache and dalvik cache
4.Reboot and enjoy
Standard disclaimer: I am not responsible for anything bad that happens to your phone. I have personally tested this on my own AT&T SGS3 and it works great for me.
Special thanks to NunHugger for his infinite wisdom in helping me figure out how to get custom boot animations working and letting me borrow his updater script. Also thanks to dsixda for the amazing Android Kitchen. Thanks again neuropass for your donation. Always appreciated, never necessary.
Download:
From here
Or, alternatively, directly from this thread
Kernel Source: http://opensource.samsung.com

Secondary Odin Instructions
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9

stratatak7 said:
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9
Click to expand...
Click to collapse
Awsome thanks..

Fantastic. Thanks again.

You're welcome! I haven't tested it yet but I didn't change any of my processes. Just trying to help out the friends up north.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

stratatak7 said:
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9
Click to expand...
Click to collapse
First of all, thanks for the kernel! Only one problem I got. I flashed this through Odin but it seems my device is still not rooted. what do I do next?
I tried installing the already rooted Samsung firmware but the install just hangs and soft bricks my S3 so I reverted back to stock and trying to root in a different way.
Any help? Please?

islandboy_2000 said:
First of all, thanks for the kernel! Only one problem I got. I flashed this through Odin but it seems my device is still not rooted. what do I do next?
I tried installing the already rooted Samsung firmware but the install just hangs and soft bricks my S3 so I reverted back to stock and trying to root in a different way.
Any help? Please?
Click to expand...
Click to collapse
I apologize I should be more clear. The insecure kernel allows you to actually root but does not actually root the device. The next step in the process is for you to flash supersu or superuser (preferably in recovery. Go to chainfires supersu thread and it will provide you with the correct packages to flash. I believe that is one method of doing it. By insecuring a kernel it just allows you to root. You'll need to include su binaries but the cwm packages on chainfires thread should take care of that. Let me know if you're still having issues and I'll take a more personal look into it.
Secondary: I know for sure if you download the qcom toolkit it will quide you through rooting without issues at all. Then you can simply flash this kernel overtop and you should still be able to keep root.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

stratatak7 said:
I apologize I should be more clear. The insecure kernel allows you to actually root but does not actually root the device. The next step in the process is for you to flash supersu or superuser (preferably in recovery. Go to chainfires supersu thread and it will provide you with the correct packages to flash. I believe that is one method of doing it. By insecuring a kernel it just allows you to root. You'll need to include su binaries but the cwm packages on chainfires thread should take care of that. Let me know if you're still having issues and I'll take a more personal look into it.
Secondary: I know for sure if you download the qcom toolkit it will quide you through rooting without issues at all. Then you can simply flash this kernel overtop and you should still be able to keep root.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks a bunch for clearing that up! I will let you know once I'm succesful. Cheers! :good::laugh:

error when flashing Insane Kit Kat

I flashed stock 4.4.2 from sammobile, cf auto root, open su user, disable knox, flashify install TWRP....and then i flashed insane kitkat...i am getting a error kernel is not se android enforcing (in red), set warranty bit: kernel (in yellow) top left corner and it gets stuck on this screen..
Does anyone know how to fix this? I would like to be on a custom kit kat rom rather than the stock version. Thanks.

ab102 said:
I flashed stock 4.4.2 from sammobile, cf auto root, open su user, disable knox, flashify install TWRP....and then i flashed insane kitkat...i am getting a error kernel is not se android enforcing (in red), set warranty bit: kernel (in yellow) top left corner and it gets stuck on this screen..
Does anyone know how to fix this? I would like to be on a custom kit kat rom rather than the stock version. Thanks.
Click to expand...
Click to collapse
Try flashing another kernel through recovery. Sorry I don't have a link. but you will get the se android enforcing message along with set warranty bit. Don't worry about that. The stuck screen is the problem and I've had problems like that after installing a backup and was told to flash a new kernel and that worked.

what kernel should i flash?

ab102 said:
what kernel should i flash?
Click to expand...
Click to collapse
Try the kernels here http://forum.xda-developers.com/showpost.php?p=44314828&postcount=2
The Touchwiz Kit Kat 4.4 kernel should work for you.

i tried that.....didnt work

can someone please help me fix this issue?

At this point all I can think of is to Odin a stock rom back on then root and install custom recovery. put the Insane rom on the phone's sdcard. Boot into recovery, wipe then install via sd card the insane rom. This is how I've done it and it worked. Only time I was getting the boot loop was when I tried to reinstall a nandroid backup I made. Oh, don't worry about disabling knox. I wouldn't go so far as to even do anything else to the stock rom once it's rooted. I wouldn't even answer the Language question it asks when you first boot up.

that didnt work either.....guess im stuck with stock kit kat ...

Did you make sure to do a full wipe before flashing the Insane kk, like Sickness stated?
Sent from an A.I. frequency

Why not post on the insane kk thread so others can see and try to help..just me .02
Im on his rebirth rom and between him(thesickenss) and others the support is unbelievable...im sure youll get farther there

yes i did full wipe..and the reason why I have it on this thread is bc i tried posting in that tread..but other ppls questiosn got in the way..thats why i wanted to open a new thread....so does anyone have any idea how i can get insane kit kat to work.
i flashed the stock 4.4 from sam mobile, then odin cfroot, flashify- TWRP...wipe, factory reset, install insane kit kat

is there a way to ODIN TWRP?..i was using flashify and installed it like that..that way i dont have to mess with the stock at all such as the language screen. Thanks.

ab102 said:
is there a way to ODIN TWRP?..i was using flashify and installed it like that..that way i dont have to mess with the stock at all such as the language screen. Thanks.
Click to expand...
Click to collapse
Yes, flash this tar in odin: (http://techerrata.com/browse/twrp2/jfltetmo Get the newest .tar)

Fenny said:
Yes, flash this tar in odin: (http://techerrata.com/browse/twrp2/jfltetmo Get the newest .tar)
Click to expand...
Click to collapse
ok i did that same error message...this is so frustrating ahhhh!!..also at the end of flashing insane kit kat it asks me..your device does not appear to be rooted, install SU user? i just said do not install, but in the past i have also said install SU user and it still gets stuck..i already rooted the phone via cf auto root..

ab102 said:
ok i did that same error message...this is so frustrating ahhhh!!..also at the end of flashing insane kit kat it asks me..your device does not appear to be rooted, install SU user? i just said do not install, but in the past i have also said install SU user and it still gets stuck..i already rooted the phone via cf auto root..
Click to expand...
Click to collapse
Try wiping /system/ before flashing the zip. I think that insane may not do a /system wipe as part of the install.

Fenny said:
Try wiping /system/ before flashing the zip. I think that insane may not do a /system wipe as part of the install.
Click to expand...
Click to collapse
yup i noticed that and did that this time..still no go...i think i just tripped up knox somehow and theres nothing i can do to fix this..ive searched everywhere .

ab102 said:
yup i noticed that and did that this time..still no go.
Click to expand...
Click to collapse
Try flashing my 1.0 kernel with odin: http://www.cheatersedge.org/android/boot.tar

Fenny said:
Try flashing my 1.0 kernel with odin: http://www.cheatersedge.org/android/boot.tar
Click to expand...
Click to collapse
Nope that did not work either.

ab102 said:
Nope that did not work either.
Click to expand...
Click to collapse
So, it just hangs on the bootloader screen whenever you flash a custom kernel, but it will boot to a custom recovery... does that sound about right?

Fenny said:
So, it just hangs on the bootloader screen whenever you flash a custom kernel, but it will boot to a custom recovery... does that sound about right?
Click to expand...
Click to collapse
yes it hangs on the boot screen and says Kernel is not se android enforcing (in red) below that it says Set Warranty Bit: kernel (in yellow)....for me to go into custom recovery i have to do volume up power and menu buttom, download mode vice versa.

[Solved] Need help with installing Cyanogenmod (Without a PC if possible)

Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.

Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app

jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!

KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.

dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.

KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.

dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.

KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.

Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app

Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?

KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband

Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.

KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.

Here is the info mrrocketdog

Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.

audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse

KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?

Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop

Root Marshmallow 6.0 Update

Hello I was able to easily root the newly released 6.0 update for the sprint galaxy s6.
First download
Cfroot for the G920F model
Download
Flash with Odin 3.10.6 or higher..
Wait for the script to finish etc and once the phone reboots, force the phone into download mode and flash the stock 6.0 recovery
Download
Then force the phone back into recovery mode and wipe cache then reboot phone back to system
Enjoy rooted 6.0 MM !
Props to the mighty Chainfire and his wizard skills

ok am i waiting when it attempts to boot recovery or just press the buttons to boot it into download again to re flash the stock recovery?

All we need now is twrp. I havent tried this root process yet.

weirdfate said:
ok am i waiting when it attempts to boot recovery or just press the buttons to boot it into download again to re flash the stock recovery?
Click to expand...
Click to collapse
after flashing cfroot you must wait until it finished the process..it will take a min...then after cfroot tells you it's done rooting the phone...you flash the stock recovery

Sunderwear said:
after flashing cfroot you must wait until it finished the process..it will take a min...then after cfroot tells you it's done rooting the phone...you flash the stock recovery
Click to expand...
Click to collapse
i must be doing it wrong then? it attempts to boot a recovery that is not seandroid enforcing last time i tried to install the custom recovery that was for the older firmware it stuck on that screen for ever and i needed to reflash my phone. just a little worried that its gonna get stuck there.
thank you for finding this root method

weirdfate said:
i must be doing it wrong then? it attempts to boot a recovery that is not seandroid enforcing last time i tried to install the custom recovery that was for the older firmware it stuck on that screen for ever and i needed to reflash my phone. just a little worried that its gonna get stuck there.
thank you for finding this root method
Click to expand...
Click to collapse
for me it was stuck in seandroid enforcing for like 1-2 mins...then it went to the cfroot screen

Sunderwear said:
for me it was stuck in seandroid enforcing for like 1-2 mins...then it went to the cfroot screen
Click to expand...
Click to collapse
yep
i waited then it went into cfroot
we got a dump of the stock recovery (im assuming thats what the other file is to flash) so im sure it wont be long till we get a custom recovery:good:

Confirmed, works for boost mobile 6.0.1 marshmallow.

Would TWRP 3.0.0 work with this or are we gonna have to wait for that update? Need my xposed modules for sure

We dont need a MM twrp....the current twrp will work just fine to flash a MM custom rom, someone just needs to make a rom.zip we flash it on top of LP and profit.

rafyvitto said:
We dont need a MM twrp....the current twrp will work just fine to flash a MM custom rom, someone just needs to make a rom.zip we flash it on top of LP and profit.
Click to expand...
Click to collapse
I also just realized that xposed won't work without a deodexed rom

122ninjas said:
I also just realized that xposed won't work without a deodexed rom
Click to expand...
Click to collapse
Can't we use flashify to install zip files? I've used xposed on stock ROMs before I thought.

will this work for 925p?

Awesome now i can mess with titanium backup. . Thanks Guess supersu is not working it says no su in the binary. Redid the steps i used odin 3.10.7 it didnt boot after the cfauto was flashed it actually booted into recovery is not seandroid enforcing. forced into download mode pushed down restarted again it went to the recovery is not seandroid enforcing screen. So i flashed the recovery cleared cache phone booted thought i was good to go nope lol. Also the same happened when i tried the twrp with odin but i had to flash the rom to get back up and running so heads up.

Guys I would definitely wait for a custom recovery. What if something happens and you have no backup?! Also, you need a deodexed ROM for Xposed to work anyway! This method would be good if all you care about is little stuff like AdBlocking.

you don't need deodexed rom anymore there is an exposed that work on 5.1.1 adn 6.0 but we just need a recovery to flash it.
but i agree i would wait to have a confirmed recovery for marshmallow

cyberone3 said:
you don't need deodexed rom anymore there is an exposed that work on 5.1.1 adn 6.0 but we just need a recovery to flash it.
but i agree i would wait to have a confirmed recovery for marshmallow
Click to expand...
Click to collapse
Prettttyy sure you need a deodexed ROM.

link below is the exposed i have been using on "stock" rom 5.1.1 and there is a 6.0 version i was on 5.1.1 no changes other than root
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
"Samsung made a lot of changes to ART without providing the sources, that's why it took a while to workaround some of their changes, more information here.
It supports Stock and close to stock Roms."

cyberone3 said:
link below is the exposed i have been using on "stock" rom 5.1.1 and there is a 6.0 version i was on 5.1.1 no changes other than root
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
"Samsung made a lot of changes to ART without providing the sources, that's why it took a while to workaround some of their changes, more information here.
It supports Stock and close to stock Roms."
Click to expand...
Click to collapse
I'm totally down to be a test dummy lol. Can anyone explain if flashify would be a replacement for recovery? I know the international folks used it to prevent certain things from tripping Knox, but at this point I'm pretty sure we all have tripped it by now

JoeFCaputo113 said:
Guys I would definitely wait for a custom recovery. What if something happens and you have no backup?! Also, you need a deodexed ROM for Xposed to work anyway! This method would be good if all you care about is little stuff like AdBlocking.
Click to expand...
Click to collapse
southernstyle said:
I'm totally down to be a test dummy lol. Can anyone explain if flashify would be a replacement for recovery? I know the international folks used it to prevent certain things from tripping Knox, but at this point I'm pretty sure we all have tripped it by now
Click to expand...
Click to collapse
flashify didn't work when i tried it wants twrp or cwm

Want to root Friends Note 4, a few questions.

Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?

The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk

How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.

rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk

samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.

rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk

Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.