I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?
herbicide said:
I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?
Click to expand...
Click to collapse
Sorry ... I would get a Windows PC, install Samsung drivers and Odin, then flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Just for repairing the device. Then you can give the windows PC back to your friend.
Thanks for the reply:
It_ler said:
[…] flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Click to expand...
Click to collapse
When I tried that earlier, the device aborted the flash process and displayed the message
SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?
herbicide said:
Thanks for the reply:
When I tried that earlier, the device aborted the flash process and displayed the message
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?
Click to expand...
Click to collapse
IDK about Heimdall, but there are patched versions of Odin available with which you can skip some file version validations.
And with Odin you can explicitly flash a pit file to re-partition the internal storage.
It_ler said:
[…] there are patched versions of Odin available with which you can skip some file version validations.
Click to expand...
Click to collapse
Oh, that sounds useful. Where can I find that patched Odin?
herbicide said:
Oh, that sounds useful. Where can I find that patched Odin?
Click to expand...
Click to collapse
There are several versions available, such as here:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Be careful to flash only files that are compatible with your exact device model.
It_ler said:
Be careful to flash only files that are compatible with your exact device model.
Click to expand...
Click to collapse
One thing I wonder is whether I already attempted to flash the wrong firmware.
If that's what I did, have I actually made the problem worse? Or will flashing the correct firmware work anyway?
SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
this means, the firmware you'll install is to old.
you can't downgrade your device.
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.
MikeT. said:
this means, the firmware you'll install is to old.
you can't downgrade your device.
Click to expand...
Click to collapse
Ah, that makes sense. And if I simply flash a newer firmware now, the earlier failure does not matter. Right?
MikeT. said:
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.
Click to expand...
Click to collapse
I have found a firmware that appears to match, at https://samfw.com/firmware/SM-G960F/XSA/G960FXXUFFUC6
any reason why that is a bad choice?
Related
I was trying to install the latest firmware on my son's M919 via Odin 3.09. I downloaded M919UVUFNB4_M919TMBFNB4_TMB from SAMMOBILE and went to Odin to install. The installation failed. The error said Fail (auth). Now when the phone boots, it goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I downloaded both versions of Kies, but neither one can see the phone in Firmware emergency recovery. I can still get into Download mode, but have been unable to successfully flash any stock firmware. I notice on the screen that the phone says SYSTEM STATUS: Official and WRITE PROTECTION: Enable. Any help will be greatly appreciated. Thank you.
RangerLG said:
I was trying to install the latest firmware on my son's M919 via Odin 3.09. I downloaded M919UVUFNB4_M919TMBFNB4_TMB from SAMMOBILE and went to Odin to install. The installation failed. The error said Fail (auth). Now when the phone boots, it goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I downloaded both versions of Kies, but neither one can see the phone in Firmware emergency recovery. I can still get into Download mode, but have been unable to successfully flash any stock firmware. I notice on the screen that the phone says SYSTEM STATUS: Official and WRITE PROTECTION: Enable. Any help will be greatly appreciated. Thank you.
Click to expand...
Click to collapse
It is possible that the file you downloaded from sammobile did not finish correctly and is corrupt. Try redownloading it and try it again. I dont think it will make any difference but I usually will use odin 3.07.
mremghz said:
It is possible that the file you downloaded from sammobile did not finish correctly and is corrupt. Try redownloading it and try it again. I dont think it will make any difference but I usually will use odin 3.07.
Click to expand...
Click to collapse
I have downloaded files a couple of times. Even downloaded the file from the post in the General section of this forum. Used 3.09 and 3.07, all with the same results. I am using Windows 8 if that makes a difference. May try it on Windows 7 when I get a chance.
RangerLG said:
I have downloaded files a couple of times. Even downloaded the file from the post in the General section of this forum. Used 3.09 and 3.07, all with the same results. I am using Windows 8 if that makes a difference. May try it on Windows 7 when I get a chance.
Click to expand...
Click to collapse
I used to have that a problem with my desktop that has windows 8. Recently I have been using my windows 7 laptop. There are different drivers needed when you are in download mode, plug it in when the phone is in download mode and let it search and find the drivers. You might even want to reinstall the samsung mobile drivers. I would also recommend to use the usb cable that came with the device. Best of luck.
mremghz said:
I used to have that a problem with my desktop that has windows 8. Recently I have been using my windows 7 laptop. There are different drivers needed when you are in download mode, plug it in when the phone is in download mode and let it search and find the drivers. You might even want to reinstall the samsung mobile drivers. I would also recommend to use the usb cable that came with the device. Best of luck.
Click to expand...
Click to collapse
It finds the drivers. I have done this on my Note 8.0 without issue. Not sure why this phone is giving me such grief.
The phone does show up in Odin in the com box correct? Even so I would still just do it on a Windows 7 computer.
Sent from my GT-I9505G using XDA Free mobile app
Uninstall kies and try again. You can also try different USB ports
RangerLG said:
I was trying to install the latest firmware on my son's M919 via Odin 3.09. I downloaded M919UVUFNB4_M919TMBFNB4_TMB from SAMMOBILE and went to Odin to install. The installation failed. The error said Fail (auth). Now when the phone boots, it goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I downloaded both versions of Kies, but neither one can see the phone in Firmware emergency recovery. I can still get into Download mode, but have been unable to successfully flash any stock firmware. I notice on the screen that the phone says SYSTEM STATUS: Official and WRITE PROTECTION: Enable. Any help will be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Had you previously been using the modem/baseband from a firmware that you weren't officially on? i.e. NB4 modem/baseband on either MDL or MK2 bootloader? If so, revert just the modem to your bootloader version and then attempt the Odin flash again.
lordcheeto03 said:
Had you previously been using the modem/baseband from a firmware that you weren't officially on? i.e. NB4 modem/baseband on either MDL or MK2 bootloader? If so, revert just the modem to your bootloader version and then attempt the Odin flash again.
Click to expand...
Click to collapse
Honestly, I am not sure which version he was on. I had assumed the latest or at least 4.3. How would I install just the modem?
mremghz said:
The phone does show up in Odin in the com box correct? Even so I would still just do it on a Windows 7 computer.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Yes, Odin sees that there is a device on the COM port.
Success. Windows 7, 4.4.2, and Odin 1.85. Flashed without issue. Thanks everyone.
Thread closed at OP's request.
Hi, I'm trying to use Heimdall to flash a custom recovery to the tablet, so that I can install CM11. The tablet is unrooted stock with all latest updates.
I'm using the latest Heimdall built from source (cloned from https://github.com/Benjamin-Dobell/Heimdall.git) on Ubuntu 14.04. (I first tried the Heimdall from the Ubuntu packages, with identical results.)
Whether I try to flash --RECOVERY, or simply print-pit, the error is the same:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Anyone know what this means and if it's possible to get it to work?!
(I should mention that Windows is not an option, I don't have it and don't know a single person in real life who does )
Also: is there a temproot method that can be used to install recovery without Heimdall?
Nathan2 said:
Hi, I'm trying to use Heimdall to flash a custom recovery to the tablet, so that I can install CM11. The tablet is unrooted stock with all latest updates.
I'm using the latest Heimdall built from source (cloned from https://github.com/Benjamin-Dobell/Heimdall.git) on Ubuntu 14.04. (I first tried the Heimdall from the Ubuntu packages, with identical results.)
Whether I try to flash --RECOVERY, or simply print-pit, the error is the same:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Anyone know what this means and if it's possible to get it to work?!
(I should mention that Windows is not an option, I don't have it and don't know a single person in real life who does )
Also: is there a temproot method that can be used to install recovery without Heimdall?
Click to expand...
Click to collapse
You need to be rooted to install a custom recovery. After that to flash a recovery, look up flashify and it will auto install cm recovery, twrp or philz (you get to choose), and it will flash it for you.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
A little late, but just in case anyone is having the same problem, it seems that Heimdall is known not to work on this device. There's an open issue in the Heimdall github tracker discussing this:
https://github.com/Benjamin-Dobell/Heimdall/issues/209#issuecomment-59784895
Unfortunately it doesn't seem very active and so I don't know if it will be fixed. The good news is that Windows+Odin worked from inside a VM, as suggested there. So at least you don't have to dual boot the damn thing
bigmike35 said:
You need to be rooted to install a custom recovery. After that to flash a recovery, look up flashify and it will auto install cm recovery, twrp or philz (you get to choose), and it will flash it for you.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
Awesome, thanks. I didn't actually know how to temproot the stock ROM, which is why I didn't go this route first. At least now I can update the recovery from within CM11 without going back to Odin, so that's quite helpful as well.
Nathan2 said:
A little late, but just in case anyone is having the same problem, it seems that Heimdall is known not to work on this device. There's an open issue in the Heimdall github tracker discussing this:
Click to expand...
Click to collapse
Heimdall doesn't work with picassowifi (10.1) either (although cyanogenmod instructions clearly say it works).
Oddly enough, the only ODIN that worked was the latest one (3.09 IIRC), no previous versions worked.
I have the exact same issue. Does anyone know a way to make this work?
hajkan said:
I have the exact same issue. Does anyone know a way to make this work?
Click to expand...
Click to collapse
Seems like the only option is to use odin on windows at the moment. Even manually loading a pit backup won't work for me.
Quick update:
I was able to find odin and hop on a windows box and perform a flash right away. for those struggling to find the correct files for odin you can locate them with the following hashes
e79370eb92859b063ae6bec5b85729d8 SAMSUNG_USB_Driver_for_Mobile_Phones.exe
9f2080faa9e4a4e9d1858e120d0af6d9 Odin3_v3.09.rar
https://support.t-mobile.com/docs/DOC-27648
Android Security Updates
Phone Samsung GALAXY Note3
Model SM-N900T
PDA Version N900TUVSFPL1
CSC Version N900TTMBFPL1
PHONE Version N900TUVSFPL1
Region TMB
Country USA (T-Mobile)
Build Date 12.12.2016
Changelist 6005498
OS Lollipop
OS Version 5.0
If anyone tried using CF-root successfully, leave a confirmation below.
I'm interested too if anyone flashes please report back asap. Doesn't seem like much seeing as the rom is still 5.0 not 5.1 or 6 so more than likely its just 300 mb of "security updates".
Just an update: the new PL1 firmware can be rooted by CF-auto-root.
One more update: the android security patch level is still 2016-09-01, the same as the SPH3 firmware. Don't know why they say this is an "android security update"in the description.
I thought the android security patch level should be 2016-12-01 since it was built on 2016-12-12.
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
bb031577 said:
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
Click to expand...
Click to collapse
Odin flash the cf-root tar file.
googlephone said:
Odin flash the cf-root tar file.
Click to expand...
Click to collapse
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
bb031577 said:
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
Click to expand...
Click to collapse
Should be the same.
I downloaded here:https://download.chainfire.eu/354/CF-Root
Unzip the file and Odin flash the tar.md5 file only, not the zip file.
THANK YOU VERY MUCH IT WORKED PERFECTLY. It must have been the file i downloaded from before.
Baseband not updaing
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Did anyone try flashing roms through TWRP? if so what do you guys use?
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
The baseband should be PL1 but the android security patch level should still be 2016-09-01.
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
frequentc said:
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
Click to expand...
Click to collapse
In order to install the update, I had to get into download mode.
macster2075 said:
In order to install the update, I had to get into download mode.
Click to expand...
Click to collapse
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have the phone turned off and then boot directly into download mode (volume-down + home + power).
frequentc said:
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have to phone turned off and then boot directly into download mode (volume-down + home + power).
Click to expand...
Click to collapse
Yes.. I had to do that in order to re-root using CF-Root and also to flash the recovery.
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
AndroidHacker99 said:
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
Click to expand...
Click to collapse
Still 5.0
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
elyranon said:
Did anyone try flashing roms through TWRP? if so what do you guys use?
Click to expand...
Click to collapse
FlashFIre. Many older posts talk MOP, TWRP, etc. At least with this hardware and firmware, FlashFire is all I use. (Much gratitude to Chainfire.)
hapa8o8 said:
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
Click to expand...
Click to collapse
Code:
# Install Heimdall and print pit
sudo apt install heimdall
heimdall detect
heimdall print-pit --no-reboot > pit.txt
# Extract binaries from firmware package
head -z -n -1 N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar.md5 > N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
tar -xvf N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
Lastly, review the pit file and pick the partitions/files you want to flash. Use the tool you're most comfortable with to do the job.
Many posts refer to the necessity of bootloaders and modems being compatible. So I have not (and would not) flash just the modem. Er, that is unless someone else already did it and reported success.
(PS. Wish *I* could walk out my door and do the Haiku Stairs, a bucket list item.)
SOLVED
Hi!
I'm new here. I managed to flash a twrp recovery that didn't play well with my tablet. I tried to flash the stock ROM with Odin, but the operation failed do to fail (size), which I have read is due to need to repartition. DO any of you know how to get hold of the PIT-file for SM-T525? It is not easy to find on the internet.
Any help would be deeply appreciated!
/paunchygent
SOLVED
Found pit file! Now its just not booting properly.
Hi again. Found a working pit file after much ado. Managed to flash the stock rom with the partition table with a couple of % left on the battery. It is still not booting properly, but at least firmware and recovery is back in working order and the boot loop is gone.
If you download a multiple Firmware from Sammy, the PIT file is included in the CSC image.
So you can extracted from there.
bierma32 said:
If you download a multiparty Firmware from Sammy, the PipIT file is included in the CSC image.
So you can extracted from there.
Click to expand...
Click to collapse
Can you please explain this a bit more in detail? Want to flash Stock-FW via ODIN, but get fail because of size of hidden.img.ext4.
From what I read until now - guess I need to flash it with a PIT. But where to get the PID file ?
What do you mean with multiparty FW. I just know source sammobile, where I can download different versions ....
---------- Post added at 02:00 PM ---------- Previous post was at 01:51 PM ----------
paunchygent said:
Hi again. Found a working pit file after much ado. Managed to flash the stock rom with the partition table with a couple of % left on the battery. It is still not booting properly, but at least firmware and recovery is back in working order and the boot loop is gone.
Click to expand...
Click to collapse
Where did you get it from? I need this too.
@starbright_
Here are the link for the Download tool. Fast download from Sammy Servers.
If you check binary nature, you will download a multiple FW with Modem, CSC , Phone and Bootloader file.
Now unzip the CSC .image and you have got the PIT file for this Rom and your Tab.
@starbright_
I forget to add the link : https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Had this tool already, but the hint "binary" was important.
Nevertheless - it still doesn't work. It tried this Odin methods (see below), both fail. No idea what is the problem !?!?
After booting into download I get this message at screen: Is this normal?
Current binary Custom
Current status: Custom
Knox: 0
Warranty: 1
Qualcom Secure Boot: enable
AP SWREV: S1 T1 R1 A1 P1
Write Protection: Enable
UDC Start
starbright_ said:
this Odin methods (see below)
Click to expand...
Click to collapse
I'd try the second method (4 files) again, but:
- No pit is necessary (it's in the CSC and Odin will apply it automatically).
- Uncheck "repartition" and "f. reset time" before flashing.
bbsc said:
I'd try the second method (4 files) again, but:
- No pit is necessary (it's in the CSC and Odin will apply it automatically).
- Uncheck "repartition" and "f. reset time" before flashing.
Click to expand...
Click to collapse
I can't believe - it passes.
What the f... !! I can't see why this works and others not. Anyhow - thank you so much.
starbright_ said:
I can't believe - it passes.
What the f... !! I can't see why this works and others not. Anyhow - thank you so much.
Click to expand...
Click to collapse
I think you was trying to apply a wrong pit.
That "50M_HIDDEN" in the filename stands for something, I guess
bbsc said:
I think you was trying to apply a wrong pit.
That "50M_HIDDEN" in the filename stands for something, I guess
Click to expand...
Click to collapse
Mh, but this is the Pit I could grab out of the binary download. So it has been a part of the image.
starbright_ said:
this is the Pit I could grab out of the binary download
Click to expand...
Click to collapse
Out of that very "binary download" you was trying to flash?
Strange...
It looks like you was trying to flash "EUR" image and the separate pit-file was from "DBT" (German) image.
Isn't that right?
Some people just post info and never post links . I had firmware for sometime already but i was waiting for other guy to post it. I know we all looking for full Odin files so here they are :
AP_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship_meta.tar
CSC_ATT_N920AATT4EQC6_CL10809541_QB12921033_REV00_use r_low_ship.tar
CP_N920AUCU4EQC6_CP6021124_CL10809541_QB12921033_REV 00_user_low_ship.tar
BL_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship.tar
Download Link of :
Nougat_N920AUCU4EQC6_Odin_Files
All this files are in one zip. Unzip and put this in appropriate windows in ODIN.
Here are Odin 3.12.3
Good Luck.
Of course, this will wipe my device again, even though I do not select the CSC?
If you allow it to flash a new system and user data image then yes.
You basically need a wipe anyways going from MM to Nougat.
Sent from my Galaxy Note5 using XDA Labs
I'm already on Nougat N920AUCU4EQC5. I'm just trying to avoid having to wipe my phone
When i use this. It passes Odin then when the phone tries to reboot and install the update it says deleting then im back to 6.0.1. Any idea why?
norbarb said:
Some people just post info and never post links . I had firmware for sometime already but i was waiting for other guy to post it. I know we all looking for full Odin files so here they are :
AP_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship_meta.tar
CSC_ATT_N920AATT4EQC6_CL10809541_QB12921033_REV00_use r_low_ship.tar
CP_N920AUCU4EQC6_CP6021124_CL10809541_QB12921033_REV 00_user_low_ship.tar
BL_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship.tar
Download Link of :
Nougat_N920AUCU4EQC6_Odin_Files
All this files are in one zip. Unzip and put this in appropriate windows in ODIN.
Good Luck.
Click to expand...
Click to collapse
thank you very much for the link, bro.. i'm already Nougated now. experiencing some blue screen, but when i'm using newest odin.. all fixed.. thx again, man, you are the best.
DuganNash said:
When i use this. It passes Odin then when the phone tries to reboot and install the update it says deleting then im back to 6.0.1. Any idea why?
Click to expand...
Click to collapse
You may use wrong odin, some security installed on your phone, What build are you on?
norbarb said:
You may use wrong odin, some security installed on your phone, What build are you on?
Click to expand...
Click to collapse
It is Odin 3.12 run as admin. it gives me the green pass, then bootloader rolls back to MM
I am on build QB2 as of now.
DuganNash said:
It is Odin 3.12 run as admin. it gives me the green pass, then bootloader rolls back to MM
I am on build QB2 as of now.
Click to expand...
Click to collapse
Can you post your about phone screen ?
norbarb said:
Can you post your about phone screen ?
Click to expand...
Click to collapse
here you go, thank you
DuganNash said:
here you go, thank you
Click to expand...
Click to collapse
Thanks. Ok. Do you have any security like any kind encryption installed on your phone ?
I update first post with newest ODIN. Are you unzipping file you download and put tar files in correct windows? Are you in Download mode when using ODIN ?
norbarb said:
Thanks. Ok. Do you have any security like any kind encryption installed on your phone ?
I update first post with newest ODIN. Are you unzipping file you download and put tar files in correct windows? Are you in Download mode when using ODIN ?
Click to expand...
Click to collapse
I'm not sure about security . It was a stock at note 5 until I tried updated to qb2. All dev factors are turned on, and the rar files are all unzipped and loaded through odin in download mode. It passes then the android update screen (the little robot ) says erasing upon revoot and I boot into mm again
DuganNash said:
I'm not sure about security . It was a stock at note 5 until I tried updated to qb2. All dev factors are turned on, and the rar files are all unzipped and loaded through odin in download mode. It passes then the android update screen (the little robot ) says erasing upon revoot and I boot into mm again
Click to expand...
Click to collapse
OK. Try this , After you unzip from one zip to 4 files , unzip all 4 files to tar.md5 and try ODIN again. Check for any encryption installed on your phone preventing bootloader from overwriting files.
norbarb said:
OK. Try this , After you unzip from one zip to 4 files , unzip all 4 files to tar.md5 and try ODIN again. Check for any encryption installed on your phone preventing bootloader from overwriting files.
Click to expand...
Click to collapse
i tried this after making sure the phone was not encrypted under the security setting. Same result unfortunately. am looking for alternatives
You're the man !! just the files Odin I was looking for. I want to marry with you ... make me a son jajaja
DuganNash said:
i tried this after making sure the phone was not encrypted under the security setting. Same result unfortunately. am looking for alternatives
Click to expand...
Click to collapse
You have to necessarily erase the security lock fingerprints, you also have to remove the password lock, you have not any type of security lock, then you have to enable developer options and type USB debugging(This last one I do not know if it is strictly necessary, but just in case)If you have some security lock on your phone, even if you pray, you will not be able to!
After update installation it is sayin(device didn't have DRK,please install DRK first)
Please help me
Thanks
TaimooR Khawaja said:
After update installation it is sayin(device didn't have DRK,please install DRK first)
Please help me
Thanks
Click to expand...
Click to collapse
What did you flash before this stock firmware?
DRK=device root key
Clicking from Edge of Galaxy
Just a thought, can you Odin flash any other version of the official AT&T firmware? Maybe try another version to see if the phone is truly screwed.
Also, have you tried a factory reset on the phone first. Maybe something (anything) loaded on the phone is preventing the Odin flash. I know this shouldn't matter but it's worth a try.
mattern1974 said:
Just a thought, can you Odin flash any other version of the official AT&T firmware? Maybe try another version to see if the phone is truly screwed.
Also, have you tried a factory reset on the phone first. Maybe something (anything) loaded on the phone is preventing the Odin flash. I know this shouldn't matter but it's worth a try.
Click to expand...
Click to collapse
Same here.. i try to flash it via odin v3.12 it showing pass message..
After reboot my phone still on MM 6.0.1