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.

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.

Problem Rooting Samsung Note 4 v(6.0.1 Marshmallow) SM-N910V

I've been trying to root my phone (note 4 from verizon) for a while and I keep running into this problem. This is what odin reads:
Method (CF-AUTO-ROOT)
<OSM>Added!!
<OSM> Enter CA for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v (ID:3.1005)
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialization. .
<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> cache.img.ext4
<ID:0/005>
<ID:0/005> complete(Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
I've tried the TWRP method, I downloaded the right file for my phone, update my drivers on pc, disabled* reactivation lock and this is what odin reads:
Method (TWRP)
<ID:0/005> Added!!
<ID:0/005> Odin engine v (ID:3.1005)
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialization..
<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>
<ID:0/005> complete(Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
I've used Odin version 3.07, 3.10, 3.12.3 and all have the same outcome. I've used two different usb cables and all USB ports on my laptop. (I have Windows 8.1 if that has anything to do with this).
For all attempts I've been in Download mode and this is what it's read:
Odin mode (HIGH SPEED)
Product Name: SM-N910V
Current Binary: Samsung Official
Reactivation lock: off
Qualcomm Secureboot: enabled (csb)
RP swrev: S1, T2, R1, A2, P1
secure download: enabled
UDC Start
Secure check fail: Recovery
<Android image>
Downloading...
Do not turn off target!!
Please help! I've looked all over Google and on sights on how to properly root Note 4 marshmallow 6.0.1. And again I've turned off Reactivation lock, tested the usb connection used different USB ports, used different files and re-downloaded the files USB debugging enabled. I don't know what else to try please help, any advice or tip would be greatly appreciated. Thank you. (Sorry for any typos)
P.s phone is still operating fine.

-spektor- said:
I've been trying to root my phone (note 4 from verizon) for a while and I keep running into this problem. This is what odin reads:
Method (CF-AUTO-ROOT)
<OSM>Added!!
<OSM> Enter CA for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v (ID:3.1005)
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialization. .
<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> cache.img.ext4
<ID:0/005>
<ID:0/005> complete(Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
I've tried the TWRP method, I downloaded the right file for my phone, update my drivers on pc, disabled* reactivation lock and this is what odin reads:
Method (TWRP)
<ID:0/005> Added!!
<ID:0/005> Odin engine v (ID:3.1005)
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialization..
<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>
<ID:0/005> complete(Write) operation failed.
<OSM> All threads completed. (Succeed 0 / failed 1)
I've used Odin version 3.07, 3.10, 3.12.3 and all have the same outcome. I've used two different usb cables and all USB ports on my laptop. (I have Windows 8.1 if that has anything to do with this).
For all attempts I've been in Download mode and this is what it's read:
Odin mode (HIGH SPEED)
Product Name: SM-N910V
Current Binary: Samsung Official
Reactivation lock: off
Qualcomm Secureboot: enabled (csb)
RP swrev: S1, T2, R1, A2, P1
secure download: enabled
UDC Start
Secure check fail: Recovery
<Android image>
Downloading...
Do not turn off target!!
Please help! I've looked all over Google and on sights on how to properly root Note 4 marshmallow 6.0.1. And again I've turned off Reactivation lock, tested the usb connection used different USB ports, used different files and re-downloaded the files USB debugging enabled. I don't know what else to try please help, any advice or tip would be greatly appreciated. Thank you. (Sorry for any typos)
P.s phone is still operating fine.
Click to expand...
Click to collapse
You CANNOT root the phone straight from MM. You have to unlock the bootloader first in 5.1.1, then flash twrp. Follow this guide: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144

SirLaughsalot said:
You CANNOT root the phone straight from MM. You have to unlock the bootloader first in 5.1.1, then flash twrp. Follow this guide: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Click to expand...
Click to collapse
I'm now at version 5.1.1 but can't figure out how to unlock bootloader. I need root permissions but I can't find any temp root app. And I'm unable to root my device still. All solutions I've seen required root access, or using kingroot, but that method doesn't work properly. (I'm very new to this sorry)
(UPDATE)
I found a solution, for temp root I installed supersu, root checker and kingo root. Kingo is a bit buggy at times but works. It gave me temp root so I can unlock bootloader.

-spektor- said:
I'm now at version 5.1.1 but can't figure out how to unlock bootloader. I need root permissions but I can't find any temp root app. And I'm unable to root my device still. All solutions I've seen required root access, or using kingroot, but that method doesn't work properly. (I'm very new to this sorry)
(UPDATE)
I found a solution, for temp root I installed supersu, root checker and kingo root. Kingo is a bit buggy at times but works. It gave me temp root so I can unlock bootloader.
Click to expand...
Click to collapse
Ok, glad to see you worked it out.
Follow this guide for a full how-to that walks you through the ENTIRE rooting/boot-loader unlock process, and how to keep permanent root on stock rom.
KingORoot installs spy-ware in your EFS folder that will slow down your device. Look here for more details and how to fix.

SirLaughsalot said:
Ok, glad to see you worked it out.
Follow this guide for a full how-to that walks you through the ENTIRE rooting/boot-loader unlock process, and how to keep permanent root on stock rom.
KingORoot installs spy-ware in your EFS folder that will slow down your device. Look here for more details and how to fix.
Click to expand...
Click to collapse
Thank you for the help I really appreciate it. I finally found a way to root my device.
Edit/update: How do I access my EFS Folder to get rid of the spy ware I didn't read anything on the thread provided, I suppose you just use a file explorer?

-spektor- said:
Thank you for the help I really appreciate it. I finally found a way to root my device.
Edit/update: How do I access my EFS Folder to get rid of the spy ware I didn't read anything on the thread provided, I suppose you just use a file explorer?
Click to expand...
Click to collapse
Use Root Explorer or similar app. I recommend you back-up the EFS folder before cleaning. Have fun!

-spektor- said:
I'm now at version 5.1.1 but can't figure out how to unlock bootloader. I need root permissions but I can't find any temp root app. And I'm unable to root my device still. All solutions I've seen required root access, or using kingroot, but that method doesn't work properly. (I'm very new to this sorry)
(UPDATE)
I found a solution, for temp root I installed supersu, root checker and kingo root. Kingo is a bit buggy at times but works. It gave me temp root so I can unlock bootloader.
Click to expand...
Click to collapse
I'd like to know how you got root on the latest firmware. I just bought a 2nd Note 4 and it came with the latest firmware. Neither of the rooting programs will work. Both fail miserably. and I've tried two dozen times. I had no problem rooting my other one since it came with 5.1.1, but this one has the 6.0.1 along with the latest security patch. Help a man out and let me know your secrets

BeckPC said:
I'd like to know how you got root on the latest firmware. I just bought a 2nd Note 4 and it came with the latest firmware. Neither of the rooting programs will work. Both fail miserably. and I've tried two dozen times. I had no problem rooting my other one since it came with 5.1.1, but this one has the 6.0.1 along with the latest security patch. Help a man out and let me know your secrets
Click to expand...
Click to collapse
If you have a stock note 4 on 6.0.1 the method I use is explained here http://forum.xda-developers.com/not...o-bootloader-unlock-upgrade-to-t3398144/page1 make sure to download the 6.0.1 official firmware before doing this just to be safe. And back up your phone because you might have to factory reset you phone after.

-spektor- said:
If you have a stock note 4 on 6.0.1 the method I use is explained here http://forum.xda-developers.com/not...o-bootloader-unlock-upgrade-to-t3398144/page1 make sure to download the 6.0.1 official firmware before doing this just to be safe. And back up your phone because you might have to factory reset you phone after.
Click to expand...
Click to collapse
Edit: you gotta unlock bootloader on 5.1.1 that's why you can't root 6.0.1 from stock Also triple check you phone can be rooted. You don't want to mess up your phone

That's the problem. The root apps don't work, so I can't get temp root in order to change to the developer version. It's that FIRST step that has me stuck. You can't continue with anything else without getting temp root first. The rest is a breeze after that.
This is my 2nd Note 4 in less than a month. The first came with 5.1.1 which made this process simple. Unfortunately, the second one was already upgraded. I got lucky on the first one. It would be sweet to root this one too, but with the latest version of 6.0.1 and unable to gain even temp root, I'm stuck. My own old Note 4 also has the same OS version and locked bootloader. It's in the same situation.
(yes... you just read I have (3) Note 4's on my account and all working. Also have Note 3 and Note 12.2 as well. I've flashed more times than should be allowed by law.)

You need to downgrade from 6.0 to 5.1.1 before you can do anything.
Sent from my SM-N910V using XDA-Developers mobile app

The version installed now is n910vvru2cpf3
I've got all the files from a previous note 4 downgrade/upgrade. However I don't see how I can use ODIN to flash a new ROM without root. Unless you're saying I should just flash (with ODIN) the system only version to roll back to 5.1.1 and keep the current bootloader. If thats' the case, and it works, I'd be good to go. I just hate using ODIN without being sure it will work. $250 is a terrible thing to waste.

BeckPC said:
The version installed now is n910vvru2cpf3
I've got all the files from a previous note 4 downgrade/upgrade. However I don't see how I can use ODIN to flash a new ROM without root. Unless you're saying I should just flash (with ODIN) the system only version to roll back to 5.1.1 and keep the current bootloader. If thats' the case, and it works, I'd be good to go. I just hate using ODIN without being sure it will work. $250 is a terrible thing to waste.
Click to expand...
Click to collapse
If you have a SM-N910V The way I downgraded my stock note 4 from verizon was flashed the file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via odin3 v3.11.1 (link: https://www.androidfilehost.com/?fid=24411628330026105 ) [Original post: http://forum.xda-developers.com/not...o-bootloader-unlock-upgrade-to-t3398144/page1 ] if your worried that it'll mess up your phone don't worry as long as you have the OFW 6.0.1 from Samobile.com (that's where I got mines from and it works so I do recommend) you can reverse any damage, at least from my experience you can. Just make sure you phone has a good connection to you your computer and the process will complete successfully.
Edit: FYI I'm not an expert on this topic but am familiar with things.

Jeez ... I've had an unrootable phone for 2 years now and I had forgotten more than I thought. I'd never be able to do all these steps in my sleep, but I got a much better handle on the process now.
You were right. You don't need root to use ODIN. I had forgotten that part. I got the process started and it worked. I'm in business, but what a work out! My brain is tired. It took almost four hours to get it to the point where I could start flashing another ROM. I did freak out when TWRP kept crashing while installing a ROM. It appears it won't install from an SD card. That's a real pain if you want to blow it away and start all over, but it works at least.
I followed this post and follow it 100% to the tee ... http://forum.xda-developers.com/note-4-verizon/general/guide-step-step-stock-n910v-6-0-1-to-t3426905
Recommendation for anyone having issues ... read the posts completely and be patient. It does work, but you must follow every step. I didn't want the CM ROM just yet, so I stopped at that point and flashed a different 6.0.1 ROM along with a new kernel. I stopped at step 53 and went off in my own direction. During the rooting process, I did end up using the PC version of the rooting software when I ran into trouble. Just give yourself plenty of time and read ... don't miss a step.
I did miss the part about copying the Jasmine ROM to the TWRP restore folder. I had wiped it all and ... well, oops. Had to go back several steps and start again. Time for me to run around and click the THANKS button for a lot of good people here. I thank you all. I forgot how much fun (ugh) this is!

SirLaughsalot said:
You CANNOT root the phone straight from MM. You have to unlock the bootloader first in 5.1.1, then flash twrp. Follow this guide: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Click to expand...
Click to collapse
cfauto root wont work with retail to dev verizon note 4 .

mojoswagger1980 said:
cfauto root wont work with retail to dev verizon note 4 .
Click to expand...
Click to collapse
No. CF Auto root wil NOT work. Please follow guides/search forums before you brick your phone. Verizon made this as hard as possible to mod.

Samsung S3 Sprint SPH-l710T not starting after upgrade try

Hello All,
I have Samsing S3 SPH-l710T Sprint phone, I was trying to use this phone for freedom pop.
I root the phone first then took some higher version image file and tried to flash with TWRP. When phone auto restarted it was not booting, it was restarting continuously, vibrating after some interval.
Positive thing is, its starting in download mode, so I have decided to flash with Odin3, for that I got flash stock rom
rapidgator site.
and followed the odin steps. I got below error message...
Code:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
One observation, when I have restarted phone in download mode the message was not usual, it was like this
Code:
ODIN MODE
PRODUCT NAME: SPH-L710T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (IN GRAY)
Warranty Bit: 1 (IN RED)
BOOTLOADER RP SWREV: 2 (IN GRAY)
and after odin fail, the message was like this...
Code:
ODIN MODE
PRODUCT NAME: SPH-L710T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (IN GRAY)
Warranty Bit: 1 (IN RED)
BOOTLOADER RP SWREV: 2 (IN GRAY)
SECURE CHECK FAIL: aboot
Please help me to restart my pnone and work for freedompop, at least it should for sprint.
Thanks!

AndroidFan186 said:
Hello All,
I have Samsing S3 SPH-l710T Sprint phone, I was trying to use this phone for freedom pop.
I root the phone first then took some higher version image file and tried to flash with TWRP. When phone auto restarted it was not booting, it was restarting continuously, vibrating after some interval.
Positive thing is, its starting in download mode, so I have decided to flash with Odin3, for that I got flash stock rom
rapidgator site.
and followed the odin steps. I got below error message...
One observation, when I have restarted phone in download mode the message was not usual, it was like this
and after odin fail, the message was like this...
Please help me to restart my pnone and work for freedompop, at least it should for sprint.
Thanks!
Click to expand...
Click to collapse
You can't root then update that phone, as far as I know. Also, make sure the .tar file you are flashing in odin is for the sph l710T. The T is important.
That aboot error looks troublesome.

madbat99 said:
You can't root then update that phone, as far as I know. Also, make sure the .tar file you are flashing in odin is for the sph l710T. The T is important.
That aboot error looks troublesome.
Click to expand...
Click to collapse
Thanks! for reply.
Oh! sad to hear. The tar.md5 I used, was for SPH-l710T only. I did make sure that "T"
If you find some workaround please let me know.
Thanks!

[SOLVED!!] Samsung S3 Sprint SPH-l710T not starting after upgrade try
I have successfully recovered it.
Code:
SPH-L710T_1_20150805092453_cj4hd76uo2.zip
zip has rar.md5
This is the file name, I have downloaded https://www.androidfilehost.com/?fid=745425885120712852

Glad you got it. Next time, do all your updates, then root. Much smoother process.

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?