Develop Bugs

[Q] Softbrick, bootloop, TWRP Password

My girlfriends S3 (Bell, I747M, d2can) is currently boot looping. It had a custom ROM on it, but I'll be damned if I could tell you which one. It was working, then it wasn't. No updates, no flash/wipe/etc.
Now I turn on her phone, and it gets to the ROM's boot screen, and just as it's about to complete, it restarts again. I can enter TWRP (2.6.3.1) but it requires a password (which is a bug, afaik). I can press "cancel" and try to reset/wipe, but it won't mount or reset the cache partition, so it fails.
I used Odin (3.07, 3.09) to try and flash TWRP 2.6.3.0 and 2.7.0.0, and both failed. The result was Odin would reboot the phone, then it would enter the same bootloop, and the recovery would still be TWRP 2.6.3.1.
I tried downloading a stock S3 firmware and flashing it with Odin. Same problem.
I've tried new drivers. New cable. New USB port. I've tried using a different computer. Always the same result.
So a summary of what I can/can't do:
Can't use TWRP to reset/wipe
Can't use ADB Sideload
Can't modify device via ADB
CAN see the device via ADB
CAN enter download mode
Any help?
I pulled DMESG at some point during all this. Maybe it can help shed some light: http://pastebin.com/4c2uL3Qq

Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.

theramsey3 said:
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
Click to expand...
Click to collapse
Appreciate all the help! I've tried pretty much every combination.
I've turned off auto-reboot, flashed, but Odin stops at:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
I assume that's where it's supposed to be. Then I enter recovery and it's still the same TWRP 2.6.3.1. Very strange.
I don't think her phone is using 4.3 bootloaders, as I don't remember them being available when I flashed this phone. I'm a Nexus guy, so maybe I'm doing something wrong this time.
EDIT: I also seem to recall on my phones that when I flashed something in Download/Fastboot mode, there was a progress bar of sorts on the phone itself indicating it was receiving something. On this phone it doesn't display anything to imply something's happening.

Boot into download and let us know what it says on the download screen. If you have the 4.3 bootloader, try flashing a pre-rooted 4.3 Bell ROM using Odin 3.07. If you have a lower version bootloader, try flashing a pre-rooted 4.1.1 or 4.1.2 ROM.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139036464
In Odin, don't check auto reboot. When you see reset in the status windows, disconnect the USB cable and pull the battery. Boot into recovery and wipe cache, data, and reboot.

Thanks for the reply! I'm 99% sure it's a pre-4.3 bootloader. Here's what it shows in DL mode:
ODIN MODE
PRODUCT NAME: SHG-I747M
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
DUALCOMM SECUREBOOT: ENABLE
If I recall correctly, a 4.3 bootloader would show two more lines at the bottom.

Tried installing a 4.1.1 ROM (root66_BMC_I747MVLDLK4)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDLK4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
4.1.2 (root66_BMC_I747MVLDMF1.7z)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDMF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

I feel it's worth mentioning again: At no point, while using Odin, does the phone display a transfer bar of any sort.

Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.

audit13 said:
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
Click to expand...
Click to collapse
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.

X04D said:
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
Click to expand...
Click to collapse
Try this: when you flash with Odin, uncheck auto reboot, start the flash process. When you see the word reset in the status window, remove the USB cable, pull the battery, and boot into recovery.

[Q] Unable to flash to stock with odin / having two 0 directories

So newb questions and might have been answered but I have been unable to find the answer I'm looking for.
Background:
SGH T999
Original I was on 4.1 stock. I used towelroot and was able to root and all that jazz. I uploaded an old version of CWM to my phone and was unable to flash and ROMs, they would all hang on the Samsung Galaxy SIII screen.
I updated CWM to put on a Cyanogen Mode ROM and all was good. I tried out a couple other ROMs then decided I wanted to go back to stock and see how stock 3.3 or 3.4 was. I tried using Odin to bring back to stock and no luck. I then installed PhilZ recovery and booted to Wicked ROM for 4.1. After this I got current TWRP and tried to update other roms. I went into ROM manager switched over to CWM 6.0.4.5 then updated my kernel. At some point along the way I noticed that on the internal sd card I have a 0 directory inside my 0 directory.
Now when I reboot my phone into Recovery mode I see a Samsung Galaxy SIII screen with the Cyanogen guy on it, then it loads to CWM but nothing is on the screen but the hat, then after a couple of seconds it loads to a Samsung screen quickly, then to the Samsung Galaxy SIII and hangs indefinitely. I'm still able to get the phone to go into download mode fine. Now I'm trying to just bring back to stock but not having any luck. Here's my repro:
1. Put hardware into download mode (HOME + Vol Down + Lock).
2. Open Odin 3.09 as Admin (I'm using Win 7).
3. Connect hardware to computer (Odin recognizes 0:Com5).
4. Place "T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5" in AP field.
5. With only "Auto Reboot" and "F.Reset Time" selected press Start button.
RESULT:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then on my hardware I get
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Offical
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
SW REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Any idea's how I can bring this back?

tiger_johnson said:
*snip*
Any idea's how I can bring this back?
Click to expand...
Click to collapse
Hmm, if the device is recognized in your PC by ODIN there's still hope. I personally recommend TWRP (LINK for latest ODIN flashable version) for everything as CWM has caused havoc with my phone before. Stay away from it. IF you can still access recovery, do format everything, including the internal SDcard. Also please use the PIT file when trying to use ODIN for the MD5 firmware you're choosing. LINK for the PIT file (choose your model's PIT and put it on the PIT part of ODIN then proceed on flashing the MD5 firmware - credit goes to DocHoliday for the PIT files). That little file can sometimes fix stuff when trying to ODIN the device back to stock firmware. Just giving ideas, don't give up and best of lucks!

You can't flash MD5. It looks like you are currently running MJC base firmware which means you can ONLY flash MJC or NC2 with Odin. Do not try to downgrade via any method or it will hard brick your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
"SW REV CHECK: Fused 1" means you currently have MJC. It will change to Fused 2 if you update to NC2. (If I'm remembering all those nemesis right).
Just FYI in case anyone was wondering.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Memory Damaged message, won't reset, recovery mode fails (red triangle,Android down )

Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.

Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.

Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...

The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?

Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.

I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.

I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.

I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk

The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!

I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe

Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.

SGH-M919 - Bad Firmware Flash - Recovery Broken - No PIT Partition

Can still get into download mode. Trying to flash the following stock ROM.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Removed!!
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
---
On Windows 7 Pro x86_64. I've tried different cables and I always use "run as administrator" when running Odin 3.0.7. At this point I've done so much to this phone to try and root, unlock, etc. to load custom ROM, that I just want this back to stock and I'm leaving it alone. These are a pain in the ass to flash. I've never had a hard time like I have with these Galaxy S4's.
From what I gather I can just flash a stock ROM, but if the above ROM isn't, can someone share a link to a valid stock ROM? Can anyone help me out? :crying:

Also, when I am in Download Mode I see the following status info in the upper left hand corner.
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX KERNEL VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC: BURST MODE enabled

It's possible the phone was flashed with some firmware beyond NB4 (I think there was an NK2 and definitely an OH3). Try flashing OH3 which is the very latest and see if that will go through.

Had the same problem with someones phone and the only way it was fixed was by trying multiple odin versions and different usb cords and eventually i got it to go through. The usb cord that came with the s4 worked while unofficial ones wouldnt. Cant remember the version of odin try at least 3 different versions with OH3 and you should be ok. Common problem with odin and unofficial cords etc. Just keep trying.

lordodin912 said:
Had the same problem with someones phone and the only way it was fixed was by trying multiple odin versions and different usb cords and eventually i got it to go through. The usb cord that came with the s4 worked while unofficial ones wouldnt. Cant remember the version of odin try at least 3 different versions with OH3 and you should be ok. Common problem with odin and unofficial cords etc. Just keep trying.
Click to expand...
Click to collapse
Frankenscript said:
It's possible the phone was flashed with some firmware beyond NB4 (I think there was an NK2 and definitely an OH3). Try flashing OH3 which is the very latest and see if that will go through.
Click to expand...
Click to collapse
Alright, I'll track down OH3 and see if that works. Thanks for the advice.

A320FL Recovery Bricked And Stuck On Bootloading

Hi everyone,
so here is the issue I'm facing with my A320FL.
Last week, after I had it all reinstalled properly, phone restarted and got stuck on FRP lock menu.
So I decided to wipe it all and reinstall with proper official ROM again.
I used Odin 3.13.3 launched as Administrator and latest Samsung Drivers.
I download latest official 8.0.0 ROM from SAMmobile.
I used the procedure with BL, AP, CP and CSC files (I don't mind losing all my data, I have backup) and all goes fine up to the green PASS! (I disabled Auto Reboot in Odin's Options just to take the screenshot):
https://ibb.co/HVrnxbw
then phone restarts, then goes with "installing updates" and quickly go up to 32%, then waits a bit: https://ibb.co/t392t7Q
then restarts again, then goes "Erasing" for a like 2 minutes: https://ibb.co/FJHMT7g
then restart again, and then the problem appears when phone gets stuck on following screen:
https://ibb.co/zHby4dx
I cannot go to recovery and wipe cache or data as I've seen on other posts to resolve this issue as recovery is blocked.
If I reboot the phone with 'Volume down + HOME + Power', I get to this screen: https://ibb.co/4RhJgJG
then if I press 'Volume Up" I have this screen: https://ibb.co/Wnh5Hv0
So I have "FRP lock: ON" at the top of the screen, and I cannot install TWRP or any custom recovery (Odin ends with a fail message if I try so): https://ibb.co/0qPLFL5
And phone shows "Custom Binary Blocked By FRP Lock": https://ibb.co/hsLdKjs
So I cannot boot into the ROM, go in Developer Options and Enable OEM unlock :/
And everytime I try to reinstall the official ROM, I get stuck on the "No Command" screen.
Any idea on how to go back to proper state?
Thanks

Just wait it out a bit. If it auto goes to recovery, it goes through that, well because the phone is kinda slow. Wait out the no command thing for 5 minutes, if it doesn't proceed that's a different issue

Thanks for your answer.
When I wait on the no command screen, the phone then reboots after like 3/4 minutes, and eventually goes back to that same screen again.
Thanks

Any chance of an update or something to try on that one please?
Thanks

Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks

mhaxor said:
Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks
Click to expand...
Click to collapse
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.

RootingPro-18 said:
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.
Click to expand...
Click to collapse
I tried that, and nothing happens.

Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/

mhaxor said:
Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/
Click to expand...
Click to collapse
Send me PM i will try to help you.?

@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.

cyberbix said:
@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.
Click to expand...
Click to collapse
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
https://www.sammobile.com/samsung/galaxy-a3/firmware/SM-A320FL/XEF/download/A320FLXXS5CSJ1/300636/
Regards

mhaxor said:
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
Click to expand...
Click to collapse
What does your bootloader state in download mode (B:?).
I guess 4, if so you have the same softbrick then me. Did you search for a combination firmware supporting Bootloader type 4 ?

I only see this screen when booting up the phone: https://ibb.co/hsLdKjs

mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.

mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Dude try bypassing FRP, i will try to search for some tools for you!

The only way I managed to bypass FRP lock was with unlocking the OEM in the device's settings in developper mode, then installing a new recovery.
But of course I can't access this now.

is it dead?
cyberbix said:
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.
Click to expand...
Click to collapse
Edit: I was using the wrong version of (3.12) odin should have used version 3.13.
anyway you can shed some light on my issue as well? this was a friends phone (legit story), here in brazil these kids don't pay attention to what they are doing. they put google accounts on phones and fail to remember them nor do they care to. the device is showing similar symptoms. all I can really say is the device will only flash combination files, if I flash a firmware it only flashes the modem. when I got the device it was on bootloader 2 (b:2 firmware A320FLXXS2BRA9). then I ended up flashing a firmware that was b:3. after I did that the device will only go to factory binary, and like I mentioned before it wont flash the firmware just the modem.
on power up the device in the upper left conner says:
nad: passed
rpwb provisioned
in bootloader:
odin mode
download speed: fast
product name: sm-a320fl
current binary: Samsung official
system status: official
frp lock: on
secure download: enabled
ccic=
warrenty void: 0 (0x0000)
rp swrev: b:3 k:1 S:1
odin after flashing a firmware:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> sboot.bin.lz4
<ID:0/008> param.bin.lz4
<ID:0/008> cm.bin.lz4
<ID:0/008> boot.img.lz4
<ID:0/008> recovery.img.lz4
<ID:0/008> system.img.lz4
<ID:0/008> userdata.img.lz4
<ID:0/008> modem_debug.bin
<ID:0/008> cache.img.lz4
<ID:0/008> hidden.img.lz4
<ID:0/008> Home Binary Download
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

@mhaxor: Are there any news on your bricked device ? Have you been successful finding a combination firmware that works with latest bootloader ?

Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,

mhaxor said:
Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,
Click to expand...
Click to collapse
Do You have telegram?