Hello,
I have OF3 which I'm not sure rooted or not (I still have SU installed so I assume it is). OTA update to 5.1.1 fails even on phone which was reset to factory default (lots of free space).
Same happens with update from update.zip placed on SD card.
I just want to go to complete stock with no rooting etc but fail to do that regardless what I do.
G
artisticcheese said:
Hello,
I have OF3 which I'm not sure rooted or not (I still have SU installed so I assume it is). OTA update to 5.1.1 fails even on phone which was reset to factory default (lots of free space).
Same happens with update from update.zip placed on SD card.
I just want to go to complete stock with no rooting etc but fail to do that regardless what I do.
G
Click to expand...
Click to collapse
If you have not updated your boot loader , which i'm assuming you didn't because you have root, than you can use this link. Follow step 4 under the notes.
artisticcheese said:
Hello,
I have OF3 which I'm not sure rooted or not (I still have SU installed so I assume it is). OTA update to 5.1.1 fails even on phone which was reset to factory default (lots of free space).
Same happens with update from update.zip placed on SD card.
I just want to go to complete stock with no rooting etc but fail to do that regardless what I do.
G
Click to expand...
Click to collapse
Hi .first comfirm that u have root or not
Then check your s5 have OA1 bootloader u can check using phone info apps from play store then follow the muniz post here
http://forum.xda-developers.com/showthread.php?t=3235774
leoishwor10 said:
Hi .first comfirm that u have root or not
Then check your s5 have OA1 bootloader u can check using phone info apps from play store then follow the muniz post here
http://forum.xda-developers.com/showthread.php?t=3235774
Click to expand...
Click to collapse
Thanks,
I"m rooted.
My bootloader is OF3, same as PDA, CSC version. Baseband is OC4.
How do I go to complete stock so I will have never to go through this exercise again next time update rolls out.
artisticcheese said:
Thanks,
I"m rooted.
My bootloader is OF3, same as PDA, CSC version. Baseband is OC4.
How do I go to complete stock so I will have never to go through this exercise again next time update rolls out.
Click to expand...
Click to collapse
I think to get update on AT&T you should have att sim plus regesterd to att...i think its easier than ota ...
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
leoishwor10 said:
I think to get update on AT&T you should have att sim plus regesterd to att...i think its easier than ota ...
Click to expand...
Click to collapse
And another thing how did u get root acces on OF3 bootloader ?
artisticcheese said:
Thanks,
I"m rooted.
My bootloader is OF3, same as PDA, CSC version. Baseband is OC4.
How do I go to complete stock so I will have never to go through this exercise again next time update rolls out.
Click to expand...
Click to collapse
You can't. Once you started flashing over OF3, you lost that ability, without any lollipop firmware to flash back to.
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
leoishwor10 said:
I think to get update on AT&T you should have att sim plus regesterd to att...i think its easier than ota ...
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
And another thing how did u get root acces on OF3 bootloader ?
Click to expand...
Click to collapse
Probably had root on a previous firmware, but OTAs did not break the root.
Thats good
shortydoggg said:
You can't. Once you started flashing over OF3, you lost that ability, without any lollipop firmware to flash back to.
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
Probably had root on a previous firmware, but OTAs did not break the root.
Click to expand...
Click to collapse
Yes. I was rooted before OF3 update and took it over the air and kept root. This is total crap that I'm stuck now in the middle. I can not get OTA or custom ROMs. I'm stuck forever on OF3 now?
artisticcheese said:
Yes. I was rooted before OF3 update and took it over the air and kept root. This is total crap that I'm stuck now in the middle. I can not get OTA or custom ROMs. I'm stuck forever on OF3 now?
Click to expand...
Click to collapse
You can flash the stock (unrooted w/out tethering) OI5 ROM then you will have access to any future OTA's but no root access: http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
muniz_ri said:
You can flash the stock (unrooted w/out tethering) OI5 ROM then you will have access to any future OTA's but no root access: http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
Click to expand...
Click to collapse
This method worked but bootloader failed to flash via ODIN, so I'm not on OI5 with OF3 bootloader. Will that cause any issues down the road?
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
artisticcheese said:
This method worked but bootloader failed to flash via ODIN, so I'm not on OI5 with OF3 bootloader. Will that cause any issues down the road?
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
It should not but if you want to be 100% official OI5 here is the G900A_OI5_Bootloader.tar.md5
Related
Hi,
I have downloaded the latest version of De La Vega for my AT&T Note 3. (Just FYI, I dont know if it makes a difference, but my phone did the recent AT&T update) After unzipping the folder, I ran the N900AUCUBMI9_OneClickBin.exe file and got this message on the application:
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I noticed on my phone that in ODIN Mode that it says "SW REV CHECK FAIL Fused 2 > Binary 1. In order to restart my phone, I have to pull out the battery. I have tried Kingo without any success. I would love to root my phone and also install BobCat Rom but I dont understand why I cant root my phone. Any help is appreciated.
shamlyn said:
Hi,
I have downloaded the latest version of De La Vega for my AT&T Note 3. (Just FYI, I dont know if it makes a difference, but my phone did the recent AT&T update) After unzipping the folder, I ran the N900AUCUBMI9_OneClickBin.exe file and got this message on the application:
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Also, I noticed on my phone that in ODIN Mode that it says "SW REV CHECK FAIL Fused 2 > Binary 1. In order to restart my phone, I have to pull out the battery. I have tried Kingo without any success. I would love to root my phone and also install BobCat Rom but I dont understand why I cant root my phone. Any help is appreciated.
Click to expand...
Click to collapse
You cannot odin mi9 over mj5 you will end up with mi9 rom and mj5 bootloaders which will give you problems. If you have already done this you can flash the pit file only and possibly save yourself however this hasnt worked for everyone. Search the forum there is a thread with the pit file available. Kingo will root your phone but by trying to dowmgrade you have other issues to fix first. The bootloadera do not allow themself to be downgraded
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
Also idk what you are thinking but we do not hqve any custom roms or recovery available for the att note 3 yet due to the locked bootloaders and other security methods used by att
I lost root after update but I just went to recovery mode did a factory reset and supersu was in my system apps. So I went to unknown sources and turned on went back to supersu and it works I have full root. I installed several apps that require root access and they installed fine and everything works perfect
khoury1 said:
I lost root after update but I just went to recovery mode did a factory reset and supersu was in my system apps. So I went to unknown sources and turned on went back to supersu and it works I have full root. I installed several apps that require root access and they installed fine and everything works perfect
Click to expand...
Click to collapse
Is there an easier solution which does not require a factory wipe?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Not that I know of
Kingo work fine for me after the update. What version of Kingo are you using?
I didn't use kingo...I tried but it keep failing
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
DamnYank! said:
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
Click to expand...
Click to collapse
You need to flash the OC4 stock kernel.
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
Muniz, i would be more than happy to. I've been searching though for a 5.0 sm-g900a tar/md5 file that i can load/flash via Odin but I have not been able to find any (other than a 'pre-rooted' one but I want to stay stock/ unrooted if possible).
Do you have any tips on where I could find it?
Thank you!
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
I found your other thread, i tried using your G900A_OC4_Stock_Rooted_Firmware.tar.md5 file via Odin and selecting it for the AP field. When executing, Odin gives me:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_OC4_Stock_Rooted_Firmware.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
And the phone screen shows SECURE CHECK FAIL: system
It looks like I was able to resolve with the info in this post:
http://forum.xda-developers.com/att...phone-trying-to-downgrade-to-4-t3076706/page4
Sorry for not finding that sooner, usually my search-fu is pretty solid but my searches just weren't hitting that (or Muniz's other stock files available from androidfilehost).
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything
Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Edit: Please do not try to flash the .Zip in recovery.. this is just a compressed file. Unzip and you can flash this using ODIN..
I recommend a factory reset before flashing..
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It literally just came out today for the SM-G920T so my guess is this is stock.
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
tflogic said:
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
Click to expand...
Click to collapse
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
magda623 said:
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
Click to expand...
Click to collapse
according to this post, SuperSU Beta seems to be working fine.
tflogic said:
according to this post, SuperSU Beta seems to be working fine.
Click to expand...
Click to collapse
Possibly. However, there is no recovery for our device listed on the recovery page. The fact that recovery breaks the boot.img without root sounds shaky though. I'll try it a few different ways. DL is done. Flashing now.
Zaphodspeaks said:
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Click to expand...
Click to collapse
Think I flash this on my.metro pcs version I flashed the tmobile 5.1.1 update on my metro pcs version it's basically the same phone
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is 100 percent stock.. from Sam Mobile..
Hell it came out early this morning.. No one has had the time yet to make a custom version..
I don't recommend updating from a Custom ROM..
If your 100 percent 5.1.1 Stock you can flash this with ODIN with no problems..
Oh its a Zipped .Tar file.. Don't try to flash the Zip.. Again do NOT try and flash the .Zip.. it will fail and you will be stupid to try..
https://support.t-mobile.com/docs/DOC-21138
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
i have a sm-g920t with an argentinian sim my firmware is G920TUEU3COK1. Can i use my SIM in this firm?
adidas123 said:
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Which functions? I haven't noticed anything missing so far.
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_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!!
Hi,
I tried to flash this using odin but it did not work so I went ahead and used Samsung Smart Switch that automatically downloads 6.0.1 and flashes it. The process, however, failed and now the phone (G920T) is stuck on a blue screen that says, "An error has occurred while updating the system software. Use emergency recovery function in the Smart Switch PC software." (image: http://i.imgur.com/t401aO6.png). Rebooting the phone takes me to the same place. I'm, however, able to get into download mode. I have tried the emergency recovery in download mode as specified by this video: https://www.youtube.com/watch?v=mi7O0OvnS2E, but it still fails, giving me this error: http://i.imgur.com/t401aO6.png. Could someone help me get my phone working?
A few notes:
- My previous firmware was 5.1.1 stock, however, I had flashed a rooted kernel using odin.
- Within download mode, it says the following: swrev b:3 k:2 s:2
Thank you in advance.
EDIT: flashing with odin gives me this error: http://i.imgur.com/oGZiCow.png
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_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!!
Click to expand...
Click to collapse
You using an older version of ODIN
Try Odin3_v3.10.7
Need help, Im looking for the latest modem and bootloader for this. Just the bootloader and modem. Thanks!
Zaphodspeaks said:
You using an older version of ODIN
Try Odin3_v3.10.7
Click to expand...
Click to collapse
Thanks. That worked. I didn't know there was a newer version available.
I don't suppose there will be a recovery-flashable version of this one, will it?
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_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!!
Click to expand...
Click to collapse
Maybe try redownloading the file and unzipping again
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
BigDaddy38 said:
Maybe try redownloading the file and unzipping again
Click to expand...
Click to collapse
What Odin Are you using?
Hello! So Im selling my tab s2 but I need it to be returned to stock to do so. Only part is odin fails on EVERY firmware I put through it and smart switch and Kies try to update but dont recognize while in bootloader mode. Below is the error Im getting. Ive tried pulling the PIT and flashing but no luck. Ive tried changing the port on my pc too but no luck.
Im on a T710 with a 5.1.1 rom installed. Any help would be much apreciated!
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet I get "check fail device 2 binary 1" in red below everything in the top right.
I think that means you're flashing firmware that is below bootloader version. I had it happen. There is a 1B and 2B for bootloader version like on here
https://samsung-firmware.org/model/SM-T810/region/XAR/
I went in stupid mode and got it to flash ignoring that error and it darn near didn't boot at all. Nothing worked for me even 2B versions until I flash a good backup in recovery then odin went fine without that red error.
You're flashing the wrong firmware. You're trying to flash a revision 1 firmware on a device running revision 2 firmware.
You need an XXU2 firmware.
ashyx said:
You're flashing the wrong firmware. You're trying to flash a revision 1 firmware on a device running revision 2 firmware.
You need an XXU2 firmware.
Click to expand...
Click to collapse
Thanks! Im downloading T710XXU2CPH1 6.0.1 from sammobile but its downloading at 300 kb/s :crying: should I do this or flash the 5.1.1 revision 2 for anyone who wants root?
Sugardaddy_duncan said:
Thanks! Im downloading T710XXU2CPH1 6.0.1 from sammobile but its downloading at 300 kb/s :crying: should I do this or flash the 5.1.1 revision 2 for anyone who wants root?
Click to expand...
Click to collapse
Download it from UPDATO
ashyx said:
Download it from UPDATO
Click to expand...
Click to collapse
I cant thank you enough! Please tell me where you live so I can come hug you!
Sugardaddy_duncan said:
I cant thank you enough! Please tell me where you live so I can come hug you!
Click to expand...
Click to collapse
If you were female maybe lol. [emoji12]