Database Users

[Q] Help : Boot Loop When Flased CF Root

Hi Guys,
I got a shiny new Note 4 (SM-N910F). I wanted to root asap , as like my other phones. I went to the CF-Root thread , downloaded the appropriate file i.e " CF-Auto-Root-trlte-trltexx-smn910f.zip and flashed it via Odin.
Now i am stuck in a boot loop where it just says recovery booting and restarts. I tried to flash the Cf-root file twice but the same thing happens. However i can go into the download mode just fine.
I am on 4.4.4
Can any1 please guide me here ? would be very thankfull.

So luckily i had the stock recovery backed up , i flashed that with odin and its back in the OS now. But whenever i try to flash the CF root Tar, it gets stuck in boot loop

Lowresolution said:
Hi Guys,
I got a shiny new Note 4 (SM-N910F). I wanted to root asap , as like my other phones. I went to the CF-Root thread , downloaded the appropriate file i.e " CF-Auto-Root-trlte-trltexx-smn910f.zip and flashed it via Odin.
Now i am stuck in a boot loop where it just says recovery booting and restarts. I tried to flash the Cf-root file twice but the same thing happens. However i can go into the download mode just fine.
I am on 4.4.4
Can any1 please guide me here ? would be very thankfull.
Click to expand...
Click to collapse
Flash / download new firmware from sammobile.com , then boot into recovery , make full wipes , and done !

Got it . Thanks .
Can i just flash another region firmware for my model?

Please Help Very Frustrated.

hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:

dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that

Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens

Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann

vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?

dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk

dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom

Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.

I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue

Unable to install custom recovery and flash custom roms on rooted note 3 lte

I am on a UK (vodafone) phone 4.4.2 KK and after rooting with odin and tripping knox (obviously) i installed CWM And TWRP and entered recovery but only after a long time i discovered that the recovery mode i was entering was stock .
In the recovery mode i couldnt find the option to install from zip only the option to install from external storage.
I have downloaded the CM 11 4.4.4 and put it on the external sd card.
In the recovery mode i navigated to the location of the CM 11 zip and attempted to flash it .
It goes through the process and at the end it says something like installation successful but the the phone boots into the normal stock firmware.
After reading a ton of material and articles i have discovered that my bootloader may be locked and this is the reason i cannot install CWM and flash custom roms.
In the end i have 3 questions.
Is there curently a solution to install CWM and flash custom roms on phones with locked bootloders ?
Will i be able to update to lollipop via Kies when is released ?
Will i be able to return my phone to its original state so that the lollipop update when it is released wont detect that the phone has been modified ?
Basically i am stuck. I have a rooted phone with void warranty and unable to install roms because the bootloder is locked ??????
I would really apreciate some help because i have run out of options and the frustration has reached stratospheric levels.
Thanks in advance for your help.

You rooted with ODIN and installed both CWM and TWRP .Thats all wrong odin is not root and you don't flash two recovery s .
You say your bootloader is locked = what model phone do you have .
Its reading as fail read the very basics .
Start at the beginning at for that you need to know what model number you have . You then find the correct root for your model and flash a recovery either CWM or TWRP not both .

JJEgan said:
You rooted with ODIN and installed both CWM and TWRP .Thats all wrong odin is not root and you don't flash two recovery s .
You say your bootloader is locked = what model phone do you have .
Its reading as fail read the very basics .
Start at the beginning at for that you need to know what model number you have . You then find the correct root for your model and flash a recovery either CWM or TWRP not both .
Click to expand...
Click to collapse
I did not flash both.
I only installed both and tried to flash either.When i saw that i couldn flash one i tried the other one.
My phone model number is SM-9005 ..
The root file i used was CF-Auto-Root for SM-N9005 .

uxaar said:
I did not flash both.
I only installed both and tried to flash either.When i saw that i couldn flash one i tried the other one.
My phone model number is SM-9005 ..
The root file i used was CF-Auto-Root for SM-N9005 .
Click to expand...
Click to collapse
Flash this in Odin.
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Sent from my SM-N9005 using Tapatalk

Untick auto reboot in Odin when you flash recovery then boot to recovery using three button combo stock ROM rewrites stock recovery when it boots iirc

celderic said:
Flash this in Odin.
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
That worked flawlessly and afterwards i managed to install CM12 5.1.
you saved me .Thanks again

TWRP install boe5

I cant install TWRP with odin.
Odin show me PASS, but when i want to go into recovery i cant (only stock recovery works) ;/
What i must to do? Thanks for help!

Mati0807 said:
I cant install TWRP with odin.
Odin show me PASS, but when i want to go into recovery i cant (only stock recovery works) ;/
What i must to do? Thanks for help!
Click to expand...
Click to collapse
Hello mati0807
One month ago i have same pb impossible to Install twrp i get same response
after the goods helps of xda i success custom recovery installation
In resume :
Change usb cable ( use original )
Check Samsung usb drivers ( yu Install kies )
Use Odin v3.09 ( works good for me )
Reinstall Os like windows XP or Seven ( if yu have installed it for many years ago )
This linkhttp://forum.xda-developers.com/galaxy-s5/general/trick-how-to-success-odin-flash-newbies-t3195645
Have Nice day !:highfive:

Thank you! its not work for me, but i did it!
1. uncheck autoreboot in odin
2. Download CWM (not TWRP or Philz > its not work for me in first time) http://forum.xda-developers.com/showthread.php?t=2697523
3. Set CWM in AP and press start
4. When it PASS, manually power off phone, and start it to Recovery
5. And now you must install TWRP or Philz again. (dont turn on the phone, only download mode)

Same problem / Still not working
Hey guys,
I have the same problem here.
The other thread ( http://forum.xda-developers.com/galaxy-s5/help/custom-recovery-protection-samsung-t3135004 ) suggested going back to an older rom version.
I have tried every other combination of flashing CF / CWM / TWRP but the outcome is the same.
No working recovery.
Is there a possibility without reverting to an older rom, as the BOE5 is not named in the other thread?

Hey guys,
got it working for me.
I flashed G900FXXU1ANG2_G900FDBT1ANG2_DBT via Odin and got a bootloop at first.
Then flashed twrp-2.8.7.0-klte.img in dowload mode
--> boot to recovery, wiped everything, installed custom rom (newest cdroid version) and super su --> phone booted, with root and installed custom rom with 5.1.1

Stuck in a never-ending bootloop after trying TWRP for SM N9005

My phone is a Samsung Note 3 SM-9005, currently it's stuck in an infinite bootloop even after removing the battery for an hour.
I get this message:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... along with the Samsung SM-N9005 logo, a couple of beeps/buzzes and then it repeats ad infinitum.
Here's what I did over the last day to get to this sorry state of affairs:
1. Upgraded from Android 4.3 (the original operating system) to 5.0 using the Samsung N9005XXUGBOA5 ROM with Odin 3.12. This worked fine but the phone lost root.
2. I rooted the phone again using Odin and Chainfire Auto-Root. All good so far.
3. I installed TWRP (the official TWRP App 1.5, going by my records)
4. I flashed the latest custom recovery which would have been 3.0.x and this seemed to be fine. So far no problems.
5. I then got ideas above my lowly station, apparently. I wanted to flash one of the newer ROMs: [Rom][N7 Port][12.12.2016] [Multi-DPI] Phronesis Rom N7 v4.1 Feature Rich & Smooth
https://forum.xda-developers.com/ga...m-phronesis-mm-rom-v1-0-feature-rich-t3463244
6. In the instructions, it said to use TWRP recovery version 2.8.7. I found that and flashed it. (Yes, it was for the Samsung SM N9005).
7. I rebooted into recovery mode to make a backup with that 2.8.7 version.
8. Now I'm stuck in boot loop hell with ...
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... with the Samsung SM-N9005 logo, a couple of beeps/buzzes and so on (as stated above).
I've tried leaving the battery out for an extended period and this hasn't worked. The phone never gets to the stage where I can talk to it with Odin or get any kind of menu. Is the phone truly bricked now?
If so, was it a critical error to go from the 3.0.x TWRP recovery back to 2.8.7 for the purposes of this custom ROM upgrade?
If not, what can be done to regain control of the phone?
This is obviously an older phone as I've had it for about 3 years now, but I'd love to get it working again if possible. I really loved it and was planning to use it for a couple more years (hence the upgrade path I've explained above).

Can you boot into download mode? I suspect you flash the 4.3 version of twrp, you need a 4.4 version. This one https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Boot into download mode and flash it with odin.

I suggest flashing the latest stock ROM, flash the latest tar version of twrp with Odin, root with supersu.zip in twrp.

Stonedead, you were right on the money. I did what you suggested (Download mode) and that different TWRP file, and it worked.
Thanks so much.
Thanks audit13 also, although I didn't need to go that far to undo my mistake.

I got the same problem with my note 3. Thank you for the solution. Now how do I exactly get TWRP working on my phone. It is already rooted.

See TWRP thread.
Basics flash twrp tar through odin

Root is not needed to install the tar version of TWRP with Odin.

Thanks. Managed to get twrp working now. Also installed the note 8 Rom

Hi ok im having the same problem kinda follow the installation as posted,so i have note 3 sm-n9005 stock rom,root and replaced twrp 4.3 for 4.4 to install phronesis n7 v7 for note 3 followed all instructed then rebooted went to samsung boot then booted to twrp recovery ive been on it all day thinking what da hell ive done wrong?can someone instruct me of what i did or didnt do or have i completely mess stuff up?cheers anyone.

instructions .
Boot into recovery (say TWRP 2.8.7.0)

JJEgan said:
instructions .
Boot into recovery (say TWRP 2.8.7.0)
Click to expand...
Click to collapse
Sorry jjegan not following?it already reboots into twrp recovery after the galaxy note 3 logo appears for 20 seconds?I have read and followed threads that have same or similar problems but no avail im am totally lost and from reading this rom it sounds great if I can get there that is,so please simple instructions would be very helpful as I'm still learning very sorry for being dumb.

This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com

JJEgan said:
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
Click to expand...
Click to collapse
Hi JJEgan,thank you for the reply back much appreciated for your time so far,so do you mean twrp-2.8.7.0-hlte-eu.tar file?and not twrp 2.8.7.0-hlte-4.4 img.tar file?that's the one I am using to flash the rom with and having problems with.

Hi there again ok im so confused not sure which one,there are so many of the 2.8.7.0 versions with 4.3 or 4.4-img.tar im not sure if im downloading 4.4 or 4.3 as im still a noob and love tech,I have read threads upon this rom problems still can't get the grasp of the simple twrp version I have lte au version android 5,and when I read 2.8.7.0 im think is it 4.4 4.3 or just 2.8.7.0 tar file?I'm following the installation up into the problem of not booting up in stays In galaxy note 3 boot and I have removed the battery 5mi z replaced then recovery and factory reset then it does the same again and I have tried 3 times waited longer each time im thinking maybe go back to stock I don't think my phone is agreeing with me,jjEgan thanks for the info amd time im sorry if annoy you with a simple installation to you,still I have read and grasp the concept of twrp installer version yeah??

Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .

JJEgan said:
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
Click to expand...
Click to collapse
Thanks for the reply JJEgan,no I have finally fix the problem solution start over fresh instalments installed stock,flash twrp 4.4, flashd supersu threw twrp,wiped 3x install,instead of rebooting threw Aroma rebooted system threw twrp it loaded first go,thanks for the threads I took bits n pieces frm each threaded problems,cheers JJEgan love the version rom,one more thing what kernel would be better or what would your choice be cheers