Galaxy S4 Mini I9195- Stuck In Bootloop

baibars · Mar 21, 2013 3 0 0

Bootloop - S4 mini I9195

Hello,

at first i apologize if i posted in the wrong place.

My phone is since a week in a bootloop. It boots to the samsung logo an ends there. It happened suddenly. I never changed something on this phone. So im surprised i saw that my knox counter is 00x01 as i tried to flash some firmware to repair the phone. It is unrooted and no cumstom rom flashed.

I tried different methods and tips from this forum and others.

I tried to flash with Odin some firmware. Even with pit files and Bootloader files the same result. The phone is still in a bootloop.

I really need your help. It makes me crazy.
Thank you for some tips and Help.

Sorry for my bad english.

RuffBuster · Sep 18, 2015 at 12:43 AM

What model of s4 Mini are using i9190 i9192 i9195 or the new i9195"L"? What version of firmware have you tried? It's strange that flashing firmware thru Odin tripped Knox... Unless you flashed a version needn't for another phone. You say this happened all of a sudden? Maybe your internal memory corrupted... Maybe. I'm guessing you were fully stock with no root before this happened? How old is your phone? Sometimes it's a matter of flashing the "correct" firmware. Where did you get your firmware from?

baibars · Mar 21, 2013 3 0 0

I9195.
I downloaded some firmwares from sammobiles. At first i tried the german DBT version I9195XXUCOE4. After that some older german firmwares. Then some files from this forum and others. But no result. Its really strange. The phone is 2 years old. Not rooted or changed something. Original software.

baibars · Mar 21, 2013 3 0 0

Nobody has an idea??

Davidich · Sep 20, 2015 at 10:02 PM

Do a factory reser/wipe cache and davlik if you have a custom recovery or try flash a custom recovery with odin,then flash a stock deodexed rom from the recovery.

RuffBuster · Sep 21, 2015 at 1:04 AM

It more sounds like a corrupt memory problem if it just happened out the blue using an unmodded phone... I have a feeling that the mini version got given some cheap memory chips... Since owning this phone I've seen a few devices on different forums just give up... It's a shame your over the 2 year warranty.

Maybe try the debloated stock version "scStock" using a custom recovery mentioned above.

I use CWM 6.0.5.1 and scStock coc2 with good results. I also use SilviuMik kernel, not sure that will make the difference though.

I once had a corrupt memory on my Galaxy S1 and luckily someone had made a custom kernel which allowed me to use my external SD card as internal memory but limited me to using old Android ginger bread. Unfortunately I've not seen anything similar here. That mod was found on htcmania forums ... Maybe that dev can do the same for you ... Maybe

Though if stock firmware doesn't fix your problem it may mean you have a serious problem...

In the end I bought a cheap broken phone with working internals from eBay and swapped out those parts for my broken phone to fix my S1..

Sanesh Munde · Sep 22, 2015 at 9:55 AM

Can your phone boot in download mode; if yes then try one click unbrick method. Get it here http://forum.xda-developers.com/showthread.php?p=15330252#post15330252

nknwn666 · Nov 23, 2013 56 7 0

I have a similar problem if not the same, same phone (mine is black edition and running 4.4.2), can boot into Download Mode and Recovery but normal boot just shows samsung text then black screen and after 2 vibrations it shows samsung text again.
Phone was stock, no root and just one day it started boot looping. As OP, i tried using odin to flash stock from sammobile. Phone is from Romania so i tried all ROMs from Romania. It succedes flashing but booting to recovery it shows:

Code:

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : SER
did not match sized '/system/csc/common/system/csc/default_application_order.xml'(No data available)

From sammobile, SER is for Russian ROMs, tried all Romanian ROMs then tried Russian and still stuck in boot loop.
Trying to wipe from recovery, i get:

Code:

E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata (or cache for cache wipe)

Tried installing a different recovery with odin and it still boots in the stock one.
That unbrick method just fails while i'm in Download Mode, connecting to pc while turned off will just charge the phone and turning it on will just boot loop.

Sanesh Munde · Sep 23, 2015 at 1:43 PM

@nknwn666
Try this.
First download cwm for your phone. Open Odin and uncheck auto-reboot in it. Now boot in download mode and connect to pc. Flash cwm. After flashing remove battery from your phone and wait for one minute. Now insert battery and boot in recovery mode. If this works try to flash custom rom.

nknwn666 · Nov 23, 2013 56 7 0

@Sanesh Munde
Still booting in stock recovery.

Sanesh Munde · Sep 23, 2015 at 7:17 PM

nknwn666 said:
@Sanesh Munde
Still booting in stock recovery.

Flash silviumik custom kernel from Odin.

nknwn666 · Nov 23, 2013 56 7 0

Same thing. Bootloop and stock recovery, tried flashing kernel without rebooting, reinserted battery and flashed recovery but still stock.

Sanesh Munde · Sep 24, 2015 at 4:50 PM

nknwn666 said:
Same thing. Bootloop and stock recovery, tried flashing kernel without rebooting, reinserted battery and flashed recovery but still stock.

May be this help.
Download minimal adb and fastboot from here http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
Now put it's folder on desktop. Copy cwm image file in folder containing minimal adb and fastboot. Now open that folder and open command prompt there. Type ' adb boot recovery.img ' where recovery.img is your recovery file name and enter. This will boot phone in custom recovery mode. If this success try to flash custom rom.

nknwn666 · Nov 23, 2013 56 7 0

ADB cannot find the phone, works with another phone of mine.

Sanesh Munde · Sep 25, 2015 at 11:21 AM

nknwn666 said:
ADB cannot find the phone, works with another phone of mine.

It seems that emmc memory of phone gets correpted. You should take help of jtag professionals.

rushwhq · Apr 6, 2008 49 0 0

Hi all

Mine cant enter in download mode... what should i do? tried to load some firmware via adb but still in samsung bootloop

hahoki · Sep 29, 2016 2 0 0

Sanesh Munde said:
It seems that emmc memory of phone gets correpted. You should take help of jtag professionals.

Hello, I hope it's OK to jump in here as well.
Not knowing very much about these things I might have exactly the above mentioned problem (corrupted memory) on my S4-iGT9195.
After many attempts with many different "specialists" I have come this far after flashing with Odin:

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9195XXUCNH5_2659908_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> BL_I9195XXUCNH5_2659908_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> CP_I9195XXUCNH5_2659908_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_OJV_I9195OJVCNH1_2502401_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> persdata.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
I do not understand that I am first being told ID:0/005 ADDED and at the end its been REMOVED!!! Can anybody please give me an idea what it means and/or confirm that this simply means memory defect? Or have I done a mistake/missed something?
Thank you for your assisstance!!!

---------- Post added at 12:55 PM ---------- Previous post was at 12:43 PM ----------

Sorry, I failed to mention that I can boot into the download mode and into recovery booting with "Set Warranty Bit: recovery." Once it's there the phone vibrates twice and goes back into "could not do normal boot etc."
Product Name : GT-i9195, Current Binary: Samsung Official, System Status: Official, Knox Kernel Lock: 0x0, Knox Warranty Void: 0x1, CSB-Config-LSB: 0x30
and grey: Bootloader AP SWAEV: 2, Write Protection: Enable.
Hope that helps? Thank you!

hahoki · Sep 29, 2016 2 0 0

Appology

Appology to baibars for having killed his thread, didn't mean to!:crying::crying::crying:

GuestD0931 · Mar 17, 2019 at 5:10 AM

My phone getting exactly same error with yours. Did you solve it?

Galaxy S4 Mini I9195- Stuck In Bootloop

New member

Senior Member

New member

New member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

New member

New member

GuestD0931

Guest