Database Users

How To DO "NAND Erase " S5 (SM-G900F) !?

Hi Guys
I Had A problem with My s5 And i Have Full Thread about the problem But No one Have solve it !!
so my friend who is junior-Developer say that i must do Nand Erase !
So Please give me the way to do Nand Erase to My s5 (SM-G900F) !

ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first

*Detection* said:
ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first
Click to expand...
Click to collapse
I Have Done Nand erase With odin !!
i have putted the pit file then the stock firmware then i have checked nand erase all and efs clear and i have forget to do backup efs what should i do !? :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]http://www.up-00.com/[/IMG]

try with odin 3.10.7
http://dl.sammobile.com/Odin3_v3.10.7.zip

daniel3x said:
try with odin 3.10.7
http://dl.sammobile.com/Odin3_v3.10.7.zip
Click to expand...
Click to collapse
i have seen the problem !!
that the internal storage is 0 MB !!

*Detection* said:
ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first
Click to expand...
Click to collapse
___________________

*Detection* said:
___________________
Click to expand...
Click to collapse
is that means that my phone is brick

Flash this PIT file with ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit, add to the PIT section, and add the stock ROM to ODIN at the same time
Stock ROM
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Flash them both together

*Detection* said:
Flash this PIT file with ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit, add to the PIT section, and add the stock ROM to ODIN at the same time
Stock ROM
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Flash them both together
Click to expand...
Click to collapse
It Says :-
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying:
What should i do !?

Boot into download mode, and check which model S5 it says at the top

*Detection* said:
Boot into download mode, and check which model S5 it says at the top
Click to expand...
Click to collapse
SM-G900F

statiicz said:
SM-G900F
Click to expand...
Click to collapse
Try flashing just this with ODIN 3.10.7 (Will trip KNOX)
Code:
https://mega.nz/#!SB4jDQhY!1jGg47kUTu5eCuGaWiPpUanUHIOeTXeJvxPEUJMUGy0

*Detection* said:
Try flashing just this with ODIN 3.10.7 (Will trip KNOX)
Code:
https://mega.nz/#!SB4jDQhY!1jGg47kUTu5eCuGaWiPpUanUHIOeTXeJvxPEUJMUGy0
Click to expand...
Click to collapse
I'm Flashing With ODIN 3.10.7

statiicz said:
I'm Flashing With ODIN 3.10.7
Click to expand...
Click to collapse
Good, well that's a new ROM to try

*Detection* said:
Good, well that's a new ROM to try
Click to expand...
Click to collapse
I'm Flashing the last stock rom (Marshmallow UAE )

statiicz said:
I'm Flashing the last stock rom (Marshmallow UAE )
Click to expand...
Click to collapse
Might not work, different regions are failing with Size! error, which region was it running originally?
The one I linked it modded for BTU G900F
You can try KIES emergency firmware recovery too
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Tutorial
http://forum.xda-developers.com/showthread.php?t=2261153

*Detection* said:
Might not work, different regions are failing with Size! error, which region was it running originally?
The one I linked it modded for BTU G900F
You can try KIES emergency firmware recovery too
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Tutorial
http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
Thanks It Worked :]

Great
Next time, read warnings before jumping in

my SM-G900M feels really slow, i think my memory chip is dying, does it help with this problem? i already have the right rom to flash in my device, whats' next?

still getting odin errors...

hey gang,
This is my current rom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have everything I need to update my Note 4 from a custom 5.1.1 Tekxodus Rom to a stock Marshmellow 6.0.1 but I am still getting an error...
I have TWRP installed as well.
Can someone please point me in the right direction. What am I doing wrong???
Odin is giving me this:
<OSM> N910T3UVU1EPE3_N910T3TMB1EPE3_N910T3UVU1EPE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Make sure your "OEM Unlock" is turn off.

where do I do that?

Your Tekxodus ROM is modified, it maybe in "Developer Option" or in "Security" as " "Reactivation Lock". Do a google if you need help in locating it.

It is checked off. It says allow bootloader to be unlocked. Do I want it unlocked thought?

Uncheck it. Anyway, you're on your own.
You can read post #34 and #36
http://forum.xda-developers.com/note-4/general/guide-how-to-root-note-4-marshmallow-t3359832

I am already rooted and have twrp. The problem is I cannot flash any new rom over it. I think I need to figure out what bootloader I need in order to flash MM.

panxpany said:
I am already rooted and have twrp. The problem is I cannot flash any new rom over it. I think I need to figure out what bootloader I need in order to flash MM.
Click to expand...
Click to collapse
Epe3, the full ROM, includes the bootloader. I usually wipe system, cache, dalvik, and internal when moving between Roms. Just don't boot it like that. Odin flash your ROM and away you go. If you have an issue and it stops after flashing recovery, Odin twrp and restore a backup to get back to where you were.

nine5raptor said:
Epe3, the full ROM, includes the bootloader. I usually wipe system, cache, dalvik, and internal when moving between Roms. Just don't boot it like that. Odin flash your ROM and away you go. If you have an issue and it stops after flashing recovery, Odin twrp and restore a backup to get back to where you were.
Click to expand...
Click to collapse
I tried that too and Odin still fails..... I wonder if I should flash a newer bootloader than then one I have (COG2) - some guides call for that.

Galaxy S8 bootloop

Hi,
So I was trying to move to Magisk from Chainfire SU, So I attemped to go back to the stock bootloader, and downloaded the firmware from here. Magisk said my bootloader was modified when trying to install, so I only installed the BL portion, assuming it was the bootloader. I am now softbricked and cannot boot into recovery or system, only into download mode (which is a shame since I have a backup in recovery). Odin fails when trying to flash anything. Any idea how to fix this? I'm currently trying to download the stock firmware from sammobile but it's both taking hours and I'm not even sure it'll flash.
Thanks for the help in advance!
Edit: Both OEM and FAP lock are and were off when flashing
Edit 2: These are the odin logs:
<ID:0/004> Odin engine v(ID:3.1203).. <ID:0/004> File analysis.. <ID:0/004> SetupConnection.. <ID:0/004> Initialzation.. <ID:0/004> FAIL! (DeviceInfo) <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/004> Removed!! <ID:0/004> Added!! <ID:0/004> Removed!! <ID:0/004> Added!!

Glassounds said:
Hi,
So I was trying to move to Magisk from Chainfire SU, So I attemped to go back to the stock bootloader, and downloaded the firmware from here. Magisk said my bootloader was modified when trying to install, so I only installed the BL portion, assuming it was the bootloader. I am now softbricked and cannot boot into recovery or system, only into download mode (which is a shame since I have a backup in recovery). Odin fails when trying to flash anything. Any idea how to fix this? I'm currently trying to download the stock firmware from sammobile but it's both taking hours and I'm not even sure it'll flash.
Thanks for the help in advance!
Edit: Both OEM and FAP lock are and were off when flashing
Edit 2: These are the odin logs:
<ID:0/004> Odin engine v(ID:3.1203).. <ID:0/004> File analysis.. <ID:0/004> SetupConnection.. <ID:0/004> Initialzation.. <ID:0/004> FAIL! (DeviceInfo) <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/004> Removed!! <ID:0/004> Added!! <ID:0/004> Removed!! <ID:0/004> Added!!
Click to expand...
Click to collapse
I have the exact problem while flashing a custom bootloader on accident instead of the stock firmware's bootloader. I also cannot enter recovery, only download mode. I cannot flash anything in Odin and recieve the same error message. Have you found a solution?

anyone got the solution? Same problem!!!
nevermind found the solution on this board nice!!!! Thanks to the board!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Trying to root my SM-G935V, having problems, odin error

I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot: prntscr.com/ n3d0xn

same issue
EquinoxPDX said:
I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
Screenshot: prntscr.com/ n3d0xn
Click to expand...
Click to collapse
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.

calscoo said:
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.
Click to expand...
Click to collapse
If you figure out the problem could you let me know, because I'm still trying to figure it out.

EquinoxPDX said:
If you figure out the problem could you let me know, because I'm still trying to figure it out.
Click to expand...
Click to collapse
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084

zfk110 said:
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084
Click to expand...
Click to collapse
How do I find what boot loader i'm on?

EquinoxPDX said:
How do I find what boot loader i'm on?
Click to expand...
Click to collapse
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version

zfk110 said:
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version
Click to expand...
Click to collapse
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?

EquinoxPDX said:
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?
Click to expand...
Click to collapse
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"

zfk110 said:
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"
Click to expand...
Click to collapse
Dangit, so I just have to wait? I was looking forward to rooting.

SM-G935A rooting with modified Odin error every flash attempt: RQT_CLOSE !!

Hey all,
I feel like im going insane trying to solve this issue. Everywhere I look now there are guides to root the SM-G935A (ATT S7E). Yet every time i attempt i experience the same issues, with each tutorial, and version of odin, etc...
I have attempted to follow this guide on androidsage - would post link but xda has its rules for new users so see ss below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and have even found more updated files than the guide has specified by the same dev:
Which crazily enough is literally called S7_Oreo_Nougat_Adb_Advanced_Root_V12 - so you'd think a pre-packed folder named for the device and containing all the files needed, would oh you know, work?
Here is my Odin Log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
S7E is able to connect just fine, but is always erroring out for the YEARS i've tried to root this device (sometimes with different error codes) is always erroring right after boot.img
I have never been able to successfully write a boot.img no matter what method i am trying. What does RQT_CLOSE indidcate? most people seem to get this error after hidden.img but mine is right at boot.img
My device in Odin Mode displays the following:
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B10(2,1,1,1,1) K10 S10
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL: [boot]Fused 10 > Binary 8
What is going wrong??? Any help/collaberation greatly appreciated.
Used factory USB cable, other usb, multiple usb ports. Am using Prince Cosmys modified odin, also using modified odin contained in s7 .zip folder downloaded from tut. running it as admin. I've tried all the usual troubleshooting.
Thanks!