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...
Related
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 finally have everything working again. I had the phone booting via the "unbrick" SD card last night but every attempt with 2 different MJB zip files failed. I eventually just found this one http://www.androidfilehost.com/?fid=23212708291681451by @loserskater and tried it and it worked. I can boot without the SD again. I did donate to him as a thanks.
First I followed this thread (and read through Mr x's thread as well) - http://forum.xda-developers.com/showthread.php?t=2549068
I was then able to boot the phone via the special SD card.
I then kept fighting with trying to get it to boot without the SD card. Since I could get to download mode I again ran CF-autoroot and I flashed TWRP 2.6.3.0 via ODIN. I kept booting to recovery and could not get either MJB bootloader that I found to work. I did get a status 6 when I tried CWM which indicated a syntax error or formatting error. I eventually found the zip file below and that worked via TWRP and then I was set.
I hope I remember everything - I was up until 4am and then didn't get a lot of sleep so I'm a little "fuzzy" now...
I will try to clean this up later for other's reference.
Edit 4: I can now get to TWRP by booting via an SD card with the unbrick file. I can also get into download mode. I tried flashing the MJB bootloader zip file via TWRP but it keeps failing. What is the next step to correct the bootloader problem if I had MJB and flashed the MJ2 bootloader (yes that was dumb...). How can I get the MJB bootloader files onto the EMMC again?
Help! I have flashed custom ROMs hundreds of times on my Captivate, Note, and Note2. My wife's S3 has been stock and had the OTA 4.3 update. After a few attempts, I did get root and TWRP 2.6.3.0 installed. I installed this ROM http://forum.xda-developers.com/showthread.php?t=2075639- was able to update SU and restored user some apps via TB. The "about device" still showed "enforcing and she had the MJB bootloader. I rebooted to recovery and again ran the "Knox removal script" which I had run a few times already. This time I ran it and then flashed the MJ2 bootloader from the OP. I can't get it to turn on now. I pulled the battery - no luck. I plug it into my laptop and I hear the sound of windows recognizing the device but it doesn't show up. If I leave the battery out and plug into the PC, then the red LED flashes. If it was my device I would be bummed but being my wife's phone, I really am hoping someone can help...
Edit: I have been trying the 3 button recovery and download options with no luck.
During my captivate days, I used a "JIG" for getting into download mode but am concerned even that won't help if there is a bootloader mismatch or something like that.
Edit2: Even though I have a black screen, I tried using ODIN and connected the phone and it says "added"! I will now look for a full bootloader flash via ODIN
Edit3: It seems like if I have the battery removed, hold the vol. down and home and then plug in the cable, ODIN recognizes it so I have a ray of hope but am still a bit "panicked". I am looking for a full MJB firmware flash via ODIN
Did you try and reboot into recovery (not download) and flash the MJB bootloader??? that is what worked for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
lfaulkner29 said:
Did you try and reboot into recovery (not download) and flash the MJB bootloader??? that is what worked for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That is what I have tried multiple times but it keeps saying failed. Can you send me a link to the exact zip file you used? Did you do anything such as flashing anything right before (supersu update), etc? I am very hopeful now knowing that you were able to get it to work.
Edit: I have a couple of .zip files that are supposed to apply the MJB bootloader files. One of them @loserskater posted comes up with a status 6 which I am researching now.
What recovery did you use TWRP or CWM? I've been trying both.
RichMD said:
That is what I have tried multiple times but it keeps saying failed. Can you send me a link to the exact zip file you used? Did you do anything such as flashing anything right before (supersu update), etc? I am very hopeful now knowing that you were able to get it to work.
Edit: I have a couple of .zip files that are supposed to apply the MJB bootloader files. One of them @loserskater posted comes up with a status 6 which I am researching now.
What recovery did you use TWRP or CWM? I've been trying both.
Click to expand...
Click to collapse
Updated the OP - resolved with the file I used.
RichMD said:
Updated the OP - resolved with the file I used.
Click to expand...
Click to collapse
what did you use to flash it?
Michael503 said:
what did you use to flash it?
Click to expand...
Click to collapse
I updated the OP with a link to the file.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
RichMD said:
I updated the OP with a link to the file.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
no, I mean what procedure.. did you finally get the file to go with TWRP?
I assume thats what you did, but I wanted to be sure. The procedure aught to be a sticky.
Michael503 said:
no, I mean what procedure.. did you finally get the file to go with TWRP?
I assume thats what you did, but I wanted to be sure. The procedure aught to be a sticky.
Click to expand...
Click to collapse
I just updated the OP with a bit more info. Let me know if that is the info you were looking for. As I mentioned, I am over-tired right now...
RichMD said:
As I mentioned, I am over-tired right now...
Click to expand...
Click to collapse
yeah, I'll bet.. stress is a *****... glad you got it licked though
Thx.
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*
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
Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.