Database Users

trying to root Note 4 5.1.1 on 910W8

Hey guys i followed this youtube guide for rooting 5.1.1 using TWRP Method https://www.youtube.com/watch?v=qpsGX_Xoxcg
i downloaded all the files but the firmware (not listen i have n910W8 = telus)
I have odin, supersu, TWRP (which n910w8 is listed) and samsung drivers.
I moved superSU and the TWRP file to root directory of note 4 5.1.1. rebooted into download mode, saw the blue indicator on odin and loaded the file. Rebooted holding volume up this time and tried to load the kernal but it doesnt exist.
I think im confused the TWRP file is NOT the kernal? Where can I get a kernal for n910W8 (telus)
thanks in advance!!

So I found this
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
which is telus 5.1.1 Rom. ill move this to my root directory and load the 910W8 TWRP file in odin and flash? Ill give it a try now wish me luck lol

ok i followed a guide online and now my phone just keeps restarting. I think im in big trouble. Im able to load openrecovery-twrp-2.8.1.0-trltecan.img into odin and boot to TWRP but now i cant load kernels? looked so easy to do now im down a phone? any help is much appreciated thanks!!!

You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.

ok so i loaded openrecovery-twrp-2.8.1.0-trltecan.img in AP (for my device) copied the custom rom
" cm-12.1-20150423-NIGHTLY-trltetmo" which was suppose to work with my 910w8 (910T) used recovery to flash it and also supersu it flashed OK... I restart and i see a little blue guy and its stuck optimizing apps. Suck in restart loop.
what did i do wrong? try a different kernel ?
thanks in advance
EDIT 1
im trying the " Tekxodus" rom. this file is way larger whats going on with that. Is it the same procedure to flash it?
EDIT 2
Flashed to tekxodus rom optimizing apps... now its stuck System UI has stopped. and I cant do nothing. Any suggestions? ?? ?
EDIT 3
Do I need to flash a certain BootLoader along with the recovery for my device (BL and AP) ? , reboot in recovery and flash the custom rom ie "Tekxodus" ?
found this guide for 910C
http://www.ibtimes.co.uk/how-root-galaxy-note-4-n910c-android-5-1-1-lollipop-1518168 with these steps
"Step-1: Download the flashable root package and transfer it to the storage of the phone
Step-2: Download Android 5.0.1 bootloader package. Extract it using any extracting tool and you should find a folder containing Odin flashable tar package and Odin binaries"
so confused lol

All you have to do is Odin stock 5.1.1 rom (COI4 i believe) then Odin TWRP then flash Tekxodus V3.2. Let everything optimize and let it sit there for a good 10 mins after optimization. Ignore what its doing. It will just work. No need to flash anything else unless you want Xposed, then you flash that right after flashing Tek (do not boot in between)

any idea where to get a custom kernel for 910w8 5.1.1 to root stock rom?

Im running this rom (flashed using odin)
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
stock telus rom. I loaded this rom by clicking BL in odin and selecting it (along with my recovery for telus 910w8). This was the only was to get my phone back into working order.
______-
I loaded my recovery for telus into odin and went to download mode.
booted into TWRP
Flashed Tekxodus V3.2.
Optimized apps for about 10 minutes and it just restarted and optimized again and again.
One time it said System UI has stopped and I was hooped.
not sure where I went wrong?
thanks for the response btw I really want to get this going cheers

equlizer said:
You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.
Click to expand...
Click to collapse
can i use any carrier software for the COI4? That's my only question. Thanks for helping!!

How to unlock note 3 bootloader : Secure download :Enable

On download mode my note 3 shows SECURE DOWNLOAD : ENABLE in blue colour which I guess means my bootloader is locked . Whenever I flash any custom rom like cyanogen mod or any custom kernel I get stuck on kernel is not seandroid enforcing set warranty bit kernel . I'm currently on stock lollipop rom .
so my question is how to unlock note 3 bootloader so I can flash custom rom (I can flash and boot rom darkera but not cyanogenmod or aosp , aokp rom)
And how to remove SECURE DOWNLOAD : ENABLE from download mode
Please Please help

Secure download enable doesn't means locked bootloader. If your phone model is n9005, it unlocked already.
Sent from my SM-N920C

Theres no unlocking for Samsung, you have Odin for that. Flash a custom recovery with it, boot in there and install the custom ROM. Done. There are dozens of manuals for that in here ^^ (Thats the 3rd time I post this one in a row... GUYS, ONE POST IS ENOUGH!)

i have samsung not 3. when i start a message id flashed and my mobile gets block. can anyone help me to inlock my mobile
fayaz

Which note 3 do you have? What message appears? Which rom is on the phone?

baig50 said:
i have samsung not 3. when i start a message id flashed and my mobile gets block. can anyone help me to inlock my mobile
fayaz
Click to expand...
Click to collapse
Information about to be flashed ROM, current ROM, current mobile, COMPLETE error message like.... by taking a picture of it, would be quite useful. Otherwise noone can help you because sadly the mods disabled glass ball support in here

Hi, I need some help.
I have Note 3 SM-N9005 Lollipop 5.0 stock rom (N9005XXEGBNL8) and rooted with TWRP recovery. I really want Xposed, tried to flash it and got stuck in bootloop, so I tried deodexing my rom, I did it with Joel Droid Lollipop Batch Deodexer, it went well until I tried to install it with TWRP, instant bootloop again, then I tried flashing any custom rom with TWRP and before flashing I always do advanced wipe, but nothing helps, roms doesn't even start installing, my phone just reboots and I'm in a bootloop again, but after flashing rom bootloop is different it doesn't show Samsung logo it just shows Samsung Galaxy Note 3 SM-N9005. So my question is can it be bootloader and if so how can I unlock it? Or is it something entirely different?
Please help...

misskiss said:
Hi, I need some help.
I have Note 3 SM-N9005 Lollipop 5.0 stock rom (N9005XXEGBNL8) and rooted with TWRP recovery. I really want Xposed, tried to flash it and got stuck in bootloop, so I tried deodexing my rom, I did it with Joel Droid Lollipop Batch Deodexer, it went well until I tried to install it with TWRP, instant bootloop again, then I tried flashing any custom rom with TWRP and before flashing I always do advanced wipe, but nothing helps, roms doesn't even start installing, my phone just reboots and I'm in a bootloop again, but after flashing rom bootloop is different it doesn't show Samsung logo it just shows Samsung Galaxy Note 3 SM-N9005. So my question is can it be bootloader and if so how can I unlock it? Or is it something entirely different?
Please help...
Click to expand...
Click to collapse
Maby look here
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118

samsung galaxy note 3 SM-N9005 has been stuck in downloading mode
Actually,i had rooted my device yesterday now, when i am trying to install cutom recovery TWRP on my device it suddenly rebooted and locked at downloadin mode.
Can,anyone suggest me any way to reboot again to normal touchwiz mode

Suggests you flashed the wrong recovery for your model .CHECK
See multiple identical posts .
READ the TWRP thread .

To the phone back to stock, flash the phone with Odin and a stock ROM from Sammobile.com.

HLTEVZW 5.0 Recovery Image

I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?

cyberoptics said:
I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?
Click to expand...
Click to collapse
Cyberoptics,
It's bad form to post the same request in multiple threads.
You'll probably have to odin back the official OF1 5.0 image and start fresh.
Cheers,
B.D.

cyberoptics said:
I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?
Click to expand...
Click to collapse
Image here : https://www.androidfilehost.com/?fid=24052804347806840
recovery here : https://www.androidfilehost.com/?fid=24052804347806842
That is what you need right ?

aaroon200 said:
Image here : https://www.androidfilehost.com/?fid=24052804347806840
recovery here : https://www.androidfilehost.com/?fid=24052804347806842
That is what you need right ?
Click to expand...
Click to collapse
YES! The recovery imaged flashed in Odin and I'm looking at my stock recovery.
Why folks told me to re-image my boot partion I have no idea... the recovery image is a whole different partition than the data... absolutely no reason to lose data.
Thanks again aaroon!

cyberoptics said:
YES! The recovery imaged flashed in Odin and I'm looking at my stock recovery.
Why folks told me to re-image my boot partion I have no idea... the recovery image is a whole different partition than the data... absolutely no reason to lose data.
Thanks again aaroon!
Click to expand...
Click to collapse
Ok no problem, but please don't flash any custom recovery (ClockworkMod/TWRP) on your note 3, it won't work , the only option is to download " flash fire" if you want to flash the JasmineROM v6.1 or something else.

i'm try but not working on 5.0.

aaroon200 said:
Ok no problem, but please don't flash any custom recovery (ClockworkMod/TWRP) on your note 3, it won't work , the only option is to download " flash fire" if you want to flash the JasmineROM v6.1 or something else.
Click to expand...
Click to collapse
I have SM-900V verizon note 3 and I am running the latest TWRP...
And Running JasmineROM v6.1 after using TWRP to flash it.

@CL3WL3SS
You are commenting on a thread from March 2016 - a time when boot loader unlocking was not available to retail Note3 phone owners.
There's probably not much point in reviving old threads and correcting folks over points that they could not possibly have been aware of.
But yeah, *now* you can run TWRP in the recovery of an unlocked bootloader phone. They didn't have that option in March.

bftb0 said:
@CL3WL3SS
You are commenting on a thread from March 2016 - a time when boot loader unlocking was not available to retail Note3 phone owners.
There's probably not much point in reviving old threads and correcting folks over points that they could not possibly have been aware of.
But yeah, *now* you can run TWRP in the recovery of an unlocked bootloader phone. They didn't have that option in March.
Click to expand...
Click to collapse
Sorry I didn't go back that far, I thought. I will definitely look at the dates from now on. Apologies.

how to use flasfire
CL3WL3SS said:
I have SM-900V verizon note 3 and I am running the latest TWRP...
And Running JasmineROM v6.1 after using TWRP to flash it.
Click to expand...
Click to collapse
How did u do that my friend? Is flashfirelike safestrap? Locked bootloader bypass?

TWRP not working with bph6

I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.

kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F

When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....

mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.

I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....

I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user

Xlim said:
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link

same iussue .. some news??
by the way to use root now i put the old firmwere

FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807

When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked

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