Develop Bugs

Another Soft Brick...

Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED

I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?

bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin

audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.

britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home

bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.

[Q] Soft bricked? Need to restore back to stock

Hey yall,
Neighbor's kid handed me his Sprint galaxy s3 today and asked if I could fix it. It's not working at all right now. I'd like to think I know a thing or two about technology but I know jack about Android...I use the other brand of phones. Anyway, lots of searches led me here to ask for help.
Far as I can tell it's a Spring LPH-710 Samsung Galaxy S3. When I turn it on it has the firmware upgrade encountered an issue screen and it doesn't do anything else. I can't get VOLUP+HOME+POWER to work (recovery mode I think) but download mode works with VOLDOWN+HOME+POWER.
I went and downloaded the Kies program from samsung but it fails to load the software. here's the error message; CAN'T POST LINKS! arrrgggg. It says "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now?" It then says I should enter some recovery code from another PC which I don't have.
It also has some small red text on the phone screen after I saw the Kies error message. It says SW REV CHECK FAIL : Fused 2 > Binary 1. That makes no sense to me but it's red and Kies error out so I'm going to assume that's not good.
I don't have a recovery key to use and the kid tells me he never backed it up to a computer before. I've read Odin is the preferred method to use for stock recovery but I don't know what files to download and use. Apparently, people are pretty unhappy with Kies...kinda like iTunes I guess. Why can't the Kies software wipe and reload the phone? Am I doing something wrong?

The device malfunctioned or had an error when he tried doing an update / flash. And if Kies is malfunctioning you can try PC Odin.
Download Sammy drivers of device, download the stock .tar image of the sprint s3 ( L710VPUDND8 ), download Odin v3.07
- At PC. Open Odin in admin mode. Click PDA and select the .tar image file and let that load and leave everything else alone in the program.
- On device press vol dn + home + power to get into download mode, press vol up to continue.
- Plug in device and let driver installation be completed. If a box in Odin ( on PC ) doesn't show a COM:##, replug device or try different ports and cables.
- Once you have that all set up click start and leave it to flash. It takes roughly 15 minutes to flash the whole thing or lesser.
If all else fails tell him to bring it in for servicing.
Posted via XDA Mobile

Thanks for the reply Sparks. I downloaded Odin 3.07, uninstall Kies and rebooted the PC. When I loaded the .md5 file, I then plugged in the phone and saw it look for drivers. The phone shows up on COM3. Below is what I see after I press start. Doesn't look good to me! Did I get the right file?
I've read that attepting to alter the operating system will void the warranty. Would this line on the download screen indicate he tried to do that? Current Binary: Custom. He said the contract is up in March so I'd hate for him to get screwed over by this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

That's the right file. Says md5 is valid.
Binary custom and/or warranty bit 1 means he already tried to flash something and it ticked the counters so he's out of luck getting it repaired.
Go download the Galaxy S3 Samsung drivers through the official site and install them, reboot pc and try the method again in a different USB PORT ( Preferebly 2.0 slots ) some ports and different cables can be iffy at times.
Posted via XDA Mobile Free

Help im new to phones and mine is "Soft bricked" (PLEASE HELP :) )

My samsung galaxy s3 mini was rooted and my friend gave it to me and i didnt know that i was rooted so i just went into backup and reset and now when i turn it on it is in a constant "bootloop" on the loading screen for att ive tried to use odin but this is the error i get
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i dont know what to do but if anyone can help me please thank you so much in advance

Any particular reason you need to re-partition?
Also, this forum is for the s3, not the s3 mini.

audit13 said:
Any particular reason you need to re-partition?
Also, this forum is for the s3, not the s3 mini.
Click to expand...
Click to collapse
im sorry i just seen s3 and i thought that it would be sorta the same and what is re-partition?

It involves partitioning/re-partitioning the phone's internal memory.
The simplest way to return the phone to stock would be to flash the phone's stock firmware from sammobile.com. Just make sure that you are flashing the same version currently installed on the phone.

wow man thanks so much i am getting the firmware right now, do i just use odin?

Yes, just make sure you are flashing the same version that is currently on the phone.
Open Odin 3.07 (this is the version I recommend), do not check anything except f.reset time. Flash the phone. When you see the word "reset" in the status windows, remove the USB cable, remove the battery, replace the battery, boot into recovery, perform a factory reset/wipe and clear the cache. Reboot.
BTW, the fact that the phone is rooted doesn't normally cause a bootloop when resetting the phone, at least this has been my experience with several different rooted phones.

audit13 said:
Yes, just make sure you are flashing the same version that is currently on the phone.
Open Odin 3.07 (this is the version I recommend), do not check anything except f.reset time. Flash the phone. When you see the word "reset" in the status windows, remove the USB cable, remove the battery, replace the battery, boot into recovery, perform a factory reset/wipe and clear the cache. Reboot.
BTW, the fact that the phone is rooted doesn't normally cause a bootloop when resetting the phone, at least this has been my experience with several different rooted phones.
Click to expand...
Click to collapse
well thank you alot man i just finished everything and once again thanks, if i have any more money on my paypal you surely would be getting some thanks again

Please do not send me anything. Saying "thanks" is enough. We are all here to help each other and learn from one another.
Enjoy your revived phone

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.

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?