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.
Related
Hello,
since some day I'm trying to flash an free knox custom rom and CWM; but I can't and the sm-N9005 refuse all custom flash
I have this in odin :
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> recovery.img
<ID:0/016> NAND Write Start!!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I've tried with odin 3.04, 3.09 and 1.85
this is the picture of information from download mode
{
"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"
}
What can I do please ?
Thank's
octopus82 said:
Hello,
since some day I'm trying to flash an free knox custom rom and CWM; but I can't and the sm-N9005 refuse all custom flash
I have this in odin :
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> recovery.img
<ID:0/016> NAND Write Start!!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
I've tried with odin 3.04, 3.09 and 1.85
this is the picture of information from download mode
What can I do please ?
Thank's
Click to expand...
Click to collapse
You will need to root your phone first but might trip knox depending on what firmware you're on. You will also need to turn off reactivation lock.
hey_joe said:
You will need to root your phone first but might trip knox depending on what firmware you're on. You will also need to turn off reactivation lock.
Click to expand...
Click to collapse
Thank you
I've flashed this stock rom N9005XXUDML3_N9005FTMDML4_FTM, it's an 4.3 version
octopus82 said:
Thank you
I've flashed this stock rom N9005XXUDML3_N9005FTMDML4_FTM, it's an 4.3 version
Click to expand...
Click to collapse
First root your phone using this on odin's AP/PDA slot ( please note that this will make Knox Warranty Void 0x1 ). Then flash CWM.
I dont5 know if this will help you i see that your reactivation lock is ON turn it off under security in settings and try again.
Sent from my SM-N9005 using Tapatalk
I think it's a driver issue. I had the same thing. Install Kies and let it update the drivers and it should work
Sent from my SM-N900T using Tapatalk
Reactivation lock is on just turn off
nabilsweet007 said:
Reactivation lock is on just turn off
Click to expand...
Click to collapse
Thank's
where can I find this option?
octopus82 said:
Thank's
where can I find this option?
Click to expand...
Click to collapse
Goto settings then general then security then find it
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
Uncheck that
I thought it was another option, it's already disabled
You are flashing it via PDA option in Odin right? (just checking as sometimes it's the easiest of things that catch people)
Hi, we bought phone for a staff in our company, but he ended up stealing moneys, and got sacked, We got his phone back, but it was locked.
What I did was factory reset, when u switch off and on holding 3 buttons, it went to enter new details and setup, but it still giving me "This device was reset. To Continue sign in with a google acc that was previously synced on this device." on last step.
I tried to flash it with stock firmvare, but odin fails every time when i press start, may b b cuz usb debug is not on.
Is it any way to unlock it?.
We got no contact with sacked staff
Btw. phone is Samsung Galaxy A8 (asia), but the process should be similar.
Thank You
you should try installing with odin the latest rom version that you can find over here
marius18br said:
you should try installing with odin the latest rom version that you can find over here
Click to expand...
Click to collapse
i did
i connected it to 2 different pcs
installed samsung usb driver and kies, but when i press start it gives FAIL
try checking OEM unlock in settings/ developer options
{
"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"
}
or try this method
the phone is locked i cant go in options
marius18br said:
try checking OEM unlock in settings/ developer options
or try this method
Click to expand...
Click to collapse
heres Odin logs
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A800FXXU1AOK2_A800FOLB1AOJ1_A800FXXU1AOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
marius18br said:
try checking OEM unlock in settings/ developer options
or try this method
Click to expand...
Click to collapse
I confirm yt video worked. Lucky I had that little usb plug at home, so was stright forward.
Big thanks. Sorted
https://youtu.be/DJ8_qbj1DPQ
Actually, its the new security feature in android by google....
So that if your phone is lost, no one can take advantage of it. Your device will require the old password even if a different binary is installed on your device....
All you can do is go to samsung service centre and ask them about this problem...
Hit thanks if you find my post useful...
I am using the latest odin and N910T3 version of tar.md5 but always stalk at following step:
<ID:0/004> Added!!
<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> Odin engine v(ID:3.1101)..
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thank you very much
Hello, i hope to help you.
I had this error when the 1st time I tried to root
{
"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"
}
After I unchecked in security like the next screen. Please note - uncheck the box just below find my mobile link
You may get better assistance in the 910T forums since the 910T3 is the same as the T but with Int. radio. https://forum.xda-developers.com/note-4-tmobile. Good luck
Thank you very much for your input. But in my N910T3 seems there is no such "block reactivation" option under my mobile....
My one is N910F. Maybe there are some differences. Maybe you can try to search about this block reactivation on the web for your model.
My issues were with the recovery but I don't remember if I put 1st the root and after the recovery or the opposite
song52xs said:
Thank you very much for your input. But in my N910T3 seems there is no such "block reactivation" option under my mobile....
Click to expand...
Click to collapse
It's called Reactivation Lock. It's under Security.
Hamra said:
It's called Reactivation Lock. It's under Security.
Click to expand...
Click to collapse
Yes, it's in security as I wrote in my 1st post.
Yeah. Often the translations aren't' exact word translations but translations of the meaning.
alba77 said:
Yes, it's in security as I wrote in my 1st post.
Yeah. Often the translations aren't' exact word translations but translations of the meaning.
Click to expand...
Click to collapse
I have a N910T and use to have a N900A. With both phones I had the same error. Only way I could flash firmware was to remove the .md5 from the file. Example: change Samsung_Firmware.tar.md5 to Samsung_Firmware.tar
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"
}
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!