Hi all. Long time reader, first time poster.
I was rooted on NG3 and figured I'd downgrade to NCE so I could get the 4.4.4 update. 4.4.4 wouldn't update in that condition and I wanted to ensure I'd be able to get Lollipop (it is coming, AT&T, right?). I backed up everything in Kies, downgraded to NCE and took the OTA to 4.4.4. All was well and then when I went to restore my backup from Kies, it told me I could backup everything except my apps. Being lazy, I figured I'd start all over and do the restore of all my apps while still on 4.4.2, then take the OTA to 4.4.4 again.
I started all over using the method linked below, but after Odin finishes and the S5 reboots, the Samsung splash logo animation almost finishes, pauses for a few seconds and the screen goes black and the notification LED is on blue and becomes non-responsive.
I've tried going into recovery and wiping cache and data and starting the Odin process linked below again with the same results for the past 3-4 hours. I've tried Kies update and initialization but that tells me my phone isn't compatible. Did 4.4.4 do something with the boot-loader and now it's incompatible with 4.4.2?
Any ideas or other options? Thanks in advance!
HTML:
http://forum.xda-developers.com/showthread.php?t=2785363
This was linked from a factory reset thread I believe.
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOW WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
Here are the last few lines from Odin:
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes [at this point it was less than a minute to get to the end]
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!! [It is in Boot Recovery Mode when this happens]
Fixed!
Okay, I think I'm back up thanks to another thread similar to mine posted recently. For anyone that is downgrading to NCE from OA1, use the G900A_Downgrade_to_NCE.tar in the 4.4.4 root thread. Do NOT use the method that contains 4 files (BL, AP, CP, CSC). The 4 stock files worked great from NG3 to NCE, but not so well from OA1, as you can see above.
TheeDesecrator said:
Okay, I think I'm back up thanks to another thread similar to mine posted recently. For anyone that is downgrading to NCE from OA1, use the G900A_Downgrade_to_NCE.tar in the 4.4.4 root thread. Do NOT use the method that contains 4 files (BL, AP, CP, CSC). The 4 stock files worked great from NG3 to NCE, but not so well from OA1, as you can see above.
Click to expand...
Click to collapse
It was my thread wasn't it.
ElectricBiskitz said:
It was my thread wasn't it.
Click to expand...
Click to collapse
Indeed it was. Mine was originally in AT&T General before it got moved. If were in the right place the first time, I wouldn't have needed to start a new thread. Hope both threads help people trying the same thing as us, though.
Related
My rooted T-mobile Note did not like the OTA update it received today (hung at the samsung logo). I reflashed the rooted UVLG3 firmware image, following the instructions at http://androidlegend.com/how-to-root-t-mobile-galaxy-note-sgh-t879/. This worked, and I'm ignoring the OTA update for now.
I don't need root anymore, i didn't really use it anyways, I would like to get back to stock.
How do i get back to the stock/factory image? From http://forum.xda-developers.com/showthread.php?t=1837907, I see items B (T879-STOCK RECOVERY IMAGE) and D (T879-STOCK BOOT IMAGE). In ODIN, do I need to load one or both of these in one the sections (Bootloader, PDA, Phone, CSC, or UMS) and would i then hit the "Start" button?
Thanks for any help.
Just go to Samfirmware.com and download the tar file for the T879. Put it in the PDA section and start.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
How can i rooting the phone if i want to keep stock rom?
Do i have to do same as regular root?
Thank you.
Sent from my SGH-T879 using xda premium
I got it
Sent from my SAMSUNG-SGH-T879 using xda premium
bigape-revamped said:
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
Click to expand...
Click to collapse
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Just remember to flash the flash counter zip if u need to send it over to repairs with Samsung cus if they know ur phone is rooted they won't fix it cus rooting a device voids ur warranty... I flashcounter.zip everything I flash a rom... I usually flash that file last...
Sent from my SGH-T879 using xda premium
thanks all I just learn something from this:good:
Problem solved
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
Got it going. Had to jump on a Windows XP 32 bit PC to get the USB drivers to see the phone. Thanks for the help.
Running great on stock.
I have the update on my status bar but I'm wondering what did the update do for u? Can u post a screen shot of ur about phone info? Thnx
Sent from my SGH-T879 using xda premium
I'm curious, can I flash the stock everything of t879 on my at&t note? I have the i717 switched fully to t-mobile with twrp. I want the ota to upgrade from 4.04
Sent from my SGH-T879 using Tapatalk 2
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
I had to flash TWRP temporarily and wipe the phones emmc and flash the stock ROM again above instruction and worked. I guess before doing anything you should wipe/factory reset your phone first before flashing the stock ROM, this I can't test but just based on logical explanation.
My solution for being stuck on the Samsung logo
I know the last post was done a year earlier, but I thought I'd share this information I learned yesterday. After numerous flashing attempts My Note was stuck on the samsung logo.
I had soft bricked my Note by not clearing out the data on my phone. The previous post here gave me a clue and not being really good at this, I wasn't able to install and get TWRP to play nice with my non-working stock rom image. But I was still able to get the the Samsung Recovery and Download modes.
The working solution (borrowed from a post by andersbot on another thread) was:
1. Go to Recovery mode. Do a "clear cache" and next a "wipe data". Then reboot.
2. Go to Download mode and then connect to a XP PC and start up Odin. Be sure to use the latest Samsung USB drivers.
3. Flash with Odin using ther stock firmware downloaded from sammobile.com. Only tick the boxes for f.reset time and autoreboot (Odin default). Click PDA and load the downloaded file renamed with .tar at the end instead of .tar.md 5.
I dont know if this was the easiest way to clear the data on my SGH-T879, but it worked, and my Note started up correctly with the stock rom.
Currently using my first android device! Samsung galaxy note 3 for att and I decided to root it. I am currently running 4.3 but want to update to 4.4 in hopes of fixing some gps issues i've been having. I tried to use ODIN to load up the stock 4.3 firmware but have been encountering some errors. My phone no longer turns on, when it does it says "firmware upgrade encountered an issue" please select recovery mode in kies and try again. I have downloaded keys 3 and tried to recover it using that but no luck. Am willing to post screens or answer any questions you guys may have!.
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
reply
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Im on 4.3. I've only tried using Odin and kies which have both failed me. what im about to try is "androidrootz.com/2013/10/how-to-unrootunbrick-at-galaxy-note-3.html".. can you link to your suggestion?
I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.
replyy
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Face_Plant said:
I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.
Click to expand...
Click to collapse
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/
I thought only the mi9 firmware was available at kies?
dbartdog said:
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/
Click to expand...
Click to collapse
Just to show people what all im working with..
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Edit:
What happens when i use ODIN3 v3.07 to load the original .tar file (AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.tar.md5)
I connect my phone
Odin detects it fine.
Place it in the PDA, Press start.
Only things checked are Auto reboot and F. Reset time
Wait about 5 mins for it to work.
Fails at the end. With this msg.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to use Kies 3.
Start up kies with phone plugged in, in odin mode.
-the connected device is not supported by kies 3.
-confirm
so i go to tools>Firmware upgrade and initializ.
Enter model SM-N900A
Followed by S/N
Device can be initialaized to its original settings.
<ok>
Prepare for firmware upgrade
<start upgrade>
Downloads file for firmware emergence recovery of note 3 from server.
waits...
Failed to upgrade firmware due to an unexpected error.
In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on
frome901 said:
In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on
Click to expand...
Click to collapse
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?
dbartdog said:
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?
Click to expand...
Click to collapse
Do you really want to be stuck on KitKat 4.4 the offical is a locked up rom for now. try searching for the "NB4 update" thread? theres also a leaked 4.4 one click too
What ^ this guy said.
I have two rooted s4 actives on stock rooted 4.4.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
SebringTech said:
I have two rooted s4 actives on stock rooted 4.2.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.
Yeah 4.4.2 typo fail. I'll check again but last time with my root file Explorer I could only find the .odex file.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Devo7v said:
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.
Click to expand...
Click to collapse
I admit I'm fairly new to this phone. I know how to flash the ML2 firmware via ODIN. Now once that is sent to the phone, I leave it stock, if I go to settings -> More -> About Device -> Click "Software Update" Will that download the NE3 OTA? Both my phones are currently on NC9 firmware, I have no issues but my wife has some odd problems with her phone. So if I have to go to stock unrooted and reroot that's fine I'll do what I have to - I just want to make sure I know what I need to do before I start.
When trying to flash ML2 files ODIN fails every time. Is it possible to go from NC9 to ML2? I've installed the drivers from Samsung, it detects the phone in ODIN but it can't write to it.
Readout from ODIN 3.04:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Now when my phone boots I get "Fimrware upgrade encountered an issue. Please select Recovery Mode in Kies and try again" making it a paperweight...
Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.
SebringTech said:
Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.
Click to expand...
Click to collapse
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly. I thank you very much for pointing out my error!
SebringTech said:
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly....
Click to expand...
Click to collapse
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
I think he said it was the bootloader.
Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
SebringTech said:
I thank you very much for pointing out my error!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
It was the bootloader. When the phone is upgraded to 4.4.2 it's boot loader can't go down from that. So the bootloader from ML2 is incompatible. When I flashed the other three files it worked just fine! Then I applied the patch to get the phone to the latest firmware. It's a .cfg file you rename it to update.zip and put it on the sd card. boot into the stock recovery and install the update. I must admit a few glitches I was having are gone now since upgrading to the latest greatest, and Towelroot made it stupid easy to root.
Ok, good to know, will pass on the information, thank you.
So here's my problem. I bought my Note 4 (SM-N910T3) with 5.1.1 and rooted. As soon as 6.0.1 released, I downloaded and flashed and then rooted a little later. I started having some small issues because of the root so I did some research and found a systemless root method on XDA that was a possible solution. At some point, probably from flashing MM, my Baseband and Bootloader got updated to the newest at the time. That was fine at the time but I starting missing some of the features of 5.1.1 that got removed in the update. So now I'm looking at iB4STiD's Rapture ROM which is build upon stock 5.1.1 but I've hit a pretty major wall. No matter what I try, how many times, I cannot flash anything through Odin, besides 6.0.1 that I haven't tried. iB4STiD provides the Baseband and Bootloader files to flash with his ROM which are for my specific model.
Now, I've read in a couple places that you can't downgrade your bootloader but that sounds weird to me so maybe someone can explain more if that's correct. Now for some info:
Download Mode Text:
Code:
[COLOR="Red"]ODIN MODE (HIGH SPEED)[/COLOR]
PRODUCT NAME: SM-N910T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (2)
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
Now this is what comes up when I attempt to flash:
Odin:
Code:
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download Mode:
Code:
[COLOR="Red"]SECURE CHECK FAIL: aboot
[1]eMMC write fail: ABOOT[/COLOR]
I am at the end here and mentally exhausted so if anybody can give some guidance or advice then that would be awesome. Let me know if you need more info!
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
nano303 said:
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
squiglybob13 said:
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
Click to expand...
Click to collapse
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
pvsgh said:
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
Click to expand...
Click to collapse
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
squiglybob13 said:
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
Click to expand...
Click to collapse
Use PhoneInfo application from Playstor to check your exact bootloader version and post it here. The error from your 1st post shows only when you try to downgrade.
I believe I've got the same problem (N910T, I tried to downgrade to 5.1.1 so that I can install Rapture v8.2), except in Odin it stops at system.img.ext4 then fails. I tried restoring with my backup through TWRP but now it's giving me this:
extractTarFork() process ended with ERROR=255
Basically I'm stuck with Odin and TWRP, I have the 5.1.1 firmware which doesn't work, and I'm currently downloading the 6.0.1 firmware and hopefully I'll be able to get it working again after this 2.2GB file finishes downloading with my 10mb/s internet -.-
I have a sm-n910t3 phone I recently got. It was already flashed with some rom, twistd i think . I got an su binary is occupied error so i thought I would just reload stock and downloaded the \N910T3UVS3EQE2_N910T3TMB3EQE2_N910T3UVS3EQE2_HOME.tar.md5 since that what the phone say it is in the battery compartment. HOWEVER,
if i look at the about device, settings, it says the model is sm-g935t
when i run odin it checks the md5, adds it to the ap block and click start I get
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
Twrp 3.2.1-0 is installed and accessable
all i wanted was to put on stock 6.0.1, twrp, root and magisk but now it seems i have a very basic os with little else.
any help will be greatly appreciated
SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.
cmccarter said:
SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.
Click to expand...
Click to collapse
Have you tried another Firmware ? this one might be corrupted, if you can boot into TWRP why don't you try to reformat the memory? and flash a rom?
Also try to get a firmware with the AP,BL,CSC, CP so you can Deep Clean the phone. try this webpage gsm-firmware(dot)com
Got it working thanks to all for the help. Did a full install of Lineage which kinda put the phone back in a regular mode. I had had Twistd d7 port installed was the main culprit that was making my phone think it was a 935. I then installed a deodexed, debloated (sorry cannot remembed whose it was) 6.0.1 that was rooted also and the phone is now 100% operational. I do want to get rid of super su and go with magisk but not real sure how to get rid of the SU that is already flashed into the phone.
Again my thanks to all who provided input to help me get everything working again.