Database Users

[Q] Help rooting Note 4 N910F

Hi,
Hope someone can help me. I'm having problems rooting my Note 4 N910F. Initially I tried CF's autoroot but my phone went into a loop with the message "CF Auto Root, Set Warranty bit : recovery" message appearing in the top left. I could not get it out of this, so then tried to install TWRP recovery. This seemed to be successful as the phone rebooted and i was able to use my phone again. See Odin log :
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
However when I tried to get into TWRP it simply boots into the stock android recovery. When i try to do a OTA update now I get the message " The operating system on your device has been modified...."
Thanks
Paul

Ok Think I've worked this out for myself. Think with CF autoroot I needed a special file that was posted by a Tony on here for my version of the N910F. Tried the TWRP again with Odin and did not do an automatic reboot this time. Pulled the battery and booted into recovery and have TWRP. Seems my phone was automatically replacing TWRP with stock recovery.
Hope this helps somebody else out!

Cannot flash stock through ODIN

Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?

savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
try download diffrent firmware
try wipe data/cache (volum up+power button +home button) if you cant access it .try rooting your device and then install recovery then wipe(cache data) and try flashing stocks firmware again
it may also be bad cable try diffrent one
reinstall kies 3(after unistalling it first)
use diffrent odin (3.04 ECT)
and try kikat firmware i believe its just firmware issue (try russian kitkat if your device varient is supported )

savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.

xxSTARBUCKSxx said:
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.
Click to expand...
Click to collapse
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...

savev1 said:
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...
Click to expand...
Click to collapse
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint

xxSTARBUCKSxx said:
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint
Click to expand...
Click to collapse
It worked! It worked! I pressed thanks bro ^.^

savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
Lol. Np bro. Glad it worked. Thats what the community is here for.
Get your phone situated and the way you like it (launchers or what have you) and make a backup in recovery and youll be good to go.

Note 4 sm-n910f
savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
I've been had the same problem having this error
----------------------
UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
-----------------------
and I badly need to flash to stock since I am using custom and having problem with my sim not being detected .
but i just cant seem to get it flashed once more like i did the first try with a stock rom ?
would you suggest me to download several stock rom in sammobile and try all.

I am having the same problem with N910W8 getting emmc write fail

[Please HELP] -----Loop on start + stuck on Samsung logo and now failed to mount/efs

Hi Guys,
I was try to flash with some rom and get error like the title.
First my s8 keep loop on starting. Spend a lot of time to fix that, so happy after go in to the rom.
How ever I have new error with the signal - No service ( circle slash)
Try again with odin on CSC but not work at all.
And now... Fail on mount efs.
I can't even flash rom anymore, even after flash rom it keep loop as the error .
I tried to research on the google, even try with the Z3X... but...
My last chance is asking help from you guys, otherwise as some guy say " samsung service asking for $300 for motherboard ... bla bla "
Help me if you can,
Many thanks,

Do you have nandroid backup or EFS backup ?

zelenko said:
Do you have nandroid backup or EFS backup ?
Click to expand...
Click to collapse
Yeah - that's promblem. I don't have it
Also living in Australia, I though problem from CSC and firmware with VAU region.
But actually not ...
So do I have anychance to do with the EFS?

try to flash latest firmware with july patches ....it should fix the problem

GoJun said:
Hi Guys,
I was try to flash with some rom and get error like the title.
First my s8 keep loop on starting. Spend a lot of time to fix that, so happy after go in to the rom.
How ever I have new error with the signal - No service ( circle slash)
Try again with odin on CSC but not work at all.
And now... Fail on mount efs.
I can't even flash rom anymore, even after flash rom it keep loop as the error .
I tried to research on the google, even try with the Z3X... but...
My last chance is asking help from you guys, otherwise as some guy say " samsung service asking for $300 for motherboard ... bla bla "
Help me if you can,
Many thanks,
Click to expand...
Click to collapse
Have you used adb before will that let u flash just the twrp package or dose it fail. and then in twrp flash youre efs backup the only other way i know is trying different official firmwares like you was.

Thank guys,
Omg one day without phone--- no internet for very long day - LOL
with the july patch now. Let see how it going.
Also I still can run to TWRP but after run the rom , it still loop stop on logo samsung.

khawarjaved said:
try to flash latest firmware with july patches ....it should fix the problem
Click to expand...
Click to collapse
Actualy, It's a Fail...
It says:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5627 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Red line: SW REV. Check Fail ( bootloader) Device 3. Binary: 2

GoJun said:
Thank guys,
Omg one day without phone--- no internet for very long day - LOL
with the july patch now. Let see how it going.
Also I still can run to TWRP but after run the rom , it still loop stop on logo samsung.
Click to expand...
Click to collapse
Hoping that I'm not spamming...
Trying to follow the youtube and got this?
[email protected] C:\platform-tools
> adb devices
List of devices attached
ce11171b8bb2ef2a05 recovery
[email protected] C:\platform-tools
> adb shell
~ # su
/sbin/sh: su: not found
~ #
Where am I wrong?

Sorry for the spam,
I just update the last thing i just do.
Now it went back to the old Adnroid Recovery... and I can't update it to the TWRP anymore...
Also can't use the adb for the flash too..
Is that my last chance is go to the Samsung store ..?

GoJun said:
Actualy, It's a Fail...
It says:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 5627 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Red line: SW REV. Check Fail ( bootloader) Device 3. Binary: 2
Click to expand...
Click to collapse
It fails because you are flashing an older firmware man look for firmware with end CRF7 or something like that... Its giving error because you are flashing a firmware with older bootloader

khawarjaved said:
It fails because you are flashing an older firmware man look for firmware with end CRF7 or something like that... Its giving error because you are flashing a firmware with older bootloader
Click to expand...
Click to collapse
Thanks so much, another chance for me.
Let me try again...
So I tried with BL_G950FXXU2CRF7_CL13760092_QB18535731_REV00_user_low_ship.
And got this:
<ID:0/004> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should I keep try the other BL one?

I tried with SM-G950F_1_20180717083127_fdfqza9z56_fac\BL_G950FXXU3CRGB_CL13971786_QB18969145_REV00_user_low_ship.tar.md5
And got success.

Congratulations man... Its working good?

It can root - But no service - Can boot to the phone - keep looping... GG
If can't do anything to fix, I think i have to go to service by samsung.

Man factory reset it once.clear storage etc.

S7edge stuck in Boot, need help in flashing firmware with Odin

Hi there,
The Samsung S7 Edge of a friend got stuck @boot. I have tried to reset and wipe. But that does not solve the problem.
So now i am trying to put on the latest official firmware from Samfw, Smammobile and/or Frija but Odin 3.14 fails.
I think the phone got stuck in an OTA update.
Please help
Here are more details.
S7 Edge SM-G935FD in the Netherlands (PHN), the G935F version should be working as well, its an exynos chipset with dual sim.
In download mode it says on top left:
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock is ON (i cannot go to devevlopper mode to change that)
Secure Donwload: Enabled
Warranty Void: 0
AP: SWREV: B:8 K:6 S:7
I followed all kind of guides on XDA
Get the right Odin 3.14
Get the right Firmware. Samfw.com_SM-G935F_PHN_G935FXXU8ETI2
Using Default Odin Settings
I have a connection to the phone.
This is the ODIN log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4045 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Dekay99 said:
Hi there,
The Samsung S7 Edge of a friend got stuck @boot. I have tried to reset and wipe. But that does not solve the problem.
So now i am trying to put on the latest official firmware from Samfw, Smammobile and/or Frija but Odin 3.14 fails.
I think the phone got stuck in an OTA update.
Please help
Here are more details.
S7 Edge SM-G935FD in the Netherlands (PHN), the G935F version should be working as well, its an exynos chipset with dual sim.
In download mode it says on top left:
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock is ON (i cannot go to devevlopper mode to change that)
Secure Donwload: Enabled
Warranty Void: 0
AP: SWREV: B:8 K:6 S:7
I followed all kind of guides on XDA
Get the right Odin 3.14
Get the right Firmware. Samfw.com_SM-G935F_PHN_G935FXXU8ETI2
Using Default Odin Settings
I have a connection to the phone.
This is the ODIN log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4045 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OH just found this great article
[GUIDE] AN ESSENTIAL GUIDE FOR G935F/FD
AN ESSENTIAL GUIDE FOR G935F/FD DISCLAIMER ☆THIS WILL BE A HUGE WORD WALL, SO DON'T BOTHER WITH THIS IN ADVANCE IF YOU MIND READING LARGE AMOUNTS OF WORDS ON SCREEN :D ☆THIS ISN'T A ROOT GUIDE EXACTLY BUT WHEN YOU READ THIS TILL THE END...
forum.xda-developers.com
Did i read it well, and understand that FRP Lock is ON.. that prevents me to install anyting?
"But if you haven't rooted/enabled OEM Unlock before, this won't work either and you may had to take your phone to a repair shop "

Help Need. Flash TWRP Custom Rom to Samsung Note 4 (SM-N910F)

Note sure if this is the right thread to post.
Phone Model : Samsung SM-N910F (Samsung Note 4)
I am using Odin v3.13.1.
TWRP -twrp-3.6.2_9-0-trlte.img
Here are my steps.
1. Factory Reset Wipe out all Data
2. Go Back into the phone and enabled USB Debugging.
3. Go into Recovery (Down + Home + Power)
4. Odin Flash with Auto-reboot off (TWRP -twrp-3.6.2_9-0-trlte.img)
5. I got error from odin
--------------
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 13 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------
It keeps failing. with the error log above.
I tried a couple of TWRP version, it fails with same error.
I tried a couple of Odin version, it fails with same error.
Is the bootloader lock ? Please help and shine me a light with this lost soul.
Thank you very much.

mixtmxim said:
Note sure if this is the right thread to post.
Phone Model : Samsung SM-N910F (Samsung Note 4)
I am using Odin v3.13.1.
TWRP -twrp-3.6.2_9-0-trlte.img
Click to expand...
Click to collapse
afaik Odin can only flash tar or tar.md5 files so choose
twrp-3.6.2_9-0-trlte.img.tar.​Personally on that old device I use Odin 3.09 as I somewhere read it suits better.
mixtmxim said:
......
Is the bootloader lock ? Please help and shine me a light with this lost soul.....
Click to expand...
Click to collapse
No. Not on this old device (at least not on my N910F)

kit kat or marshmallow?