PDA: MK6
PHONE: MK6
CSC: ML1 (BOG)
My GT-I9300 was updated to 4.3 around 3 to 4 weeks ago using the OTA update. Three days ago it suddenly turned off by itself and got stuck at the samsung boot logo.
Whenever i attempt to access the recovery mode i get errors can't mount /efs (file or directory not found) and same error for the cache folder. So the only accessible mode is the download mode:
ODIN MODE
PRODUCT NAME : GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
So far i tried to flash the same stock rom (I9300XXUGMK6_I9300BOGGML1_.tar.md5) using odin versions (3.09, 3.07, 3.04, 1.85) and they all fail with the following message:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Kies emergency recovery also fails. I tried different PCs, usb cables, with or without samsung usb drivers....
Any help will be really appreciated
roger8 said:
PDA: MK6
PHONE: MK6
CSC: ML1 (BOG)
My GT-I9300 was updated to 4.3 around 3 to 4 weeks ago using the OTA update. Three days ago it suddenly turned off by itself and got stuck at the samsung boot logo.
Whenever i attempt to access the recovery mode i get errors can't mount /efs (file or directory not found) and same error for the cache folder. So the only accessible mode is the download mode:
ODIN MODE
PRODUCT NAME : GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
So far i tried to flash the same stock rom (I9300XXUGMK6_I9300BOGGML1_.tar.md5) using odin versions (3.09, 3.07, 3.04, 1.85) and they all fail with the following message:
Kies emergency recovery also fails. I tried different PCs, usb cables, with or without samsung usb drivers....
Any help will be really appreciated
Click to expand...
Click to collapse
I know you don't want to here this but a Nand write fail usually means you need a new motherboard you could try this but it's not looking good >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
Related
Hi! A newbie here.
I wanted to flash ics rom over 2.3.4(device is rooted(superoneclick)).
I downloaded rom manager via market, tried getting into CWrecovery, however got this message: E:"Failed to verify whole-file signature".
I read somewhere that I need to flash "PDA" with a .tar via Odin in order for CWR to work. So I downloaded the tar mentioned on the site, then began flashing, with the following results:
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now, when I turn my phone on it says: "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again."
Kies can not recognize the phone, however, Odin can, and pc does the connected beep when device is reconnected.
Is there a way for me to fix my phone, or did I just made a brick out of it?
Flash back to the stock from and then retry. That's what I did for my very first from too.
Send from my G2X!
I apologize humbly for my n00bishness, but how do I do that exactly?
c0rk7 said:
I apologize humbly for my n00bishness, but how do I do that exactly?
Click to expand...
Click to collapse
Here is the link:http://forum.xda-developers.com/showthread.php?t=1075278
http://forum.xda-developers.com/showthread.php?t=1113928
i can see the stock roms here, but none of them matches my region.
I downloaded a rom, device is in download mode.
looks like it's frozen, it's like that on the pic for 20 minutes now.
on the phone:
Odin mode
Product name: GT-i9100
Custom binary download: YES (3 counts)
Current binary: CUSTOM
Downloading..
Do not turn off target!!
What to do?
Turn off battery, remove battery, reattach battrry, then peepare odin, once odin detected, press start
Rom : MIUI ICS XGT 'EXTENDED'
Kernel : Xcell-69X
Modem : XXKP8
Sent from Galaxy SII
c0rk7 said:
I downloaded a rom, device is in download mode.
looks like it's frozen, it's like that on the pic for 20 minutes now.
on the phone:
Odin mode
Product name: GT-i9100
Custom binary download: YES (3 counts)
Current binary: CUSTOM
Downloading..
Do not turn off target!!
What to do?
Click to expand...
Click to collapse
Retry.
Try a different usb port and different usb cable.
I downloaded a different rom, rooted with cwm, made a backup, copied cooked rom next to backup, restored rom via cwm.
working like a charm, thank you everyone.
I own a Orange Samsung S2 i9100 handset. This was working without problem until this morning where it was stuck on bootscreen. Recovery mode does not work.
I tried to update firmware using Odin 3.07 however this does not work. It fails to install.
I am now stuck with the message "Firmware upgrade encountered an error".
I cannot access SD card so rooting etc seems unlikely.
Any ideas?
Win 8 Machine
i9100
ORA-I9100XWLSY-20130606160421
Check out @Hopper8 thread about odin :thumbup:
Thanks.
I assume you are referring to this thread ( [GUIDE][Troubleshoot a failed Odin flash] )?
http://forum.xda-developers.com/showthread.php?t=2345831
I have tried recovering with the two most applicable firmware packages below. I do not know what others to try. I don't think I can use custom packages as I cannot access my SD Card?
http://www.sammobile.com/firmwares/2/
GT-I9100 Galaxy S II
PDA: I9100XWLSY
CSC: I9100ORALS8
MODEM: I9100BVLS4
Added: 2013-06-05
GT-I9100 Galaxy S II
PDA: I9100XWLSW
CSC: I9100XEULS5
MODEM: I9100XXMS2
Added: 2013-05-29
Odin does recognize my phone but each PDA update fails... Kies is installed but not running. Phone still can only go download mode and due to failed Odin update now shows no boot screen (only firmware fail message). I cnanot restore on Kies as did not use this PC before with phone.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSY_I9100BVLS4_I9100ORALS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.. *** At this point I click start
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
andrewwright said:
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
Click to expand...
Click to collapse
I have tried philz recovery steps however this also fails in Odin.
I have tried different usb ports and reinstalling drivers. However Odin can see the phone, so it may not be a USB driver/port issue.
The biggest hurdle is getting Odin to run the flash.
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Original cable used? Have you read and tried all of whats in that thread?
andrewwright said:
Original cable used? Have you read and tried all of whats in that thread?
Click to expand...
Click to collapse
Original Samsung Cable.
Followed instructions in this thread using md5 files for i900?
http://forum.xda-developers.com/showthread.php?t=2201860
Odin packages instructions: Samsung Only
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
to remove yellow triangle, use TriangleAway
Click to expand...
Click to collapse
Whatever I do, Odin still seems to fall over at same place.
What do I need to perform a full factory reset? I take it use Odin to install firmware?
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Sent from a galaxy far, far away
Hopper8 said:
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Click to expand...
Click to collapse
This doesn't work. I have assumed from your suggestion that I use Odin to install firmware via Odin. This fails as well.
I now have a new SD Card I could use to load any software onto the device. However I can not get to the recovery mode screen at all (only download mode). Therefore have no idea what to do now!
I also think my phone is worse now - on download mode screen:
ODIN MODE
PRODUCT NAME: GT-I9100
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: CUSTOM
Click to expand...
Click to collapse
What guide should I use to completely factory reset the phone?
How do I check if the phone memory is correctly partitioned?
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
dmuk said:
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
Click to expand...
Click to collapse
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
niksyspidy said:
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
Click to expand...
Click to collapse
What version? I have tried 1.85, 1.87, 3.04, 3.07 - all fail.
Can I use Kies to repair if I have not previous Kies backups?
I have searched threads here as well as other places and have had no success.
Device: Verizon Samsung Galaxy S3 (SCH-I535)
Info: Stock, non-root and no ROMS
Current firmware: KitKat 4.4.2
I was trying to use Odin 3.09 to revert to the firmware version 4.1.2 (which I got from http://www.sammobile.com/firmwares/) in order to install CM 11. I entered the phone into download mode and entered the 4.1.2 firmware file. Everything loaded and connected fine. I clicked Start and it stopped at aboot.mbn and failed because I think 4.4.2 has a locked bootloader. I also think I tripped the Knox Security flag and therefore it is now softbricked. The phone can still go into Download mode but not recovery mode.
I followed two guides to unbrick it:
1) http://forum.xda-developers.com/showthread.php?t=2581166
The microSD card method did not work. I have not tried JTAG.
2) http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Odin once again fails and cannot flash the VRALEC.bootchain.tar.md5 file, leaving the same error as before:
HTML:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This error appears on my phone:
HTML:
SW REV CHECK FAIL: Fused 2 > Binary 0
What can I do now?
scorpadorp said:
What can I do now?
Click to expand...
Click to collapse
you could post your question in the correct forum http://forum.xda-developers.com/galaxy-s3-verizon
this here is i9300 international forum, so probably no one can help, espacially because i9300 has no knox.
scorpadorp said:
I have searched threads here as well as other places and have had no success.
Device: Verizon Samsung Galaxy S3 (SCH-I535)
Info: Stock, non-root and no ROMS
Current firmware: KitKat 4.4.2
I was trying to use Odin 3.09 to revert to the firmware version 4.1.2 (which I got from http://www.sammobile.com/firmwares/) in order to install CM 11. I entered the phone into download mode and entered the 4.1.2 firmware file. Everything loaded and connected fine. I clicked Start and it stopped at aboot.mbn and failed because I think 4.4.2 has a locked bootloader. I also think I tripped the Knox Security flag and therefore it is now softbricked. The phone can still go into Download mode but not recovery mode.
I followed two guides to unbrick it:
1) http://forum.xda-developers.com/showthread.php?t=2581166
The microSD card method did not work. I have not tried JTAG.
2) http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Odin once again fails and cannot flash the VRALEC.bootchain.tar.md5 file, leaving the same error as before:
HTML:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This error appears on my phone:
HTML:
SW REV CHECK FAIL: Fused 2 > Binary 0
What can I do now?
Click to expand...
Click to collapse
I know my post maybe can't help you but I has the same problem with a Samsung Galaxy Mini 2 and I go to a SAMSUNG service and they resolved me. And I think this brick is because any Samsung device is not able to downgrade to an old version...
Read this about downgrade:
http://forum.xda-developers.com/showthread.php?t=2613745&page=2
[SOLVED]EDIT:
Here is how I solved the problem. I a xda thread I found a similar problem and someone claiming this:
-Downloaded stock firmware and extracted files
-removed .md5 off the end and extracted it again
-inside should be boot.img cache.img recovery.img system.img etc.
-used Unified Android Toolkit to create individual flashable files of each file
-flashed them in the order they came
-everything passed
Click to expand...
Click to collapse
So I tried it, and it worked till the last .tar with the system.img in it. Here I had to switch USB cables from the original Samsung one to my Usb cabel from the Amazon Fire Stick. And then it also worked. For the flashing I used Odin 3.10.6 and the firmware was the G925FXXU2COH2 one. I deactivated Auto-reboot in Odin and after flashing each file I manually restarted the phone to Download mode by holding Vol down + Home + Power.
/[SOLVED]Edit
Hey guys,
this is my current situation: Phone is stuck in cyan screen with "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". I can't use Smart Switch because I was rooted and on "XtreStoLite Deo-Mod Edition 2.3" when the phone bricked. ODIN does recognize the phone. I used Odin3 v3.10.6.
What I did to brick it:
- Downloaded a firmware and tried to flash it to unroot the phone, following that guide
http://forum.xda-developers.com/galaxy-s6/general/how-to-unroot-unbrick-galaxy-s6-t3110608
Model SM-G925F
Model name GALAXY S6 Edge
Country Germany
Version Android 5.1.1
Changelist 5599585
Build date Wed, 12 Aug 2015 08:11:31 +0000
Product code DBT
PDA G925FXXU2COH2
CSC G925FDBT2COH3
Click to expand...
Click to collapse
Since I was on "XtreStoLite Deo-Mod Edition 2.3" the device had the XXU2COH2 BL and stuff (I guessed)
- ODIN failed directly after NAND Write Start!!
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I tried to fix the problem:
- Flashing TWRP form http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866 --> Fails
-Flashing G925FXXU2COH2 stock firmware and G925FXXU2BOGB_G925FDBT2BOG8_DBT (from http://stockroms.net/file/GalaxyS6Edge/SM-G925F/Germany/5.1.1/G925FXXU2BOGB_G925FDBT2BOG8_DBT.zip)
- After finding this http://forum.xda-developers.com/galaxy-s6-edge/help/guide-s6-edge-unbrick-guide-t3187655 and some other threads I removed the hidden.img from both firmwares I already tried, repacked them and flashed with ODIN.
---> modified G925FXXU2BOGB_G925FDBT2BOG8_DBT fails after flashing modem
----> modified G925FXXU2COH2 fails like this:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Sooo.. according to the guide I mentionied I would need to flash pit and Stock firmware at once like this:
1) Get your device to download mode by using this combo "VolumeDown-Home-Power"
2) Open an UP TO DATE ODIN.
3) Find the corresponding .PIT file for your S6 EDGE.
4) Find the corresponding stock rom for your S6 EDGE.
5) Then put them into odin CORRECTLY. Rom to "AP", .pit to PIT
6) Make Sure these are checked: "Re-partition","NAND all erase"
7) Plug your device in and then press start.
Click to expand...
Click to collapse
But I am not sure if this is the right thing to do. Also I don't know which of the provided pits for the SM-G925F I am supposed to use? http://forum.xda-developers.com/gal...925-pit-files-multi-thread-download-t3171636/ Whats the difference between them? Aaaand I'm still not sure which firmware I should be flashing
I would really appriciate your help..
Small update:
Found this suggestion on reddit and tried it
If you've tried to flash firmware off of Sammobile, and had your heart stop when the flash fails, fear no longer.
To fix the soft brick:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
After flashing the hidden.img.tar I was stuck on the Samsung Logo (before the bootanimation) but I could boot into normal Downloading mode. Tried flashing the stock firmware without the hidden.img and got
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And I'm back to the screen saying I should use Smart Switch..
Well I again flashed the hidden.img.tar, then I could get in TWRP. I did restore on old backup and did a factory reset. The phone booted! So I dicided to try the unroot one more time. I was on kind a funny Baseband-Version so I decided to flash COH2 Bootloader and Modem, but Odin right after starting the NAND write and I was stuck on the Error massage from the beginning..
Flashed hidden.img.tar and the phone booted normaly.
What is going on? What do I need to flash or do to get back to stock?
In the device information I now have:
Modell: SM-G925F
Android-Version: 5.1.1
Basebandversion: G925FXXU2BOGE
Kernel-version: 3,10,61-Alex-V_1.2
Buildnumber: XtreStoLite Deo Mod v.2.3 - XXU2COH2
It is really kind of mixed up and I have know idea why I can't just flash with ODIN.
Worked for me but with very minor tweak
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Stuk in bootloop
spencersj said:
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Click to expand...
Click to collapse
After flashing boot.tar my phone is stuck in bootloop and nt coming out despite hard reset also and i m also unable to flash new fw via odin.
plz help.
it states SOLVED.....???
Hi!
Here my story.
Flashing "cm-12.1-20151016-UNOFFICIAL-temasek-i9300-V18.0-ds94-FIXED.zip" (Android 5.1.1) and running smooth for 2 days. Recharing battery overnight causing bootloop.
I tried numerous attempts to regain access with odin, however no success.
TRG-I9300XXUGOC1-20150715205218
CF-Auto-Root-m0-m0xx-gti9300
different pit files etc.
Fresh samsung usb driver
Click to expand...
Click to collapse
Product name: GT-I9300
Custom Binary Download: Yes(2 counts)
Current Binary: Custom
System Status: Custom
Click to expand...
Click to collapse
As i understand this means NO emmc failure.
Odin different files 1.85, 3.04, 3.07, 3.10.7
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Gave phone to 2 different mobile stores -> no success.
Is emmc dead?
Any special tricks fix?
greets
Fluffz
Will your device accept a btu stock rom?. I can give you a link if you want to try my stuff..
I wish I stole my HTC M9.
ok, gimme link.
whats about hard brick sd card recovery bootloader?
http://forum.xda-developers.com/showthread.php?t=2581166
i have same working s3 on android 5.1.1 -> one idea is to safe working bootloader to sd card and flash the bricked phone.
I found out that "cm-12.1-20151016-UNOFFICIAL-temasek-i9300-V18.0-ds94-FIXED.zip"
using 4.1.2 bootloader (i9300xxemc2) which can cause bootloop on i9300.
Another i9300 with stock firmware using i9300xxugna8 with bootloader 4.3 should avoid bootloop, however forbid downgrade to earlier versions.
Based on this information, anyway to debrick phone without replacing emmc?
greets