Hey guys,
I'm kinda lost here, I bought this phone a few months ago on a black friday sale in the US.
A few weeks it started bootlooping (the 'preboot logo' kept flashing) it got worse and worse. Remember, I never tried to root, install a custom recovery/OS, nothing!
The only way to get it out of the bootloop was to do a factory reset or sometimes a clear dalvik. But it got worse and worse, and booting into recovery was getting harder and harder...
5 factory resets further, and dozens of dalvik clears, it it bootlooping again!! And it is now impossible to boot into recovery, only download mode.
So I reinstalled the os through odin using these files: https://forum.xda-developers.com/at.../nougat-odin-files-g928a-g928at4eqc6-t3596180
When that didn't work, I used these files: https://forum.xda-developers.com/at...odin-files-g928a-g928aucs4cqa1-build-t3576469
Same bootloop, and still impossible to boot into recovery via power+vol up+home.
You might ask, why don't you repair it under warranty?
Well, I live in france and samsung france refuses to even touch an american device!
Ps: here are the options I had ticked in odin:
1st time: F reset and re-partition
2nd flash: NAND erase, F reset and re-partition
3rd flash: bootloader update, NAND erase, F reset and re-partition
Here is a log, md5 checks included, in case you wonder:
<ID:0/006> 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/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I would greatly appreciate your help as I'm lost,
Many thanks in advance,
nxss4
I hope you receive a solution to this problem, I'm currently having the same problem and it literally appeared overnight.
Related
I've unbricked phones before and even messed with dead EFS partitions and lived to tell the tale, but I cannot for the life of me figure this one out.
Somebody gave me a S4 Mini (GT-I9190) that was bootlooping. I got it into download mode and ODIN flashed a firmware without any problems. When it reboots, it says "Recovery Booting" for a few seconds, then turns off and bootloops again. Download mode continues to work, have flashed many other firmwares, but always the same thing. It just will not boot into recovery.
Tried CWM, TWRP and Philz (all found from various threads on this forum) and all of them seem to flash properly on Odin, but recovery will just not work. I even got a PIT file and repartitioned, to no avail. NAND Erase All with PIT and firmware too makes no difference.
I cannot try the debrick.img advice because the phone is not hardbricked. As far as I can tell, the issue is that the recovery partition is completely borked. But trying to search for ways to restore the recovery partition keeps taking me to the same old threads about how to access recovery mode using buttons and nothing about how to rebuild it!
Any thoughts? Any suggestions on where I should look too are appreciated.
Oh and yeah. to complicate matters a little, I have no idea what firmware version was on it before it died. Samsung Kies tries to initialize with a XSG firmware, so thats the one I downloaded from sammobile. And nope, firmware initialization thru kies also makes no difference at all.
Did you try stock recovery?
As far as I know, it was stock recovery when I got it. Wouldn't boot, so tried the rest. Flashing stock firmware did not make any difference, so don't think stock recovery works either. Have not tried extracting stock recovery from the odin tar and flashing directly though.
karthikrr said:
As far as I know, it was stock recovery when I got it. Wouldn't boot, so tried the rest. Flashing stock firmware did not make any difference, so don't think stock recovery works either. Have not tried extracting stock recovery from the odin tar and flashing directly though.
Click to expand...
Click to collapse
Its been a long time but i would like to know if you were able to fix it, i got exacctly the same problem and i have tried to flash everything on odin they seem to flash ok but booting to recovery i get "no command| error and the phone just reboot, see my odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_YER_I9195YERCNJ3_CL3081440_QB2781319_REV01_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<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> AP_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> persdata.img.ext4
<ID:0/008> persist.img.ext4
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> NON-HLOS.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> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
I re-flashing stock firmware 6.0.1 EQF1 and i get this notification, please help me
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Write)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
nobody here, thanks all, i sold it
we have to fid a way past tht signed portion
Hi everyone,
looks like my mobile remains in bootloop (Samsung Logo) and I can’t solve it since a few days. As I didn’t find the right solution in the forum I hope that somebody of you have a clever idea what I could test.
It started that the phone rebooted every few minutes (maybe an update was running) and I couldn’t do anything. After I wiped cache and data in the recovery mode (factory reset) the mobile worked for one day. As I needed to reboot the mobile I get stucked on the screen with the Samsung logo.
As I’m still able to access download and recovery mode I tried the same procedure as written above without success. I downloaded the latest firmware (A320FLXXS5CSK1 / DBT) with samfirm (V.0.5.0) and flashed it with Odin (V3.14.1). This was successful with Odin but I waited over an hour and the mobile didn’t pass over the Samsung screen. I tried to repeat the procedure and disabled autoboot – no success even after starting samsung recovery mode and wipe cache + data. (Odin successful – installing android on mobile after reboot remains on samsung logo)
In recovery mode I see the following failures but not sure if it indicates to the root cause as I tested the recovery mode with a working SMA320FL and saw the same failures.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to clear BCB message: failed to find /misc partition
I had an SD card in usage. I tried it with and without: No change.
I can’t install TWRP as the phone is FRP locked and as soon as I try to install TWRP it will be blocked. As I couldn’t find a combination file with the same binary I couldn’t try the described procedure by forens1c.
https://forum.xda-developers.com/sa...20fl-2017-unlock-solution-frp-update-t3884971
Downgrade as far I understood is not possible due to the latest version of bootloader.
Further information:
Android 8.0
SM-A320FL
Current binary:Samsung Official
System Status: Custom
FRP Lock: On
B:5 K:3 S:3
Odin Log as example:
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> userdata.img
<ID:0/006> modem_debug.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 3864 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Would be good to have any advice what else could be tested.
Flix24 said:
Hi everyone,
looks like my mobile remains in bootloop (Samsung Logo) and I can’t solve it since a few days. As I didn’t find the right solution in the forum I hope that somebody of you have a clever idea what I could test.
It started that the phone rebooted every few minutes (maybe an update was running) and I couldn’t do anything. After I wiped cache and data in the recovery mode (factory reset) the mobile worked for one day. As I needed to reboot the mobile I get stucked on the screen with the Samsung logo.
As I’m still able to access download and recovery mode I tried the same procedure as written above without success. I downloaded the latest firmware (A320FLXXS5CSK1 / DBT) with samfirm (V.0.5.0) and flashed it with Odin (V3.14.1). This was successful with Odin but I waited over an hour and the mobile didn’t pass over the Samsung screen. I tried to repeat the procedure and disabled autoboot – no success even after starting samsung recovery mode and wipe cache + data. (Odin successful – installing android on mobile after reboot remains on samsung logo)
In recovery mode I see the following failures but not sure if it indicates to the root cause as I tested the recovery mode with a working SMA320FL and saw the same failures.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to clear BCB message: failed to find /misc partition
I had an SD card in usage. I tried it with and without: No change.
I can’t install TWRP as the phone is FRP locked and as soon as I try to install TWRP it will be blocked. As I couldn’t find a combination file with the same binary I couldn’t try the described procedure by forens1c.
https://forum.xda-developers.com/sa...20fl-2017-unlock-solution-frp-update-t3884971
Downgrade as far I understood is not possible due to the latest version of bootloader.
Further information:
Android 8.0
SM-A320FL
Current binary:Samsung Official
System Status: Custom
FRP Lock: On
B:5 K:3 S:3
Odin Log as example:
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> userdata.img
<ID:0/006> modem_debug.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 3864 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Would be good to have any advice what else could be tested.
Click to expand...
Click to collapse
Try repartition device.
i got twrp on there and magisk but couldnt log in to my samsung and google accounts, an i read startin odin i had to log out first from them, which i did so i thought i might have missed something so i did it all over and now its bricked.
it started out with getting black screen with a tiny red text that i needed official rom or something like that. and it got that if i tried booting regularly or even trying to boot twrp.
so i currently can only get into download mode and it wont let me flash new twrp or official firmware. i tried flashing recovery, bootloader and other things separate and the all fail so i'm able to enter download mode but cant do anything with odin.
this is my latest odin log, it just stops and i get the error on my phone in red text looking pretty much the same, only thing that seem to change is if it says bootloader or system etc.. the odin log saying it failed doesnt show up until i unplug or exit, and i waited a few hours the first time so i knew it was a done deal before aborting it
i'll add picture of how my download mode looked as it fails and another how it looks if i try starting the phone in any other way, it tells me to use emergency recovery in smart switch for pc but when doing that my phone isnt showing up so i can't do that neither. and that screen only showed up after i tried flashing the new firmware.
Code:
<ID:0/004> 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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6557 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> up_param.bin
<ID:0/004> cm.bin
<ID:0/004> keystorage.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
i got a G960F/DS and restoring it in the beginning i always had an old 2018-2019 security patch running android 9, not sure exact which firmware but the fw zip i tried flashing was called G960FXXU2CRLI_G960FOXM2CRLI_DBT
if that makes any difference. i tried finding something something in a similar time frame as my original one which is why i chose that one.
so please help me solve this
Fixed by @hainguyenthao
Thank you so much
Same issue on my side
JimZiii said:
Fixed by @hainguyenthao
Thank you so much
Click to expand...
Click to collapse
Can you tell me how you have fixed that issue?
Rgds
Bob
I can't flash my Samsung A320 (A3 23017) with the original firmware usin Odin. I previously did the flash, but now Odin fails with the exact firmware I used before. I rooted the device with TWRP to rid some bloatware before and now my second attempt to flash fails. Any suggestions? Thanks
Here's the log:
<ID:0/006> 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/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4296 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PS: I tried both clean and partial flash.
version of binary must be same or upper
A320FLXXS9CTK2 - binary 9