Related
I rooted my phone like 30 minutes before the latest update came out (LG2) and when a friend was playing with it, he updated it. Now it appears I do not have root anymore. How can I get this back so I can flash the CM10 rom on here? If I open super user my first 2 sets of data under "su binary v3.1" are red and then the 3rd item which is /system/xbin/su is green. Let me know if there is any other data I can provide to help assist. Thank you so much!
I lost root last week, titanium backup failed, super user was denied access etc. I tried to update binaries but that didn't work either. However when I booted into recovery it was still clockwork recovery not stock. So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me. If you boot into recovery and it's the stock recovery then my guess is you will probably need to reroot via the Odin method.
coogrrr94 said:
I lost root last week, titanium backup failed, super user was denied access etc. I tried to update binaries but that didn't work either. However when I booted into recovery it was still clockwork recovery not stock. So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me. If you boot into recovery and it's the stock recovery then my guess is you will probably need to reroot via the Odin method.
Click to expand...
Click to collapse
I have CWM installed and i can do the volume,home button, power on button and load into it, but whenever i run any package (includind CWM_superuser.zip i get an error saying Esignature failed. I tried reflashing the CWM but when i open odin i cant get it to show the phone and light up the com port box... any other ideas?
You can't flash the root from recovery zip either? If you haven't tried, that should reroot your phone.
flonker said:
You can't flash the root from recovery zip either? If you haven't tried, that should reroot your phone.
Click to expand...
Click to collapse
Nope gives me the same esignature failure
What about adb?
When you're in CWM recovery you should be able to disable signature verification.
coogrrr94 said:
So all I had to do to regain root was to flash the cwm_superuser zip then the latest teamepic-root-from-recovery zip. It worked for me.
Click to expand...
Click to collapse
Hi. Can u be more specific how u did that. I want also regain my root
kanon104 said:
Hi. Can u be more specific how u did that. I want also regain my root
Click to expand...
Click to collapse
Boot into recovery> go to install zip from sdcard>click on toggle signature verification
That should disable it. Its on by default.
Sent from my SGH-I747 using xda app-developers app
Hostage XII said:
Boot into recovery> go to install zip from sdcard>click on toggle signature verification
That should disable it. Its on by default.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I just did the odin thing again and it worked. What Spring Galaxy means btw?
Ran into Same issue, but still had clockwork mod in reboot, so......
How to regain root if cwm is working is just to reflash team epics root recovery zip in recovery....thats it!!!
Walla
Im not the first to have this issue and not the last, may come to be very difficult in future, whos to say, but if it helps...thanks is appreciated!!
I recently purchased this SGS3, installed CWM and rooted it. Everything was going great - but then i was offered the most recent OTA update, so i reflashed the stock recovery via Odin, did the update which is:
4.0.4
T999EVLH2
same kernel
bld #: IMM76D.T999EVALH2
now, its saying the phone is no longer rooted (yet superSU is still there) but checkroot is saying that it isnt rooted, and no matter what i do, flashing CWM via Odin passes, but will not stick (as in, i boot into recovery mode and that damned stock recovery is STILL THERE, wtf?)
can anyone offer any assistance or insight into my issue.
Thanks
~Wikkid
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Aerowinder said:
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Click to expand...
Click to collapse
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
mikewikkid said:
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
Click to expand...
Click to collapse
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Aerowinder said:
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Click to expand...
Click to collapse
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
mikewikkid said:
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
Click to expand...
Click to collapse
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/jv6pHg8b
Aerowinder said:
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/sUJixYID
Click to expand...
Click to collapse
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
mikewikkid said:
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
Click to expand...
Click to collapse
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Aerowinder said:
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Click to expand...
Click to collapse
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
mikewikkid said:
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
Click to expand...
Click to collapse
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
xanderman said:
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
Click to expand...
Click to collapse
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Aerowinder said:
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
Click to expand...
Click to collapse
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Thistleknot said:
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Click to expand...
Click to collapse
Umm, 2 things....
You realize this thread is over a year old and the last post was over 9 months ago?
And those links look like they are for the S4....
Sent from my SGH-T999V using Tapatalk 4
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.
I've used Odin 3.07 to flash n900t-cwm-recovery-6.0.4.4(1025) but it didn't pass. I'm tired now and I want to go to bed but it bugs me I don't have root.
On 4.2 I think it was easy but on 5.0 it won't work for me, now. I've scoured pages and pages, so for now I am kindly asking for some directions.
Try flashing the latest TWRP and then flash supersu from TWRP to get root.
audit13 said:
Try flashing the latest TWRP and then flash supersu from TWRP to get root.
Click to expand...
Click to collapse
Thanks, did it, it flashed it but now it gives me "Recovery is not Seandroid Enforcing". I pulled the battery right after the pass message, no change.
Read in thread about "Reactivation Lock" but I don't have that option in the stock Lollipop 5.0.
Any ideas?
So your phone is not booting? Boot into download mode and tell us what it says.
Oh no, the phone works fine. I can boot into stock Lollipop but it won't boot into recovery (Vol Up). It boots into Odin Vol Down.
All I want is to install su. First I tried to flash CWM recovery with Odin, didn't pass. Then I tried TWRP (their website is down), it passed but got "Recovery is not Seandroid Enforcing" error. So now I'm lost. I think all have to flash a modified ROM but I'm confused about their specs (what is Deoxified)
Wait wait, Oding IS the recovery, no? I'm totally confused now.
Try this: open Odin and uncheck everything except f.reset time, connect the phone, flash TWRP, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, use button combination to boot into recovery.
Thanks for the help. I've tried that sequence before. It didn't work. I'll try it again.
But I've managed to install su using Chainfire's Auto Root for Kitkat (but I have Lollipop). Now I have an older recovery. Will that cause any troubles?
What I've learned from my "ordeal" is make sure you have the right versions. In my case particularly the phone model, N900T, and then the software versions, N900TUVUFOB6, where B6 is the Lollipop (right?).
No no no!
I've rebooted into old recovery now my user interface in Lollipop doesn't work. I guess the recovery deleted some cache (noticed some messages at the bottom)
I guess I'll burn the Lollipop + CF Autoroot for the N-th time and never boot into recovery.
Bogdan45 said:
I've used Odin 3.07 to flash n900t-cwm-recovery-6.0.4.4(1025) but it didn't pass. I'm tired now and I want to go to bed but it bugs me I don't have root.
On 4.2 I think it was easy but on 5.0 it won't work for me, now. I've scoured pages and pages, so for now I am kindly asking for some directions.
Click to expand...
Click to collapse
Do you still need help? If so reply back. I'll do way best to help. Had the three main custom recoveries and had my share of problems and learned from them haha.
LiftedDroid said:
Do you still need help? If so reply back. I'll do way best to help. Had the three main custom recoveries and had my share of problems and learned from them haha.
Click to expand...
Click to collapse
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.
Bogdan45 said:
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.
Click to expand...
Click to collapse
I used chain fires autoroot 9005, and installed TWRP
Sent from my SM-N9005 using Tapatalk
Bogdan45 said:
Yes, I do need a working recovery for stock Lollipop 5.0 on Note 3.
Click to expand...
Click to collapse
Sorry was busy last few days with minecraft lol. I will get that up in a few and have link for you
Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app
No, I don't have it.
tenjohn23 said:
Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Make sure you have patched sd access and set correct path for location.
SD patch
Or use this this version of twrp and open in Odin just as you would cf autoroot.
Uploading now
---------- Post added at 01:40 ---------- Previous post was at 01:30 ----------
tenjohn23 said:
Hi there,
I have one question. I have rooted my phone with cf-autoroot method same as you and like you I can't installed custom recovery, weather it be TWARP or CWM. Buy my question isn't this.
I was just randomly checking my app manager for all my apps and found getroot version 1.0 was installed.
Can you confirm me that u have the same thing.
Because it has access to my camera SD card and sms.
Let me know.
Sent from my SM-N900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Make sure you have patched sd access and set correct path for location.
TWRP 2.8.7 Open Recovery
SD patch
Or use this this version of twrp and open in Odin just as you would cf autoroot.
TWRP 2.8.7.0 4.4
Also thesee are for smn900t I am sure as long as your using any snm900* you OK. Any issues try hard reset and last option do reflash of stock
Bogdan45 said:
Oh no, the phone works fine. I can boot into stock Lollipop but it won't boot into recovery (Vol Up). It boots into Odin Vol Down.
All I want is to install su. First I tried to flash CWM recovery with Odin, didn't pass. Then I tried TWRP (their website is down), it passed but got "Recovery is not Seandroid Enforcing" error. So now I'm lost. I think all have to flash a modified ROM but I'm confused about their specs (what is Deoxified)
Wait wait, Oding IS the recovery, no? I'm totally confused now.
Click to expand...
Click to collapse
the enforcing thing is because you have a custom recovery only, it just tells the user that it isn't factory
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 ?