[Help] Forgot to install SuperSu - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

When I 'reboot'ed to restore, I was clicking 'reboot' without thinking twice. I realized I didn't install SuperSu in it. I had SuperSu app but I didn't install it yet. So I went ahead, rebooting until the logo showed up but it shut. Again, the logo showed up and it shut. It was going on.
One simple question- HOW DO I FIX?!
I feel stupid as a elephant.
Thanks!

Go to the play store and install it.

w7excursion said:
Go to the play store and install it.
Click to expand...
Click to collapse
I already had it installed before. Nothing happened.

What are you trying to do that is related to super su?

w7excursion said:
What are you trying to do that is related to super su?
Click to expand...
Click to collapse
Well, at first, I added SuperSU and then I added TWRP. I realized I hadn't installed SuperSU from Play Store yet. Then BOOM. The logo kept restarting. What should I do?
I just wanted to add a Noterized rom later but....

What did you root with? I thought Cf auto root installed it during the root process. http://forum.xda-developers.com/showthread.php?t=1538053

w7excursion said:
What did you root with? I thought Cf auto root installed it during the root process. http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I did follow what it said and nothing happened! I didn't understand!
http://grantbarker.com/samsung-galaxy-note-4.html --- This is what I followed Rooting and Flashing. SuperSu appeared in my Note 4. I thought it was all set. So I went ahead to reboot but it didn't work. The logo kept appearing and then disappearing. Forth and back. I didn't understand what did I do wrong.

Link which cf auto root file you used . Hit the thanks to chainfire http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 and should be this one https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip

w7excursion said:
Link which cf auto root file you used . Hit the thanks to chainfire http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428 and should be this one https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip
Click to expand...
Click to collapse
That's the link I downloaded. :crying:

idavyko said:
Well, at first, I added SuperSU and then I added TWRP. I realized I hadn't installed SuperSU from Play Store yet. Then BOOM. The logo kept restarting. What should I do?
I just wanted to add a Noterized rom later but....
Click to expand...
Click to collapse
You're not very good at describing the steps, your current situation, firmware you started with or answering questions so my response may be out in left field; you decide.
Did you happen to have OE1 or OF5 build before you started?
When you you say the logo kept restarting, did you leave out a step? Sounds like you used Odin to flash CF Auto Root, TWRP and proceeded to flash a custom ROM and it didn't boot.
Did you forget to do a much needed step of taking a nandroid backup as soon as you got to TWRP recovery?
Did not restart... Two things you can do. If you have the nandroid backup from TWRP, use it.
If you don't have it, flash the Odin CF Auto Root and try to reboot. If it boots, note the build and make a nandroid.
Most common mistake made in XDA in past weeks is trying to downgrade builds OE1 and OF5 to take a custom ROM when it's not supposed to happen. Bugs and reboot issues galore. And no way to upgrade until a stock recovery is found or a tar released.
Read and you may find some answers to your situation, if I'm out of bounds.
Sent from my SM-N910P using Tapatalk

samep said:
You're not very good at describing the steps, your current situation, firmware you started with or answering questions so my response may be out in left field; you decide.
Did you happen to have OE1 or OF5 build before you started?
When you you say the logo kept restarting, did you leave out a step? Sounds like you used Odin to flash CF Auto Root, TWRP and proceeded to flash a custom ROM and it didn't boot.
Did you forget to do a much needed step of taking a nandroid backup as soon as you got to TWRP recovery?
Did not restart... Two things you can do. If you have the nandroid backup from TWRP, use it.
If you don't have it, flash the Odin CF Auto Root and try to reboot. If it boots, note the build and make a nandroid.
Most common mistake made in XDA in past weeks is trying to downgrade builds OE1 and OF5 to take a custom ROM when it's not supposed to happen. Bugs and reboot issues galore. And no way to upgrade until a stock recovery is found or a tar released.
Read and you may find some answers to your situation, if I'm out of bounds.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Whoa, what? What OE1 and OF5? How do I know? OMG, I feel stupider now. I thought backup was from TWRP but oops. Where do I find nandroid backup?

idavyko said:
Whoa, what? What OE1 and OF5? How do I know? OMG, I feel stupider now. I thought backup was from TWRP but oops. Where do I find nandroid backup?
Click to expand...
Click to collapse
If it boots to TWRP recovery, check both the ext and sd card for backup when selecting the restore tab. I think it defaults to where you backed it up but check anyway. There's a tab button to select location in the restore menu.
No backup? Reflash CF Auto Root and reboot. If it boots, go back to recovery and make a backup in TWRP recovery.
If you don't have TWRP, flash in Odin and do the above steps.
Sent from my SM-N910P using Tapatalk

samep said:
If it boots to TWRP recovery, check both the ext and sd card for backup when selecting the restore tab. I think it defaults to where you backed it up but check anyway. There's a tab button to select location in the restore menu.
No backup? Reflash CF Auto Root and reboot. If it boots, go back to recovery and make a backup in TWRP recovery.
If you don't have TWRP, flash in Odin and do the above steps.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I reflashed CF Auto Root and rebooted it. It said FAIL. Not working successfully.
https://download.chainfire.eu/585/CF-Root1/CF-Auto-Root-trltespr-trltespr-smn910p.zip - I used it for CF AUTO. I don't know how it happened. : (

In the settings go look in the "About Device" and see what the software version is. Hopefully not the two versions mentioned earlier.

There's also instructions in the CF Auto Root for flashes not taking. Something like if you don't see the red android in recovery, pull battery and reboot to recovery... Follow the OP.
Sent from my SM-N910P using Tapatalk

w7excursion said:
In the settings go look in the "About Device" and see what the software version is. Hopefully not the two versions mentioned earlier.
Click to expand...
Click to collapse
That's a major problem... I can't EVEN get in homescreen at all. I am at where Samsung logo restarting is. Not even get in homescreen at all.

samep said:
There's also instructions in the CF Auto Root for flashes not taking. Something like if you don't see the red android in recovery, pull battery and reboot to recovery... Follow the OP.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Done there, done that many times. There is NO red android in recovery. I see a green android every time I try to reboot.

I'm sure you tried this but it's a step process: Odin flash CF with auto boot enabled. If you don't see red Android, pull battery and boot directly into recovery.
No boot after that? Try boot into recovery again. Factory reset a few times and try to reboot. If that's a dead horse, you can try to flash OB7 modem in Odin (extract from OB7 stock tar) and flash noterized stable 2. Consider wiping all but ExtSdCard and flash again if still won't boot. But know you're in a realm of risks that you must weigh for yourself. I'm not liable for a brick.
Sent from my SM-N910P using Tapatalk

samep said:
I'm sure you tried this but it's a step process: Odin flash CF with auto boot enabled. If you don't see red Android, pull battery and boot directly into recovery.
No boot after that? Try boot into recovery again. If that's a dead horse, you can try to flash OB7 modem in Odin (extract from OB7 stock tar) and flash noterized stable 2. But know you're in a realm of risks that you must weigh for yourself. I'm not liable fit a brick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
OK Show me OB7 link.
I haven't installed Noterized Stable 2 yet.

*rolls in a wheelbarrow full of bricks*

Related

How to Clear flash count/Unroot/Become Stock Again

This morning I decided it was time for flash count clear/un-root / back to stock
I searched forum for hours finally finding something tucked away from clear view that would give me results I seeked.
This method took me about 10 min , successfully clearing count , doing away with root giving me factory out of the box ready for ATT store exchange if needed.
Many thanks to cortez.
This method was posted by cortez in chainfire root thread.
http://forum.xda-developers.com/showpost.php?p=33949289&postcount=51
cortez.i said:
@CF - donation made for your efforts with the "keep it simple root method"! this is the easiest method to root and then unroot that i've used. right after i rooted my device, i installed GooManager, flashed TWRP and began customizing my device. however, after a couple of days with my GN2, i've determined i'm not the targeted user for this device, so i unrooted and returned to att. this is a solid device, super fast, fluid with unlimited potential! In my case, I simply prefer the size of my S3.
my unroot, return to stock rom, stock recovery and Normal device status are listed below. AS ALWAYS I AM NOT RESPONSIBLE IF THIS FUBAR's YOUR DEVICE. i'm simply posting for informational purposes only. (not sure all of the steps below are are necessary):
Reboot to TWRP recovery to complete a factory reset
Used CF's method to re-root and reinstall the stock recovery (e.g., method listed in 2nd Post of this thread).
Purchased & installed Triangle-Away from market
Used Triangle-Away to reset the counter
After reboot (from step 4) uninstalled Triangle Away
Via SuperSU, used the Full Unroot option to unroot. Checked GN2 Device Status and it said Modified
Booted into stock recovery performed a factory reset.
After device rebooted, checked Device Status again and it said Normal
Returned the device to att corp store; att checked and confirmed device status (as Normal) and issued a refund.
CF, thanks again for your efforts!
Click to expand...
Click to collapse
I can vouch for that app used it twice flawlessly
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
45ACP1911 said:
I can vouch for that app used it twice flawlessly
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
funny thing happened to me after i returned my first Note2; i won another one at a special event the same day (evening)! seriously. i could not believe it!
glad the method i used worked for you. CF deserves all the credit for making it super simple!
cortez.i said:
funny thing happened to me after i returned my first Note2; i won another one at a special event the same day (evening)! seriously. i could not believe it!
glad the method i used worked for you. CF deserves all the credit for making it super simple!
Click to expand...
Click to collapse
If you got 2 sell me one :good:
Good stuff man. Definitely must know. Reported to be stickied so we dont lose this!
Instead of having a plethora of stickies, why dont you contact mjwhirly and see if he will add this to his post? http://forum.xda-developers.com/showthread.php?t=1987541
sling said:
This morning I decided it was time for flash count clear/un-root / back to stock
I searched forum for hours finally finding something tucked away from clear view that would give me results I seeked.
This method took me about 10 min , successfully clearing count , doing away with root giving me factory out of the box ready for ATT store exchange if needed.
This method was posted by cortez in chainfire root thread.
http://forum.xda-developers.com/showpost.php?p=33949289&postcount=51
Click to expand...
Click to collapse
So u are using the same tar file to root? This will install stock recovery?
Sent from the TermiNOTEr 2!
Thanks op. This will be very useful in case I ever need to return my phone or submit my phone in for warranty service. I was looking for a stock rom that could be flashed using odin, but couldn't find one.
scrosler said:
If you got 2 sell me one :good:
Click to expand...
Click to collapse
If I had 2 I would give you 1 and throw in a month of Straight Talk service .
borijess said:
So u are using the same tar file to root? This will install stock recovery?
Sent from the TermiNOTEr 2!
Click to expand...
Click to collapse
Not using a tar file to root.
If such file was available this thread title would read
***AT&T STOCK TAR FILE AVAILABLE!!!!***
I would throw in some big smileys it would be a party thread.
When you root using Chainfire method it provides Stock Recovery to fall back on.
http://forum.xda-developers.com/showthread.php?t=1980644
Thanks I did it worked flawlessly.
Sent from the TermiNOTEr!
Nice just what i needed to return my note 2 for replacement unit.
Not working for me
I tried this, to the letter, it didn't work.
I never did anything other than rooting using CF-auto root to root so I could restore from Titanium Backup.
I'm on the i317M.
I did a factory reset through the stock recovery (Would TWRP make a difference?), re-rooted using CF-auto root, installed Triangle Away, ran it, did a full unroot through SU, did another factory reset and still, device shows modified.
I don't know what I'm doing wrong. I desperately want to go back to stock.
EDIT: TriangleAway says: "on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!" - I am on a stock firmware! But it doesn't reset my status. In download mode, it still says "custom" - annoying!
Yossarian33 said:
I tried this, to the letter, it didn't work.
I never did anything other than rooting using CF-auto root to root so I could restore from Titanium Backup.
I'm on the i317M.
I did a factory reset through the stock recovery (Would TWRP make a difference?), re-rooted using CF-auto root, installed Triangle Away, ran it, did a full unroot through SU, did another factory reset and still, device shows modified.
I don't know what I'm doing wrong. I desperately want to go back to stock.
EDIT: TriangleAway says: "on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!" - I am on a stock firmware! But it doesn't reset my status. In download mode, it still says "custom" - annoying!
Click to expand...
Click to collapse
Yes TWRP could play factor.
If in your shoes I would,
Chainfire root.
Install TWRP using Goomanager
Make back up in TWRP then reboot device.
Boot into TWRP and install recovery
From there follow direction in op to get stock.
sling said:
Yes TWRP could play factor.
If in your shoes I would,
Chainfire root.
Install TWRP using Goomanager
Make back up in TWRP then reboot device.
Boot into TWRP and install recovery
From there follow direction in op to get stock.
Click to expand...
Click to collapse
What do you mean by "Boot into TWRP and install recovery"? Flash the stock recovery while in TWRP? Why do this if CF-autoroot will flash stock recovery anyway?
What I did:
CF-autoroot
Goomanager - install TWRP
Create backup in TWRP
Wipe /data and /cache in TWRP
Reboot into download mode
Flash CF-autoroot (flashes stock recovery)
Run Triangle Away
EDIT: SU Full Unroot (Yes I did this, I forgot to mention)
Check device status - still modified
Factory reset through stock recovery
Check device status - still modified.
What is preventing my device from reading "normal" where others have succeeded? It's puzzling. Anyway, thanks for all your help. I will probably just wait for a stock ODIN flashable firmware to make everything well again.
Yossarian33 said:
What do you mean by "Boot into TWRP and install recovery"? Flash the stock recovery while in TWRP? Why do this if CF-autoroot will flash stock recovery anyway?
What I did:
CF-autoroot
Goomanager - install TWRP
Create backup in TWRP
Wipe /data and /cache in TWRP
Reboot into download mode
Flash CF-autoroot (flashes stock recovery)
Run Triangle Away
Check device status - still modified
Factory reset through stock recovery
Check device status - still modified.
What is preventing my device from reading "original" where others have succeeded? It's puzzling. Anyway, thanks for all your help. I will probably just wait for a stock ODIN flashable firmware to make everything well again.
Click to expand...
Click to collapse
based on your reply, it appears you missed the step to open the SuperSU app and select the Full Unroot option. once this is done, then perform a factory reset from stock.
cortez.i said:
based on your reply, it appears you missed the step to open the SuperSU app and select the Full Unroot option. once this is done, then perform a factory reset from stock.
Click to expand...
Click to collapse
Yes sorry, I did that but forgot to add it to my post. My post is now edited.
There is an update for triangle away just run app and reset counter to zero.
Sent from my SGH-I317M using xda premium
jon3sh said:
There is an update for triangle away just run app and reset counter to zero.
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
But it doesnt remove modified status. Im trying and cant get it to normal.
Deleted...
Sent from my SGH-I317M using xda premium

Odin Says "Pass", But phone is not rooted.

Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Just download superuser and simply place it on your phones SD card it's really easy
Sent from my SPH-L710 using xda app-developers app
ricanjoe said:
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Click to expand...
Click to collapse
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
billard412 said:
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
Click to expand...
Click to collapse
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
ricanjoe said:
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
Click to expand...
Click to collapse
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
About to give it a shot. Placing the root file on my external SD and phone into download mode, about to launch the odin app on pc.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
ricanjoe said:
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
Click to expand...
Click to collapse
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
billard412 said:
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
Click to expand...
Click to collapse
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
ricanjoe said:
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
Click to expand...
Click to collapse
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
billard412 said:
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
Click to expand...
Click to collapse
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
ricanjoe said:
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
Click to expand...
Click to collapse
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
STOCK RECOVERY TAR
billard412 said:
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
Click to expand...
Click to collapse
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
ricanjoe said:
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
Click to expand...
Click to collapse
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
advocatebutdfh
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Click to expand...
Click to collapse
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
ricanjoe said:
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
Click to expand...
Click to collapse
No problem glad to help. And just in case u need it, the stock recovery tar is attached below.
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
Click to expand...
Click to collapse
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
ricanjoe said:
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
Click to expand...
Click to collapse
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
billard412 said:
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
Click to expand...
Click to collapse
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
ricanjoe said:
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
Click to expand...
Click to collapse
Personally I think the chances of your efs going bad are slim and a backup is more for paranoid people. With that said it never hurts to back it up. I just wouldn't restore it unless you have to.

Stuck in Odin Mode [from attempt to install a recovery rom]

I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.
Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.
Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.
Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.
So far so good. The lil blue loading bar is filling.
got back to rooting. but I didn't do anything else. haven't even went to super user
Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?
Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.

[Q] odin use AFTER -oe1...

after being sucked into the oe1 vortex, (they pulled a sneaky on me)... can we use odin just to root and/or install custom recovery(s), or is it locked out completely?... I know we cannot load roms, downgrade, etc. ... I want to root, install twrp or phils, and then probably load Noterized... but I need to know if Odin can be used to load cf-autoroot and then a custom recovery, AFTER having installed the -oe1 update... thanks in advance for any and all help...
Yes to root....no for unrooting
EpicBarbecue said:
Yes to root....no for unrooting
Click to expand...
Click to collapse
thanks, man... your screen name is way cool, too, btw, but it makes me hungry... again... so I can root it again thru cf-autoroot thru odin, then I will install phils or twrp... do u have a preference, phils or twrp?...
Lol no problem...i use TWRP...and im on OE1.
going to root when i get home, and then i will load twrp tomorrow... and then noterized... thanks...
mlongue1 said:
going to root when i get home, and then i will load twrp tomorrow... and then noterized... thanks...
Click to expand...
Click to collapse
... and I am pretty sure there is some bbq in my near future...
Hahaha no doubt.. had BBQ chicken for dinner...good luck my friend.
Disregard.
Sent from my SM-N910P using XDA Free mobile app
Yea cm used the oel base it fried all there roms lol now there rebasing to ob7 again lol
pbedard said:
Yea cm used the oel base it fried all there roms lol now there rebasing to ob7 again lol
Click to expand...
Click to collapse
So they are stuck on LP?
catseyenu said:
So they are stuck on LP?
Click to expand...
Click to collapse
OE1 is also LP, just newer firmware with a bootloader that prevents downgrading.
DreamingWolf said:
OE1 is also LP, just newer firmware with a bootloader that prevents downgrading.
Click to expand...
Click to collapse
So CM infected them with the bootloader of no return.
/SMH...
catseyenu said:
So CM infected them with the bootloader of no return.
/SMH...
Click to expand...
Click to collapse
Not really. When they re-base a ROM, they set it to work with the latest firmware (i.e. radios). They don't change the bootloader and CM doesn't flash one when it installs. So they didn't infect anyone. They were just trying to stay current with the latest firmware.
Thanks, that sounds a little better.
I looked in the Sprint Development forum and didn't see the posts, where is this being discussed?
So I'm stuck. Not my first rodeo by a long shot but my note 4 got the OE1 without my knowledge. No prior backup or even root on ob7. Had myself a big sigh and rooted through Odin, no big deal. Trying to install TWRP says it succeeds in Odin. But when I try to boot into recovery it fails and kicks to download mode. Is there a version of TWRP for this update or should I go back to Philz?
airplane_guy said:
So I'm stuck. Not my first rodeo by a long shot but my note 4 got the OE1 without my knowledge. No prior backup or even root on ob7. Had myself a big sigh and rooted through Odin, no big deal. Trying to install TWRP says it succeeds in Odin. But when I try to boot into recovery it fails and kicks to download mode. Is there a version of TWRP for this update or should I go back to Philz?
Click to expand...
Click to collapse
When you flashed TWRP did you have autoreboot checked in Odin? If you did you should edit Odin.ini and change the value of autoreboot from 1 to 0, save it then flash TWRP. This time after it says success it will just sit there. Remove the usb cord, pull the battery, then replace the battery and boot directly into recovery by vol up+home+power. I have found that TWRP often doesn't flash properly if you reboot into system instead of recovery immediately after the flash.
Sent from my SM-N910P using XDA Premium HD app
DreamingWolf said:
When you flashed TWRP did you have autoreboot checked in Odin? If you did you should edit Odin.ini and change the value of autoreboot from 1 to 0, save it then flash
Click to expand...
Click to collapse
I have never had that problem but I will check once I get home. I've never had to post here in 4 years since everything has already been answered, but I figured running around without a functioning recovery might not be the best option... Thanks.
i can now definitely and definitively confirm that that we can use odin, after -oe1, to root and load an alternate recovery such as twrp... i am now on twrp 2.8.6.0 , and i will be loading noterized sometime this weekend... i went with twrp to get used to it, as it is included in noterized...
airplane_guy said:
So I'm stuck. Not my first rodeo by a long shot but my note 4 got the OE1 without my knowledge. No prior backup or even root on ob7. Had myself a big sigh and rooted through Odin, no big deal. Trying to install TWRP says it succeeds in Odin. But when I try to boot into recovery it fails and kicks to download mode. Is there a version of TWRP for this update or should I go back to Philz?
Click to expand...
Click to collapse
hey, airplane guy, sounds as if u got jumped by -oe1 like me... i had a dm-verity error earlier last week, and when i finally borke down and re-loaded -ob7, they downloaded/loaded -oe1 when i went to the kitchen to get a drink... i had forgotten that AUTO-UPDATE is default ON... anyway, in my adventures this week of loading twrp, i found that just flashing it is not enough, u have to IMMEDIATELY boot/reboot to recovery, so the SCRIPT has a chance to OVERWRITE the auto-command to TRASH the recovery u just loade and revert to stock recovery... so when u reboot normally, without the auto-script over-writing the command, the revert-to-stock will overwrite your loaded recovery... u can watch it happen, mine kept saying ' installing update ', when i knew i was completely disconnected... after a ton of searching/reading/experimenting, i finally figured it out... i loaded flashify, let it download and install twrp, and then IMMEDIATELY WENT STRAIGHT TO RECOVERY, and watched the twrp auto-script overwrite the commands... and then twrp came up and i am good to go... if i had went straight to recovery after odin-flashing twrp the other day i could already have been done...
mlongue1 said:
hey, airplane guy, sounds as if u got jumped by -oe1 like me... i had a dm-verity error earlier last week, and when i finally borke down and re-loaded -ob7, they downloaded/loaded -oe1 when i went to the kitchen to get a drink... i had forgotten that AUTO-UPDATE is default ON... anyway, in my adventures this week of loading twrp, i found that just flashing it is not enough, u have to IMMEDIATELY boot/reboot to recovery, so the SCRIPT has a chance to OVERWRITE the auto-command to TRASH the recovery u just loade and revert to stock recovery... so when u reboot normally, without the auto-script over-writing the command, the revert-to-stock will overwrite your loaded recovery... u can watch it happen, mine kept saying ' installing update ', when i knew i was completely disconnected... after a ton of searching/reading/experimenting, i finally figured it out... i loaded flashify, let it download and install twrp, and then IMMEDIATELY WENT STRAIGHT TO RECOVERY, and watched the twrp auto-script overwrite the commands... and then twrp came up and i am good to go... if i had went straight to recovery after odin-flashing twrp the other day i could already have been done...
Click to expand...
Click to collapse
... going to load noterized this weekend...

Note 4 Marshmellow root not working!

So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess
aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk
imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!
Will the same method work on pj1 ?

Categories

Resources