I have a Samsung T580 10.1 2016 16GB tablet.
It had a custom Marshmallow ROM from XDA on it until Christmas when I upgraded to
[T580]_Stock-DBT-8.1.0-XXU4CRK5-FW_v1.3_by_hanspampel via installing the zip file in TWRP.
Nice ROM and it worked fine.
Then [T580]_Stock-DBT-8.1.0-XXU4CSAI-FW_v1.4_by_hanspampel was released and I decided to install that to update the security patch.
This is where it all went wrong. As soon as I started the install, the screen went off and it rebooted to a blue screen with the android man and a message saying something like "installing update". Then another blue screen with the android man leaning over with "+ +" eyes and the message no command.
it then went into a loop of rebooting, the blue screen with leaning over man and no command and reboot ........
I can boot it into downloader (odin) mode
I couldn't boot it into recovery.
it was impossible to power it off, so the battery ran flat
looking at the log (image attached) there is a message that stands out saying
E: failed to mount /system - (invalid argument)
I thought that this was a simple case of flashing the latest stock ROM so I tried to flash
T580BTU4CSA1_CL15260192_BTU via Odin3 v3.13.1_3. but it fails when trying to write system and displays a pink message on the T580 saying "FRP is enabled, ignore PIT download" .
I've tried many other official ROMs too, but they all fail with the same message or because they are not binary 4 bootloaders.
I've tried the "Unlock SM-T580 Binary 4 FRP" ROM too, but it also fails to flash because of the PIT.
As a last resort I have stripped the system.img out of the "Unlock SM-T580 Binary 4 FRP" AP file and the flash does then complete. and the device boots to the T580XXU4ARJ1 recovery program.
From here I can wipe cache and factory reset. The data partition seems intact! and most importantly, power it off so I can rechharge it.
so after all that, My question is: Is there any kit or box that a repairer might have which can reset the FRP lock so it can be flashed with stock ROM using stock PIT?
There is nowhere near me that updates and flashes mobile phones and I would like to ensure they do have whatever kit is required, before I potentially waste time travelling.
Proving the device is mine is not a problem as I do have the original invoice for it.
I'm sorry this post is so long. I didn't want to miss anything out.
Help!
saznat said:
I have a Samsung T580 10.1 2016 16GB tablet.
It had a custom Marshmallow ROM from XDA on it until Christmas when I upgraded to
[T580]_Stock-DBT-8.1.0-XXU4CRK5-FW_v1.3_by_hanspampel via installing the zip file in TWRP.
Nice ROM and it worked fine.
Then [T580]_Stock-DBT-8.1.0-XXU4CSAI-FW_v1.4_by_hanspampel was released and I decided to install that to update the security patch.
I'm sorry this post is so long. I didn't want to miss anything out.
Help!
Click to expand...
Click to collapse
Sounds like OEM lock was on when you flashed
I know that for the phone you can use Kies or Smartswitch.
Did you try with Smartswitch and then emergency recovery mode?
For Kies or Smartswitch you need a recovery code so that is useless
Can you flash cf autoroot and TWRP with odin ?
If yes you can go back in TWRP and flash the hanspampel rom again
Hi thanks for replying
I did try an old version of smartswitch, where you can enter the device type or serial. Unfo., Smartswitch doesn't recognise the device in download mode.
I have tried flashing TWRP in various ways by odin but again, the FRP lock prevents installing a non stock bootloader/.recovery. with the message
"Custom Binary (Recovery) Blocked by FRP Lock"
If I can find a way to get TWRP on there, I was hoping I could just recover from my last TWRP backup. I hadn't thought of side loading the previous ROM again. That's a good idea. If only I can get past the FRP to install it.
Any other thoughts or ideas would be welcome.
Can anybody tell if this PIT problem can be fixed by software or connecting to specific hardware that a phone repairer might have. Or do I just have a an uneconomical to repair brick?
Samsung Service say they can fix it, but because it's been modded, they'd have to replace the motherboard, which I don't believe there is anything physically wrong with. Apart from the expected eFuse from modding it..
saznat said:
Can anybody tell if this PIT problem can be fixed by software or connecting to specific hardware that a phone repairer might have. Or do I just have a an uneconomical to repair brick?
Samsung Service say they can fix it, but because it's been modded, they'd have to replace the motherboard, which I don't believe there is anything physically wrong with. Apart from the expected eFuse from modding it..
Click to expand...
Click to collapse
The frp issue is likely because you attempted to flash a firmware not intended for your region which is why system states custom. DM-verity also probably fails.
It looks system is stuck at custom status.
If you can find a revision 4 combination firmware install it and then factory reset from within settings.
This should hopefully reset system back to official status.
Then ensure you have the correct firmware for your region and install it.
Hi.
I have got a revision 4 combination rom. I can only flash it if I leave out system.bin, as that causes odin to fail
due to PIT. Once I've installed it I can get into recovery and choose system reset. The log shows that /data was wiped ok.
I'm assuming that I need the combination system partition to be flashed in order for it to find the software
needed to do the reset. is that right? or is just being able to wipe cache and data enough?
on another note. Does the custom ROM have to be the same region as the last custom ROM that was installed? Or does it have to be the same as the original ROM it had when I bought it?
I don't remember what it came with, but I'm pretty sure it wasn't UK (BTU). If I download every 8.1.0 ROM from Sammobile, which will take a long time. Do you reckon that I will hit on the right one and be able to flash the system partition without error?
Thanks for your help. I've been concentrating on FRP, maybe I should have been concentrating on system status
saznat said:
Hi.
I have got a revision 4 combination rom. I can only flash it if I leave out system.bin, as that causes odin to fail
due to PIT. Once I've installed it I can get into recovery and choose system reset. The log shows that /data was wiped ok.
I'm assuming that I need the combination system partition to be flashed in order for it to find the software
needed to do the reset. is that right? or is just being able to wipe cache and data enough?
on another note. Does the custom ROM have to be the same region as the last custom ROM that was installed? Or does it have to be the same as the original ROM it had when I bought it?
I don't remember what it came with, but I'm pretty sure it wasn't UK (BTU). If I download every 8.1.0 ROM from Sammobile, which will take a long time. Do you reckon that I will hit on the right one and be able to flash the system partition without error?
Thanks for your help. I've been concentrating on FRP, maybe I should have been concentrating on system status
Click to expand...
Click to collapse
System won't flash? Tbh this is what is needed.
Which combo firmware did you attempt to install?
Also are you still at custom status?
In recovery mode it says:
MMB29K.FA60_T580XXUARJ1
samsung/gtaxlwifiix/gtaxlwifi
6.0.1/MMB29K/FA60_T580XXUARJ1
I extracted it from the SM-T580 Binary 4 FRP Unlock ROM that
had the only Binary version 4 bootloader within that I have found
Can you recommend another one I could try?
saznat said:
In recovery mode it says:
MMB29K.FA60_T580XXUARJ1
samsung/gtaxlwifiix/gtaxlwifi
6.0.1/MMB29K/FA60_T580XXUARJ1
I extracted it from the SM-T580 Binary 4 FRP Unlock ROM that
had the only Binary version 4 bootloader within that I have found
Can you recommend another one I could try?
Click to expand...
Click to collapse
Dont you mean T580xxu4arj1?
Anyway try installing the combination firmware then just the stock system image.
Go to recovery and factory reset.
Let me know where that gets you.
You could also try to flash the firmware with the PIT.
http://gsm-firmware.com/index.php?a=downloads&b=file&id=17048
yes sorry. T580XXU4ARJ1 .
I'll give it a go and post the result. Thanks
HI TWRP JEDI
Here are the results.
Flash Combination T580XXU4ARJ1
FAILED
Tablet Screen has purple message:
Failed - FRP Enabled - Ignore PIT download
Odin Log
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1016 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------------------------------------------------
Reflash Combination ROM again without system.img
Passed
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 36 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> cm.bin
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
As there's no system Tablet has a fatal exception and shows
"KERNEL PANIC UPLOAD MODE" alongside a small android man
------------------------------------------------------------
Flash just system.img from T580XXU4CSA1_BTU
No message on Tablet
FAILED
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1689 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then tried with a different region - T580XXU4CSA1_DBT
Result was the same as T580XXU4CSA1_BTU
--------------------------------------------------------------
Flash system.img from T580XXU4CSA1_BTU with the pitfile you linked to.
with repartition option unticked
Message on Tablet:
FRP is enabled, ignore PIT download
FAILED
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1689 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------
Thanks again TWRP JEDI, I really appreciate your help here. Unfortunately, I keep thinking of more questions.
If I include system.img.lz4 in the file I flash, I get no message appear on the tablet screen during flashing. But, if
I rename it as system.img I got the following message on the tablet:
"FRP is enabled, not allow download non-FRP SYSTEM binary"
Am I right in assuming that it doesn't matter whether I flash the system.img or system.img.lz4 file type, the problem is actually the same one - FRP preventing flashing of the system binary. Am I right that The only difference is that it only tells tells me about it on the tablet when I flash the system file without the .lz4 extension?
Should I be flashing system.img or system.img.lz4? Should it make any difference?
Are there regional differences in system.img between different firmwares? I thought the regional stuff was in the CSC tar file. Am I right in assuming that system.img is the same in all regional firmwares?
Sorry. So many questions! I'm just confusing myself. It'd be a great help if you can give me any answers.
saznat said:
HI TWRP JEDI
Here are the results.
Flash Combination T580XXU4ARJ1
FAILED
Tablet Screen has purple message:
Failed - FRP Enabled - Ignore PIT download
Odin Log
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1016 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------------------------------------------------
Reflash Combination ROM again without system.img
Passed
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 36 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> cm.bin
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
As there's no system Tablet has a fatal exception and shows
"KERNEL PANIC UPLOAD MODE" alongside a small android man
------------------------------------------------------------
Flash just system.img from T580XXU4CSA1_BTU
No message on Tablet
FAILED
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1689 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then tried with a different region - T580XXU4CSA1_DBT
Result was the same as T580XXU4CSA1_BTU
--------------------------------------------------------------
Flash system.img from T580XXU4CSA1_BTU with the pitfile you linked to.
with repartition option unticked
Message on Tablet:
FRP is enabled, ignore PIT download
FAILED
Odin Log
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1689 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------------------------------------------------------
Thanks again TWRP JEDI, I really appreciate your help here. Unfortunately, I keep thinking of more questions.
If I include system.img.lz4 in the file I flash, I get no message appear on the tablet screen during flashing. But, if
I rename it as system.img I got the following message on the tablet:
"FRP is enabled, not allow download non-FRP SYSTEM binary"
Am I right in assuming that it doesn't matter whether I flash the system.img or system.img.lz4 file type, the problem is actually the same one - FRP preventing flashing of the system binary. Am I right that The only difference is that it only tells tells me about it on the tablet when I flash the system file without the .lz4 extension?
Should I be flashing system.img or system.img.lz4? Should it make any difference?
Are there regional differences in system.img between different firmwares? I thought the regional stuff was in the CSC tar file. Am I right in assuming that system.img is the same in all regional firmwares?
Sorry. So many questions! I'm just confusing myself. It'd be a great help if you can give me any answers.
Click to expand...
Click to collapse
As long as the system image isn't modified it shouldn't matter, but you could try renaming to system.img.lz4.
Also when you flash the pit you need repartition ticked.
I think that's the root of my problem. I can't flash the PIT because FRP Lock won't let me. Without the system partition, I can't flash system.bin.
I'm beginning to wonder if this is beyond the capabilities of an ordinary home PC, unless there's some other software that can get round the FRP lock.
Is there a box or bit of kit that a phone shop or repairer might have that can reset the FRP lock so that I can write the PIT and then flash stock rom? Or do I now have a doorstop?
Proving I am the owner is not a problem.
saznat said:
I think that's the root of my problem. I can't flash the PIT because FRP Lock won't let me. Without the system partition, I can't flash system.bin.
I'm beginning to wonder if this is beyond the capabilities of an ordinary home PC, unless there's some other software that can get round the FRP lock.
Is there a box or bit of kit that a phone shop or repairer might have that can reset the FRP lock so that I can write the PIT and then flash stock rom? Or do I now have a doorstop?
Proving I am the owner is not a problem.
Click to expand...
Click to collapse
I think the actual crux of the problem is the region this tablet is from. The system partition is denoted as revision 2, so it cannot be downgraded. Probably the reason why the combo firmware doesn't work either.
What's needed is the correct firmware.
I suggest you try the firmware below:
https://samfrew.com/download/Galaxy__Tab__A⑥__/9q2e/KOO/T580XXU4CRJ9/T580KOO4CRK1/
Thanks for staing with me on this. I'll give this a try.
Yes, I tried that ROM and nearly half of the other regions that are on there and they
all fail as soon as it tries to flash system.img.
I've also managed to extract the PIT file from the tablet and it doesn't match the ones in the ROMS I've downlooaded. It seems to have two extra entries, STEADY and CARRIER, also, many of the addresses and block sizes are wrong. I guess this might be the system problem, because the system partition is not the right size.
I'm guessing that if I could flash the correct PIT, then I stand a chance of flashing a combination ROM or Stock ROM. Unfortunately, I can't flash any PIT file or CSC because the FRP Lock
prevents it. And I can't flash any stock AP or even just system.img until the partitions are fixed.
Are there any options left without sending it to Samsung who insist that regardless of anything, they won't touch it without replacing the motherboard, as that's policy with any modded device. The cost wouldn't be much less than just getting a new one!
Is there something a high street repairer can do, which I can't?
saznat said:
Yes, I tried that ROM and nearly half of the other regions that are on there and they
all fail as soon as it tries to flash system.img.
I've also managed to extract the PIT file from the tablet and it doesn't match the ones in the ROMS I've downlooaded. It seems to have two extra entries, STEADY and CARRIER, also, many of the addresses and block sizes are wrong. I guess this might be the system problem, because the system partition is not the right size.
I'm guessing that if I could flash the correct PIT, then I stand a chance of flashing a combination ROM or Stock ROM. Unfortunately, I can't flash any PIT file or CSC because the FRP Lock
prevents it. And I can't flash any stock AP or even just system.img until the partitions are fixed.
Are there any options left without sending it to Samsung who insist that regardless of anything, they won't touch it without replacing the motherboard, as that's policy with any modded device. The cost wouldn't be much less than just getting a new one!
Is there something a high street repairer can do, which I can't?
Click to expand...
Click to collapse
Like I mentioned earlier in this thread I suspected that this device may be from a carrier and the system partition may be a different size.
Ok so let's go back to basics and see if we can work out what's needed.
Can you provide me with that PIT and the serial number of the device and any other info on the device itself?
Where did you purchase this device and in which country?
Also how did you manage to extract the PIT?
Another thing that confuses is how this initially happened.
At some point OEM_UNLOCK must have been enabled for TWRP to have been installed in the first place.
Somehow flashing that modified rom flipped the switch and re-enabled FRP.
I think all we need do is find the correct firmware. If you can provide the details above there's half a chance to fix this.
No point sending to Samsung. As for a third party repair shop? I'm not sure what they could do without having the correct firmware.
It seems it all comes down to finding that carrier based firmware.
The device details are:
MODEL: SM-T580 10.1 2016 with 16GB (WIFI Only)
PRODUCT: AJNB3R
UN: CAJ036DF7ECBBA3
VENDOR: SAMSUNG
VER: T580XXU4CSA1
SERIAL: R52HA2BZ9TA
PURCHASED IN UK THROUGH VERY
The pit file attached was extracted by chimera. I have no idea how reliable chimera is, or whether the PIT they saved is actully what is on the device. However, I did try changing all the PIT entries in it to match the ones you sent me the other day. I was hoping that if I did this and the signature part of the file was untouched, I might be able to flash it.
I was wrong. I couldn't. I got the same error on line 1892 mentioned below.
The first thing I did when I bought the tablet in 2016 was to install TWRP custom recovery and root it. So from day one, OEM was unlocked.
I have never flipped that switch off and I don't know what else did.
---------------------------------------------------------------------------------
This problem started when I updated my custom ROM from TWRP and the
device crashed within seconds of starting the install. That update was just upgrading the ROM that was already on the device. I do still have the TWRP image I saved before installing the update.
Looking into that backup I extracted some files which are shown below. HoweverI don't know if any of the information extracted from the previous TWRP backup is of any use, as any of that information could have been overwritten or wiped by the update
I was upgrading the ROM from
[T580]_Stock-DBT-8.1.0-XXU4CRK5-FW_v1.3_by_hanspampel.zip
to
[T580]_Stock-DBT-8.1.0-XXU4CSB1-FW_v1.4_by_hanspampel.zip
/system/CSCVersion.txt contained: T580OXA4CRK5
/System/SW_Configuration.xml
--------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<SW-Configuration>
<MobileData>
<PublicName>SM-T580</PublicName>
</MobileData>
<CustomerDataSet>
<CSCName>T580OXA</CSCName>
<CSCVersion>4CRK5</CSCVersion>
<NbCustomer>5</NbCustomer>
<CustomerData src="/Customer/DBT/customer.xml" />
<CustomerData src="/Customer/ITV/customer.xml" />
<CustomerData src="/Customer/XEO/customer.xml" />
<CustomerData src="/Customer/XEF/customer.xml" />
<CustomerData src="/Customer/BTU/customer.xml" />
</CustomerDataSet>
</SW-Configuration>
build.prop
-------------
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=M1AJQ
ro.build.display.id=M1AJQ.T580XXU4CRK5 by hanspampel v1.3
ro.build.version.incremental=T580XXU4CRK5
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.version.security_index=1
ro.build.date=Fri Nov 16 18:11:46 KST 2018
ro.build.date.utc=1542359506
ro.build.type=user
ro.build.user=dpi
ro.build.host=21HH1D07
ro.build.tags=release-keys
ro.build.flavor=gtaxlwifixx-user
ro.product.model=SM-T580
ro.product.brand=samsung
# ro.build.product is obsolete; use ro.product.device
ro.build.product=gtaxlwifi
ro.product.name=gtaxlwifixx
ro.product.device=gtaxlwifi
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale=en-GB
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=gtaxlwifixx-user 8.1.0 M1AJQ T580XXU4CRK5 release-keys
ro.build.fingerprint=samsung/gtaxlwifixx/gtaxlwifi:8.1.0/M1AJQ/T580XXU4CRK5:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=T580XXU4CRK5
ro.build.official.release=true
ro.config.rm_preload_enabled=0
ro.build.changelist=14598547
ro.product_ship=true
ro.chipname=exynos7870
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=universal7870
ro.board.platform=exynos5
ro.vendor.product.manufacturer=samsung
ro.vendor.product.model=SM-T580
ro.vendor.product.brand=samsung
ro.vendor.product.name=gtaxlwifixx
ro.vendor.product.device=gtaxlwifi
# end build properties
#
# from device/samsung/gtaxlwifi/system.prop
#
#
# system.prop for universal7870
#
ro.arch=exynos7870
ro.kernel.qemu=0
ro.kernel.qemu.gles=1
persist.demo.hdmirotationlock=false
# read DS/SS property
import /efs/factory.prop
#system prop for Bluetooth SOC type
#BT
qcom.bluetooth.soc=rome
sys.config.phone_start_early=true
# GPU WFD support
ro.exynos.vendor.wfdsupport=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product.first_api_level=23
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.arch=exynos7870
persist.demo.hdmirotationlock=false
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d
/dev/umts_ipc0
exynos.ril.modempath=/dev/block/mmcblk0p5
exynos.ril.nvpath=/efs/
ro.debug_level=0x4948
dev.usbsetting.embedded=On
ro.hdcp2.rx=tz
ro.opengles.version=196610
debug.hwc.otf=1
debug.hwc.winupdate=1
debug.hwc.nodirtyregion=1
debug.sf.disable_backpressure=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
persist.sys.strictmode.disable=true
keyguard.no_require_sim=true
ro.carrier=unknown
persist.radio.atfwd.start=false
ro.security.icd.flagmode=multi
security.ASKS.policy_version=000000
ro.build.scafe.version=2018A
ro.sf.lcd_density=240
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_Horizon.ogg
ro.config.notification_sound=Skyline.ogg
ro.config.alarm_alert=Morning_Flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.ringtone_2=Basic_Bell.ogg
ro.config.notification_sound_2=S_Charming_Bell.ogg
security.mdpp.mass=skmm
ro.security.vpnpp.ver=2.1
ro.security.vpnpp.release=1.1
ro.frp.pst=
ro.wsmd.enable=true
ro.security.vaultkeeper.feature=0
ro.com.google.clientidbase=android-samsung
ro.control_privapp_permissions=log
setupwizard.feature.deferred_setup_suggestion=false
setupwizard.feature.deferred_setup_notification=false
ro.setupwizard.wifi_on_exit=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=8.1_201809
ro.build.version.sem=2701
ro.build.version.sep=90500
ro.treble.enabled=false
ro.build.selinux=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
ro.config.knox=v30
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.timaversion_info=Knox3.2_..
ro.config.iccc_version=3.0
ro.config.dmverity=A
ro.config.kap=true
ro.kernel.qemu=0
ro.ss.bid=20649615
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xdb1b08cd8281e0409e275a4d3bf7582eed2a04f5000000000000000000000000
customer.xml (general info only)
----------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<CustomerData>
<GeneralInfo>
<CSCEdition>ED0003</CSCEdition>
<Country>Germany</Country>
<CountryISO>DE</CountryISO>
<Region>EUR</Region>
<SalesCode>DBT</SalesCode>
</GeneralInfo>
Is it right to assume that my current pit file (extracted through chimera) came from that failed update? Or could it have come from one of the other ROMS I have tried to flash since? I can't remember any flash through odin that didn't say "FRP is enabled, ignore PIT download".
and if I tick the repartition option ,I always get an odin log like this
while Flashing. This extract was while flashing T580XXU4CSA1:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3496 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
I can't find out how to get round this or understand what this Line 1892
issue is.
I'm not sure whether I managed to flash an incorrect custom ROM, although I was very careful to ensure they were all named T580. I don't get why there is a CARRIER pit entry in a WIFI only device. I'm assuming CARRIER relates to a mobile network.
Is it worth my while downloading all the latest binary 4 firmwares for all regions and flashing them one by one, in the hope that one will do the job?
And thanks again. I keep getting flustered and wondering what is actually relevent in all this. You're helping to keep me focused and not wandering off on pointless tangents.
If there's anything else in the TWRP image that may help you, I'll extract it and post it.
saznat said:
The device details are:
MODEL: SM-T580 10.1 2016 with 16GB (WIFI Only)
PRODUCT: AJNB3R
UN: CAJ036DF7ECBBA3
VENDOR: SAMSUNG
VER: T580XXU4CSA1
SERIAL: R52HA2BZ9TA
PURCHASED IN UK THROUGH VERY
The pit file attached was extracted by chimera. I have no idea how reliable chimera is, or whether the PIT they saved is actully what is on the device. However, I did try changing all the PIT entries in it to match the ones you sent me the other day. I was hoping that if I did this and the signature part of the file was untouched, I might be able to flash it.
I was wrong. I couldn't. I got the same error on line 1892 mentioned below.
The first thing I did when I bought the tablet in 2016 was to install TWRP custom recovery and root it. So from day one, OEM was unlocked.
I have never flipped that switch off and I don't know what else did.
---------------------------------------------------------------------------------
This problem started when I updated my custom ROM from TWRP and the
device crashed within seconds of starting the install. That update was just upgrading the ROM that was already on the device. I do still have the TWRP image I saved before installing the update.
Looking into that backup I extracted some files which are shown below. HoweverI don't know if any of the information extracted from the previous TWRP backup is of any use, as any of that information could have been overwritten or wiped by the update
I was upgrading the ROM from
[T580]_Stock-DBT-8.1.0-XXU4CRK5-FW_v1.3_by_hanspampel.zip
to
[T580]_Stock-DBT-8.1.0-XXU4CSB1-FW_v1.4_by_hanspampel.zip
/system/CSCVersion.txt contained: T580OXA4CRK5
/System/SW_Configuration.xml
--------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<SW-Configuration>
<MobileData>
<PublicName>SM-T580</PublicName>
</MobileData>
<CustomerDataSet>
<CSCName>T580OXA</CSCName>
<CSCVersion>4CRK5</CSCVersion>
<NbCustomer>5</NbCustomer>
<CustomerData src="/Customer/DBT/customer.xml" />
<CustomerData src="/Customer/ITV/customer.xml" />
<CustomerData src="/Customer/XEO/customer.xml" />
<CustomerData src="/Customer/XEF/customer.xml" />
<CustomerData src="/Customer/BTU/customer.xml" />
</CustomerDataSet>
</SW-Configuration>
build.prop
-------------
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=M1AJQ
ro.build.display.id=M1AJQ.T580XXU4CRK5 by hanspampel v1.3
ro.build.version.incremental=T580XXU4CRK5
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.version.security_index=1
ro.build.date=Fri Nov 16 18:11:46 KST 2018
ro.build.date.utc=1542359506
ro.build.type=user
ro.build.user=dpi
ro.build.host=21HH1D07
ro.build.tags=release-keys
ro.build.flavor=gtaxlwifixx-user
ro.product.model=SM-T580
ro.product.brand=samsung
# ro.build.product is obsolete; use ro.product.device
ro.build.product=gtaxlwifi
ro.product.name=gtaxlwifixx
ro.product.device=gtaxlwifi
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale=en-GB
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=gtaxlwifixx-user 8.1.0 M1AJQ T580XXU4CRK5 release-keys
ro.build.fingerprint=samsung/gtaxlwifixx/gtaxlwifi:8.1.0/M1AJQ/T580XXU4CRK5:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=T580XXU4CRK5
ro.build.official.release=true
ro.config.rm_preload_enabled=0
ro.build.changelist=14598547
ro.product_ship=true
ro.chipname=exynos7870
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=universal7870
ro.board.platform=exynos5
ro.vendor.product.manufacturer=samsung
ro.vendor.product.model=SM-T580
ro.vendor.product.brand=samsung
ro.vendor.product.name=gtaxlwifixx
ro.vendor.product.device=gtaxlwifi
# end build properties
#
# from device/samsung/gtaxlwifi/system.prop
#
#
# system.prop for universal7870
#
ro.arch=exynos7870
ro.kernel.qemu=0
ro.kernel.qemu.gles=1
persist.demo.hdmirotationlock=false
# read DS/SS property
import /efs/factory.prop
#system prop for Bluetooth SOC type
#BT
qcom.bluetooth.soc=rome
sys.config.phone_start_early=true
# GPU WFD support
ro.exynos.vendor.wfdsupport=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product.first_api_level=23
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.arch=exynos7870
persist.demo.hdmirotationlock=false
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d
/dev/umts_ipc0
exynos.ril.modempath=/dev/block/mmcblk0p5
exynos.ril.nvpath=/efs/
ro.debug_level=0x4948
dev.usbsetting.embedded=On
ro.hdcp2.rx=tz
ro.opengles.version=196610
debug.hwc.otf=1
debug.hwc.winupdate=1
debug.hwc.nodirtyregion=1
debug.sf.disable_backpressure=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
persist.sys.strictmode.disable=true
keyguard.no_require_sim=true
ro.carrier=unknown
persist.radio.atfwd.start=false
ro.security.icd.flagmode=multi
security.ASKS.policy_version=000000
ro.build.scafe.version=2018A
ro.sf.lcd_density=240
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_Horizon.ogg
ro.config.notification_sound=Skyline.ogg
ro.config.alarm_alert=Morning_Flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.ringtone_2=Basic_Bell.ogg
ro.config.notification_sound_2=S_Charming_Bell.ogg
security.mdpp.mass=skmm
ro.security.vpnpp.ver=2.1
ro.security.vpnpp.release=1.1
ro.frp.pst=
ro.wsmd.enable=true
ro.security.vaultkeeper.feature=0
ro.com.google.clientidbase=android-samsung
ro.control_privapp_permissions=log
setupwizard.feature.deferred_setup_suggestion=false
setupwizard.feature.deferred_setup_notification=false
ro.setupwizard.wifi_on_exit=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=8.1_201809
ro.build.version.sem=2701
ro.build.version.sep=90500
ro.treble.enabled=false
ro.build.selinux=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
ro.config.knox=v30
ro.config.tima=0
ro.config.timaversion=3.0
ro.config.timaversion_info=Knox3.2_..
ro.config.iccc_version=3.0
ro.config.dmverity=A
ro.config.kap=true
ro.kernel.qemu=0
ro.ss.bid=20649615
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xdb1b08cd8281e0409e275a4d3bf7582eed2a04f5000000000000000000000000
customer.xml (general info only)
----------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<CustomerData>
<GeneralInfo>
<CSCEdition>ED0003</CSCEdition>
<Country>Germany</Country>
<CountryISO>DE</CountryISO>
<Region>EUR</Region>
<SalesCode>DBT</SalesCode>
</GeneralInfo>
Is it right to assume that my current pit file (extracted through chimera) came from that failed update? Or could it have come from one of the other ROMS I have tried to flash since? I can't remember any flash through odin that didn't say "FRP is enabled, ignore PIT download".
and if I tick the repartition option ,I always get an odin log like this
while Flashing. This extract was while flashing T580XXU4CSA1:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3496 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
I can't find out how to get round this or understand what this Line 1892
issue is.
I'm not sure whether I managed to flash an incorrect custom ROM, although I was very careful to ensure they were all named T580. I don't get why there is a CARRIER pit entry in a WIFI only device. I'm assuming CARRIER relates to a mobile network.
Is it worth my while downloading all the latest binary 4 firmwares for all regions and flashing them one by one, in the hope that one will do the job?
And thanks again. I keep getting flustered and wondering what is actually relevent in all this. You're helping to keep me focused and not wandering off on pointless tangents.
If there's anything else in the TWRP image that may help you, I'll extract it and post it.
Click to expand...
Click to collapse
Did you ever make a backup of the stock rom with TWRP before installing anything custom?
The PIT error about line 1892 will be a line of code in Odin itself that cannot execute because the PIT is wrong
Have you tried any other versions of ODIN? I would work my way down in the versions and see if any can overcome the issue.
Also all that information above seems to come from the custom roms you flashed not the original.
Related
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<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> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
AHLASSICH said:
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<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> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
Click to expand...
Click to collapse
Hey there, I'm trying to update my I337M's modem as well (I have a post in this forum) so I'm in the same boat as you. From the looks of it, it seems like you're not using the correct modem firmware. If you'd want to update I believe it's something like UMUEMK6 for our phones, I've tried looking around and I can't find it anywhere. Hopefully that offers some direction but I'm waiting to see as well since I'm having the same problem with Google ROMs as well (The data signal never works).
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
For some reason, yours is the only version of the mk6 modem file that worked for my i337m after I was on 4.3 GE and went to old MDJ modem to try sim unlock. Which didn't work, sigh... Thanks!
SimonPalmieri said:
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
Click to expand...
Click to collapse
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
jk2rd said:
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
Click to expand...
Click to collapse
Bootloader and modem are not tied together..... MK6 is the latest modem and works with 4.4.2 roms (for I337M), once the actual 4.4.2 update drops for i337m we will be able to update to that modem.
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
MK6
jk2rd said:
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
Click to expand...
Click to collapse
First you need to decide if you want to sim unlock the phone, still possible on mvluamg1, not possible on MK6. I would make sure you have a copy of modem.bin for mvluamg1 first, just incase. Then flash the MK6, I run MK6 on 4.4.2 GErom since we don't have a kitkat modem for i337m yet... once there is I will be updating.....
PS if you can find files that have md5 checksum, that is always good because then you can check the file to make sure it is complete. I had that issue flashing the MK6 modem, first file I downloaded failed in Odin, plus it had no md5 for me to check. Second one I donwloaded had the md5, which I checked and it flashed perfectly....
Stock G955USQU2CRC5 Odin Files
Model: SM-G955U
Model Name: Galaxy S8+
Country: (USA)
Version: Android 8.0 Oreo
Security Patch Level: March 1st, 2018
PDA: G955USQU2CRC5
CSC: G955UOYN2CRC5
Download here: G955USQU2CRC5
DOWNLOAD for ODIN:
ODIN v3.13.1
Issues
bboii86 said:
Stock G955USQU2CRC5 Odin Files
Model: SM-G955U
Model Name: Galaxy S8+
Country: (USA)
Version: Android 8.0 Oreo
Security Patch Level: March 1st, 2018
PDA: G955USQU2CRC5
CSC: G955UOYN2CRC5
Download here: G955USQU2CRC5
DOWNLOAD for ODIN:
ODIN v3.13.1
Click to expand...
Click to collapse
I need help. When I tried to flash the phone with Odin, this error came up:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> apdp.mbn
<ID:0/006> msadp.mbn
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 4625 M
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Have you been able to update the android version? What version were you coming from?
Worked flawlessly, thank you!
bboii86 said:
Stock G955USQU2CRC5 Odin Files
Model: SM-G955U
Model Name: Galaxy S8+
Country: (USA)
Version: Android 8.0 Oreo
Security Patch Level: March 1st, 2018
PDA: G955USQU2CRC5
CSC: G955UOYN2CRC5
Download here: G955USQU2CRC5
DOWNLOAD for ODIN:
ODIN v3.13.1
Click to expand...
Click to collapse
Tried to upgrade but got the an error:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> omr.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4732 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
liquid286 said:
Tried to upgrade but got the an error:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> omr.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4732 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Could be the odin
Try the original odin
ODIN v3.13.1
bboii86 said:
Could be the odin
Try the original odin
ODIN v3.13.1
Click to expand...
Click to collapse
Same issue, just to be sure, CSC_OYN goes to CSC and HOME_CSC_OYN goes to User data right?
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> omr.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4733 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
liquid286 said:
Same issue, just to be sure, CSC_OYN goes to CSC and goes to HOME_CSC_OYN User data right?
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> omr.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4733 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That's what you're doing wrong. Home CSC doesn't go to userdata. It goes as follows: BL to BL, AP to AP, CP to CP and CSC to CSC for a fresh installation. Home CSC would go to CSC, if you're upgrading from your current firmware. That would prevent from wiping your data. You only need 4 files.
bboii86 said:
That's what you're doing wrong. Home CSC doesn't go to userdata. It goes as follows: BL to BL, AP to AP, CP to CP and CSC to CSC for a fresh installation. Home CSC would go to CSC, if you're upgrading from your current firmware. That would prevent from wiping your data. You only need 4 files.
Click to expand...
Click to collapse
I matched them up like you said but I'm still getting the same error, I'm trying to update from an older version so I'm using Home CSC, but I also tried the normal one. Maybe it's because I'm in an older version? Im trying to upgrade from QGL (Aug 2017)
liquid286 said:
I matched them up like you said but I'm still getting the same error, I'm trying to update from an older version so I'm using Home CSC, but I also tried the normal one. Maybe it's because I'm in an older version? Im trying to upgrade from QGL (Aug 2017)
Click to expand...
Click to collapse
Same thing keeps happening to me. Did you find a solution?
rogerandgina said:
Same thing keeps happening to me. Did you find a solution?
Click to expand...
Click to collapse
No, nothing yet. I've tried updating to RB9 or RC5 and the same error. I've also used modded odin and normal odin 3.13.1
Any idea @bboii86?
liquid286 said:
No, nothing yet. I've tried updating to RB9 or RC5 and the same error. I've also used modded odin and normal odin 3.13.1
Any idea @bboii86?
Click to expand...
Click to collapse
I took mine to a samsung experience center at best buy and they flashed crc5 on mine. I had a problem with my binaries.
These CRC5 Odin files worked perfectly for me.
liquid286 said:
No, nothing yet. I've tried updating to RB9 or RC5 and the same error. I've also used modded odin and normal odin 3.13.1
Any idea @bboii86?
Click to expand...
Click to collapse
This will help. This link is the OTA update CRB9 to CRC5 for anyone who is on build CRB9, trying to update to build CRC5. Just simply download the file, transfer it to your sd card, turn off the device, put the device in recovery by pressing volume up, bixby button and power button all at the same time for about 8 seconds. Scroll down to update by sd card, locate the CRB9 to CRC5 file, select the file and that's it. It will update and it will wipe your data. So please be sure to backup your data with the smartswitch app on your phone or smartswitch application on your computer, before applying the OTA update.
Download here: CRB9-TO-CRC5
bboii86 said:
This will help. This link is the OTA update CRB9 to CRC5 for anyone who is on build CRB9, trying to update to build CRC5. Just simply download the file, transfer it to your sd card, turn off the device, put the device in recovery by pressing volume up, bixby button and power button all at the same time for about 8 seconds. Scroll down to update by sd card, locate the CRB9 to CRC5 file, select the file and that's it. It will update and it will wipe your data. So please be sure to backup your data with the smartswitch app on your phone or smartswitch application on your computer, before applying the OTA update.
Download here: CRB9-TO-CRC5
Click to expand...
Click to collapse
I've heard about installing the OTA files to update and that might work. I think I expressed myself incorrectly, I'm in version QGL and I'm trying to update to android 8 either RB9 or RC5, do you know where I could get the OTA files to go from:
QGL to QJC
QJC to QK5
QK5 to QL1
QL1 to RB1
RB1 to RB9?
BTW, the error I'm getting on Odin now is: <ID:0/005> Complete(Write) operation failed.
liquid286 said:
I've heard about installing the OTA files to update and that might work. I think I expressed myself incorrectly, I'm in version QGL and I'm trying to update to android 8 either RB9 or RC5, do you know where I could get the OTA files to go from:
QGL to QJC
QJC to QK5
QK5 to QL1
QL1 to RB1
RB1 to RB9?
BTW, the error I'm getting on Odin now is: <ID:0/005> Complete(Write) operation failed.
Click to expand...
Click to collapse
Flash CRB9 odin and then update CRB9 to CRC5. That would be the easiest method.
Download here: G955USQU2CRB9
USERDATA_ATT
bboii86 said:
Flash CRB9 odin and then update CRB9 to CRC5. That would be the easiest method.
Download here: G955USQU2CRB9
USERDATA_ATT
Click to expand...
Click to collapse
YES, that worked perfectly :good:! I had tried before updating to RB9 and had the same error that I had with RC5, but I didn't have the USERDATA file and with that it worked flawlessly, maybe that's why I couldn't update straight to RC5 and I needed the USERDATA file for that one
---------- Post added at 09:00 PM ---------- Previous post was at 08:53 PM ----------
rogerandgina said:
Same thing keeps happening to me. Did you find a solution?
Click to expand...
Click to collapse
I finally got it to work with the help of @bboii86, what I did was use odin to install RB9 using the userdata he shared and then upgraded to RC5 with the OTA file he shared on this link:
Download here: CRB9-TO-CRC5
The files for RB9 are here
User data for RB9 here
@l.hieunghia1999 try this as well, maybe it'll help
Thanks @bboii86. Never have issues with your uploads.
striker661 said:
Thanks @bboii86. Never have issues with your uploads.
Click to expand...
Click to collapse
No problem. Glad to help out. ?
Worked 1st time. :good:
Got a phone off ebay with Oreo already.
I've tried multiple firmware already with odin. Just cannot get it to flash. Any suggestions?
Using Odin v3.13
This is the last firmware, April 20th 2018. G930VVRS4BRC3
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The message that accompanies the big red FAIL sign on top.
I've already used odin 3.12 and another firmware that was dated Jan 2018.
Tried another suggestion by unticked autoreboot and F. Reset time
Am I just doing this wrong?
Thanks for reading:fingers-crossed:
human101 said:
Got a phone off ebay with Oreo already.
I've tried multiple firmware already with odin. Just cannot get it to flash. Any suggestions?
Using Odin v3.13
This is the last firmware, April 20th 2018. G930VVRS4BRC3
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The message that accompanies the big red FAIL sign on top.
I've already used odin 3.12 and another firmware that was dated Jan 2018.
Tried another suggestion by unticked autoreboot and F. Reset time
Am I just doing this wrong?
Thanks for reading:fingers-crossed:
Click to expand...
Click to collapse
What does it say on the on the phone after it fails? There is usually an error message on the teal download mode screen too
lvpre said:
What does it say on the on the phone after it fails? There is usually an error message on the teal download mode screen too
Click to expand...
Click to collapse
SW REV CHECK FAIL =: [aboot]Fused 8 > Binary 4
[1]emmc write fail : aboot
Thank you.
human101 said:
SW REV CHECK FAIL =: [aboot]Fused 8 > Binary 4
[1]emmc write fail : aboot
Thank you.
Click to expand...
Click to collapse
You'll need to flash a firmware that is b8. Check the last 5 digits... It needs to be an 8, you are using a 4 firmware
lvpre said:
You'll need to flash a firmware that is b8. Check the last 5 digits... It needs to be an 8, you are using a 4 firmware
Click to expand...
Click to collapse
Good, in advance I appreciate the help you can give me since the phone is unusable, it is a Galaxy S7 G930V and I am stuck in a firmware with binary 8.
The issue is that the mobile was super well running Turrón 7 G930VVRS4BRC3 (binary 4), everything worked perfectly well, one day I decided to update to the latest version for then Oreo 8 G930VVRS4CRI1 (binary 4) using Odin 3.13, the phone in his first reboot gets stuck in the Verizon logo, it also heats up a lot, after I forced the shutdown using buttons volume down and on, I turn on the phone and after several attempts manages to start but sending constant messages "Google Play service stopped "," phone stopped "," messages stopped "," clock stopped "," Samsung keyboard stopped "," wifi stopped "" settings stopped ", etc., again and again with each of the applications, not even a minute when the Samsung logo reboots and the same thing happens again, fortunately I managed to flash again the firmware I had previously (Turrón 7) and the mobile continued to work perfectly if No problem.
As time goes by, a new update of Oreo 8 G930VVRS8CRK1 (binary 8) is released, which I updated thinking that all those problems had been solved and I have found that the same errors continue.
When I try to downgrade by flashing the Turrón 7 G930VVRS4BRC3 (binary 4) it happens to me exactly like the fellow @ humana101.
I have flashed the binary firmwares 8 of the G930T and G930U versions downloaded from both Updato and Sammobile and with all of them the same bootloop and close of APP occur.
I have come to the conclusion that the problem is that my Oreo 8 update does not work for my device.
Can someone help me downgrade again Turrón 7, find some firmware that serves me or some Turrón 7 with binary 8?
The device is useless, help!:llorando:
can we downgrade binary
lvpre said:
You'll need to flash a firmware that is b8. Check the last 5 digits... It needs to be an 8, you are using a 4 firmware
Click to expand...
Click to collapse
i just need to know, i have s7 g930fd with oreo having binary 3 as i checked following ur method by noticing 5th digit from the last firmware model, now i have checked the list of available roms at sammobile and could not find nougat rom with binary 3, so now the question is can it be downgraded to nougat or can we exchange the oreo binary 3 file with nougat binary, like any way to downgrade from oreo binary 3 to nougat, please suggest
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
My trusty Galaxy Note 3 N9005 32GB has been giving me a few minor file errors recently, so I re-installed from a nandroid backup (ROM is MagMa NX VX PCE 6.0.1) with Phantom kernel) and it's been great for a few weeks now, performing better than ever in fact.
However yesterday, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."
I can't get into Recovery or use ADB, so I ran Odin on my PC and it showed the device as Added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin started sending the TWRP .tar file normally, it quickly reported "Get PIT for mapping ... There is no PIT partition". The phone screen showed "UDC START" then "MMC: mmc_read fail". The USB port and USB cable are the same ones I've been using for some recent adb pull backups so they should be OK.
I tried installing a new PIT file (first from a previous backup of my own setup, and then from generic versions for this device) but Odin with AutoReboot, Re-Partition, and F.Reset Time ticked showed:
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone showed:
UDC START
MMC: mmc_read fail
I then tried downloading a 4files repair installation of a stock Lollipop ROM (the most recent I could find for this device, N9005ZSUGPJ2) and used Odin to install the included PIT, AP, BL, CP and CSC files, with Nand Erase All selected too:
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time, the phone showed:
UDC START
MMC: mmc_read fail
ERASING USERDATA PARTITION...
I could really do with some expert help or advice here from anyone who knows more about these things than I do... or do I have an unexpected brick on my hands? Thanks!
Andre
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
here is the procedure you have to follow...
PLEASE.....DO NOT skip ahead, just follow my instructions in sets,
Here are the Files you NEED to download:
Odin3 v3.10.zip
CHARGE the device to 100% Battery BEFORE beginning!
Download and extract the Files.
Open ODIN, place each of the Files in corresponding boxes:
BL = BL
AP = AP
CP = CP (MODEM)
CSC = CSC
Please select these Check-boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
START!!
After it reboots, WAIT 10 Minutes, Skip the Wizard and perform a Factory Data Reset!
rayman95 said:
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
Click to expand...
Click to collapse
Which phone version, or which 4files?
Phone is a Galaxy Note 3 N9005 (UK 32GB).
File was from https://zfirmware.com/download-samsung-repair-firmwares/ , version http://www.mediafire.com/file/9ux01...3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
I was hoping to be able to use this device until the Note 10 is released, but maybe I'll have to settle for an S10+. Problem is, I prefer my nice Note 3 to anything they have released since (removable battery, no stupid curved-edge display, proper physical front buttons away from the main screen, a bigger - OK, wider - display than anything since, etc)
Andre
andrewilley said:
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
Click to expand...
Click to collapse
From my own experience, this problem is a manufacturing defect that affects a lot of samsung devices produced from Q3 of 2014 until Q2 of 2015. The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
However, I managed to fix a Galaxy S5 with the method I already described. And that has been presented as a momentary solution by several xda users, like here.
I wrote : momentary solution because this error is definitely a hardware failure, a fixed device will only work for a random period then the problem will get worse until the device become completely unusable.
Fortunately, you can buy a new motherboard for less than 30euro. And that's what I recommend you to do.
andrewilley said:
Galaxy-Note3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip[/url] . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
Andre
Click to expand...
Click to collapse
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
zlazaar said:
The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
Click to expand...
Click to collapse
I've been noticing a few file-read errors over the last 5 months or so, which I put down to bad blocks even though e2fsck -cfv showed zero errors. I thought a reformat and nandroid restore had fixed it, but obviously if the problem is lower down that might just have been delaying the inevitable. I suspect that installing a new mobo would not really be a good long-term plan as that could just as easily have the same issue (as they'll all be 4+ years old by now).
rayman95 said:
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
Click to expand...
Click to collapse
I'll try the KitKat version (normally I'd look for a BTU version, but beggars can't be choosers as the saying goes). If I can at least get it running for now and restore my backup via TWRP then I can do a more relaxed and controlled switchover to an S10+.
Andre
Whatever I try, I can't get a new PIT file to re-partition the memory:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2252 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
Phone shows MMC: mmc_read fail
Does anyone have a known good PIT file for the UK Note 3 N9005 32GB, along with a matching BL/AP/CP/CSC combo (any ROM version would do) that they would be willing to either upload or point me to?
Thanks,
Andre
I guess I probably should treat this device as a brick now and get it replaced, no other suggestions?
Andre
sammobile forum ??
JJEgan said:
sammobile forum ??
Click to expand...
Click to collapse
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
andrewilley said:
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
Click to expand...
Click to collapse
i send you my french files....
take here my files...
Thanks, I'll download and give them a try when I get back on home wi-fi. I fear I'll probably get the same results, but at least I'll have tried everything before giving up on it.
Andre
File downloaded, thank you. There doesn't seem to be a matching PIT file in there though, just the BL, AP, CP and CSC. Is that correct? As stated earlier in the thread, the PIT seems to be corrupted on my device, so was hoping for all 5 files to match...
Andre
rayman95 said:
take here my files...
Click to expand...
Click to collapse
I did try the 4files in your ZIP, but without a new PIT file I got the same partitioning error as before:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Andre
the pit HERE...
good luck..
rayman95 said:
the pit HERE...
good luck..
Click to expand...
Click to collapse
Many thanks for all your help, but still dead even with the correct PIT I'm afraid.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this phone is on its way to the Great Home for Expired Technology in the Sky.
Andre
Just read some user not this phone replaced eMMC chip.
From Aliexpress
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Thaser said:
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Click to expand...
Click to collapse
You need to put it in download mode first.
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Thaser said:
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Click to expand...
Click to collapse
Post a screen shot of your download screen and odin log.
ashyx said:
Post a screen shot of your download screen and odin log.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Thaser said:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
zfk110 said:
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
Click to expand...
Click to collapse
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Thaser said:
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Click to expand...
Click to collapse
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
zfk110 said:
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
Did the above, still no success. Stuck at initialization
Thaser said:
Did the above, still no success. Stuck at initialization
Click to expand...
Click to collapse
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
ashyx said:
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
Click to expand...
Click to collapse
I will second this. My laptop will not see Odin added at all for most of my devices. And out out of like 6 USB cables only 1 works for Odin downloading but good for everything else
Custom Binaries Blocked by FRP Lock
May I start you over with your diagnostics. Not initializing? Does this mean you cannot boot into recovery, at all? But can get into download mode which you cannot use?
Try booting to recovery and tell me if you see little red letters at the top left that say something about FRP lock. If this is your issue I'll explain what's going on with your device.
There are two types of FRP protection I've seen in this tablet. The first one most of us know of and it can be best described as being able to boot or power on compared to the other one which acts similar to a bootloop and does not power on.
This seems to be a common bug with the current Rootings applied to this device that are using CF-Root or a variation thereof. Samsung insisted that CF-Root shouldn't be used on this device and that's where the problem apparently comes from. The device owner is caught in a bootloop type of mode where the logo comes and goes and somehow accessing recovery is impossible. At the top left side of the screen in fine red letters reads, "Custom Binaries Blocked By FRP Lock. " This apparently shuts off the OEM unlock also leaving you with access to the Bootloader/Downloader, but Odin3 would refuse to flash even the official Firmware. Suddenly the impossible Hard-Brick comes to mind. Fortunately for all of us someone invented Odin3 and Samsung device owners rarely have to deal with a hard bricked device..
Here's what you need.:
Odin3.10 to Odin3,13. Either one works. The following file will give you Odin3.13.
The SM-T580 Binary 4 FRP Unlock file can be obtained here (this is a 1.98GB rar file):
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Extract the file, preferably to a folder of its own that you create.
Prep device for flashing (boot to download mode), connect to PC and fire up Odin3. The first section should light up blue means you're connected. Click on AP, go to the extracted 3file and doublr click on the file starting with the word "unlock." Wait til Odin does it's checksum and then you can press start.
This will reset your device to factory!!
Now you're going to want to Bypass the Google Account and remove FRP which is the first FRP I mentioned.
Let me know how it goes for you..