S4 mini keeps restarting - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<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.1203)..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Hello razvanells. Sorry for taking advantage of your topic, but I'm having the same problem as you.
This also happened with the S4 Mini (but I9192 version) of a my friend. This device had no root and had a stock rom. He hung up and did not turn on anymore, locking on the screen Samsung Galaxy S4 Mini I9192. I downloaded the stock rom from the sammobile site and installed it by Odin. The log I received was identical to yours, saying that the installation occurred successfully, but when the device reboots it goes to recovery mode and it does not start, I can only enter the download or recovery mode.
I tried the hard reset and received the following error:
Formatting / data ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formating / cache ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete.
Click to expand...
Click to collapse
I tried to recover the stock rom using Kies but it did not work either.
After a lot of research on google, I found a guy saying he was able to recover a smartphone using TWRP and formatting the memory in FAT and then reformatting it to EXT4 (at that link: http://forums.androidcentral.com/t-...850-encrypted-phone-freezes-when-turning.html).
I tried to install TWRP by Odin, which according to the log occurred perfectly, but after restarting the device the Android default recovery was there (even entering the recovery mode as soon as the phone rebooted).
I tried to install the CWM for Odin, and so it was. Odin's log said it was successful but when the phone was rebooted there was the default Android recovery again (even entering the recovery mode as soon as the phone rebooted).
I have no more ideas, and I wanted to ask if anyone knows how to solve this?
Thank you.

razvanells said:
Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<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.1203)..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
même problème que vous

Related

[Q] Firmware upgrade encountered an issue, Please select recovery mode in Kies

Folks,
Can you please help me on my Samsung Tab 3 SM-T210, I've been trying to fix it for days now the steps that I have done is flashing it to a stock rom T210XXAMG7_T210XSAAMG1_T210XXAMG7_HOME.tar.md5 using odin v3.07 I followed all the steps that I found on the internet and nothing happens it shows PASS! in odin though. I think the problem maybe is I can't get the device into the download mode, tried holding power volume up and home button all at the same time and it goes right back to the firmware upgrade encountered an error.
ODIN MODE
PRODUCT NAME: SM-T210
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210XXAMG7_T210XSAAMG1_T210XXAMG7_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> PBL.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> NVM.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> PBL.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> NVM.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
If you have further insight please let me know.
Thanks,
BesterEM
you must repair ur tab with jtag z3x or other emmc box...so ur boot emmc is corupted and u must repair it

[2015] ODIN failed flashes reflashing STOCK 4.4.2 - Please HELP :'(

Hi there!
I recently bought a N3N (N7505) :good: for mobile drawing. Since I bought it used, I found KNOX at 0x1 and the 4.4.2 it came with was already annoyingly buggy (lags everywhere, packed RAM & phone app FCs). I did manage to root it through CF-Autoroot (I think?) and even put a custom recovery (TWRP touch v2.8.7.0)
The problem is, everytime I download a ROM from Sammobile (md5 checks confirm undamaged downloads), it fails to flash via ODIN (flashes ALL THE WAY till the end and says FAILED - phone reboots perfectly to previous OS like nothing happened) and I'm wondering if I downloaded the wrong ODIN files, or is there something I'm missing?
So, i'm currently on N7505XXUCNL1 and wondering how I can reflash it (or a similar one) to refresh the phone anew :angel:
ROMz, Y U NO FLASH???
Any advice on what ROM would best suit me to refresh my N3N with???
:victory::victory::victory:Thanks in advance!!:victory::victory::victory:
UPDATE:
When i'm in Download mode, this is the information displayed
ODIN MODE
PRODUCT NAME: SM-N7505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
AP SWREV: (2)
The ODIN log for when I try to flash N7505XXUCNL1_N7505OXXCNL1_TPH is here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The ODIN log for N7505XXUCOE1_N7505SWCCOF1_SWC is here:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I'm stuck on the Firmware update encountered an issue. Please select recovery mode in Kies and try again
can you provide us the log?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
The ODIN failed flash log??
Where do I find that?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
Greetings damadikaz,
I have posted my ODIN logs as an UPDATE on the main post for two separate flashes that both failed.
Any help is greatly appreciated:highfive::highfive::highfive:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
audit13 said:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
Click to expand...
Click to collapse
Oh WOW!!! It could be!
Thank you very much:laugh:
Going to download tonight and flash :good::good::good:
Will return with feedback!
Thanks again good sir! :highfive::highfive::highfive:

FAIL! flashing stock fiirmware 5.0.2, sm-t805 with odin 3.10

hi guys
i flashed stock firmware but odin failed midway... tab s shows the yellow triangle and "encountering an issue". i couldnt recover with kies. it also fails.
there's odin's log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i can access download mode. i can't download another rom cuz it took a week to download this one!! anyone can help me?
This is common when you flash a firmware not for your region. Easy fix, just boot to recovery and wipe cache then reboot. Everything should be fine after that.

[URGENT] I think I have brick my set.

Hello XDA, Thank you very much.
So I have a Note 2 (N7100) 3G version running on CM12 (6.0.1) not recently flashed, I have been using for a month or 2 now. Everything seemed great and all.
Until, Last night I had a bit load on my phone, running 3G + Wifi Mobile Hotspot + GAME, and usual (Yeah, it was bad of me :3) suddenly my phones crashes and goes in boot loop. Next thing i did, went into recovery wipe all, reboot, but still boot loop. I then flashed the same ROM I did before (6.0.1) CM12 thinking maybe a fresh flash will work this, but still no luck, rather I was stuck with "patching system image unconditionally" and then verifying something which took forever so i had to pull battery. Now, I need help, Please suggest something. I can still access Recovery.
Regards,
Khurry!
as suggested by one the member here, I downloaded latest firmware from SAM and flashed using ODIN. Logs here
<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..
<ID:0/004> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Still im boot loop. Any suggestion?
Did you perform a factory wipe before booting the newly- flashed rom for the first time?

GT-7100 stuck on samsung logo

Hi,
I woke up this morning and found my phone stuck on the startup logo.
I tried removing the battery and wipe the cache but it won't go past the start up logo.
I don't care about the phone, I wanted to change it anyway but I would like to retrieve some data before. So I haven't try the factory reset yet. Is there a way to save some data ? (my contacts and some data from note everything and task list mainly).
I afraid to try something and wipe all my data.....
Note : when I go to recovery, It says "failed to mount /efs (no such file or directory)... failed to mount /system ......"
Flash TWRP using Odin. Then boot into TWRP, mount the data partition, connect the phone to a computer, and copy off the data files. Hopefully, this method works for the phone.
You mean I have to install TWRP (? Team win recovery project) on my phone using Odin ? Is that correct and then start the phone with TWRP ?
Does my phone need to be rooted for that ? (it's not).
I haven't use odin or TWRP yet but I will try and tell you if that works.
Any advice for how to use Odin and TWRP for a beginner ?
Thanks
So after making a few more research to understand how to use odin et twrp, I tried to flash twrp using odin but it failed. Here is my log :
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so what do I do now ?
Use the tar version of TWRP, not the IMG version.
I used this file : twrp-3.0.2-0-t03g.img.tar so it should be right
So I finally tried to wipe the data from recovery mode and it didn't work.
Tried to reload the firmware using odin (N7100XXUFOC2_N7100OXAFOC2_N7100XXUFNG1_HOME.tar.md5) and got this :
<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..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something else I can do or is this a hardware problem ?
The sboot.bin file is the bootloader for the phone and could be failing due to the following reasons:
the ROM is not for the phone;
need to use a different USB cable and/or different USB 2.0 ports;
the bootloader in the phone is newer than the bootloader in the ROM;
the ROM needs to be flashed with a pit file;
the memory chip is damaged.

Categories

Resources