Related
The initial problem
My i9023 got totally bricked after restoring it to factory defaults. As soon as I changed the SIM card and tried to power the phone up, it just wouldn't do anything; the display wouldn't turn on (neither while charging), no vibration, no light on the touch keys, nothing.
The inspirers
I found the posts by AdamOutler about the Unbrickable Mod and the Unbrickable Resurrector, plus a nice thread started by cyberalex88 on how he unbricked his Nexus S.
Current situation
Starting from what it is mentioned on the threads mentioned above, I performed the Unbrickable Mod with the help of a friend last Monday, and now the phone is detected by the Unbrickable Resurrector, but I cannot get it to work again.
The Unbrickable Resurrector interacts with the phone somehow ("S5PC110 detected") and seems to enable the Download Mode, but it is not working as I think it should.
My diagnosis
I think that the partition table of the phone is broken, but there might also be a problem with the resurrection. I've spent a good time finding information, but still I haven't been able to find a way to fix the issue. I do not how to proceed anymore.
Working environment
I've been using a dual boot PC, with Ubuntu 13.04 64bit and Windows 7, trying both Odin 1.83 and Heimdall 1.4.0 (from Ubuntu) to flash the original firmware (I9023_EUR_GRI54_XXKB3) downloaded from samfirmware.
Using The Unbrickable Resurrector
After launching the Unbrickable Resurrector, inserting the battery to the phone and plugin the usb to the Linux machine, the Resurrector detects my phone. From that starting point, I've been able to enable the "Download Mode" (search and home buttons lighted on) in the phone in two different ways:
Selecting Nexus S as Device type
After selecting "Nexus S" and performing the resurrection, the phone enters on what it should be the "Download Mode" (search and home buttons lighted on), but then it is not detected by Heimdall.
Code:
[email protected]:~#heimdall detect
ERROR: Failed to detect compatible download-mode device.
I don't know if it's related with this, but the Resurrector does not show the "Download Mode" photo on top of the window after resurrecting.
This is the log from the resurrection:
Code:
Building command list
#S5PC110 (Nexus S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: nexus_sbl.bin LOCATION:0x33040000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button while holding button combination
5. Download new software with fastboot for Linux.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 031
=> loaded 24576 bytes from /tmp/TempHeimdallOneClickA2EFF4DC/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 032
=> loaded 1310720 bytes from /tmp/TempHeimdallOneClickA2EFF4DC/UnBrickPack/nexus_sbl.bin
=> Downloading 1310730 bytes to 0x33040000
=> Data checksum 6106
=> usb_bulk_write() returned 1310730
Modified SBL Injection Completed Download Mode Activated
Selecting Galaxy S as Device type
Since the Heimdall message got me worried, I tried to resurrect the phone selecting the other two device types, and it seems that it gets to "Download Mode" (search and home buttons lighted on) as "Galaxy S". As Galaxy S, after the resurrection, and unlike as Nexus S, the window shows the Download Mode photo on the top part and Heimdall detects the phone:
Code:
[email protected]:~#heimdall detect
Device detected
This is the log from the resurrection:
Code:
Building command list
#S5PC110 (Galaxy S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: Sbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 033
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick9ECA7A24/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 034
=> loaded 1310720 bytes from /tmp/TempHeimdallOneClick9ECA7A24/UnBrickPack/Sbl.bin
=> Downloading 1310730 bytes to 0x40244000
=> Data checksum f37e
=> usb_bulk_write() returned 1310730
Modified SBL Injection Completed Download Mode Activated
Using Heimdall
Since Heimdall wouldn't detect the phone unless resurrecting as Galaxy S, I proceeded from that resurrection. The first thing I tried was to flash the original rom, but since I got an error message related with the phone's pit file, I focused on getting the pit file from the phone.
This is the output of the "print-pit" argument:
Code:
[email protected]:~#heimdall print-pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So, Heimdall is not able to get the PIT file from the phone, but it does reboot the device since the search and home buttons are turned off after launching the command. So there is some kind of communication.
Guessing that the partition table of the phone might be corrupted, I found a pit file that it is supposed to be for the device (u1_02_20110310_emmc_EXT4.pit), and launched the following Heimdall command trying to repartition the phone:
Code:
[email protected]:~#heimdall flash --repartition --pit u1_02_20110310_emmc_EXT4.pit --BOOT boot.img --SBL1 bootloader.img --RECOVERY recovery.img --FACTORYFS system.img --DATAFS userdata.img --MODEM modem.img --CACHE dgs.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Using Odin
Since I had no luck with Heimdall, I installed Windows 7 on my Linux machine and rebooted to Windows after the resurrection in both modes of operation (Nexus S and Galaxy S) to try Odin. The result was the same in both cases, the device was not detected and the program only checks if the rom files are correct.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Bootloader_I9023XXKA3.tar.md5 is valid.
<OSM> PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is valid.
<OSM> MODEM_I9023XXKB3_REV_00_CL912571_SIGNED.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I installed the Samsung USB drivers before using ODIN and plugging in the phone, so I don't think that the fact that the phone is not being detected by Odin has nothing to do with the computer itself.
Call for help
I've tried everything in my hands to try to unbrick the phone with no luck. I don't usually seek for help on the forums, but I see no other choice.
Does anyone have any clue on what to do in order to unbrick the phone?
Have you tried fastboot?
Yes. It does not detect the device.
AdamOutler said:
Have you tried fastboot?
Click to expand...
Click to collapse
unai_goiko said:
Yes. It does not detect the device.
Click to expand...
Click to collapse
Try it again, but hold the key combination.
We don't force the Nexus into Fastboot mode. you could boot it into Odin, Fastboot, or Recovery mode using this tool.
I did try the key combination ( power and volume up), and since it wouldn't work, I also tried others (power and volume down, and power and both volume buttons). Is there any other way to try to get into that mode?
AdamOutler said:
Try it again, but hold the key combination.
Click to expand...
Click to collapse
I'm sitting here with this exact problem. Anymore insight?
Adsmji said:
I'm sitting here with this exact problem. Anymore insight?
Click to expand...
Click to collapse
I had the same problem as the OP. Can enter download mode just fine (thanks to Unbrickable Mod), but fails to print PIT or flash anything. I think the flash is fried, that would explain the problem. The phone however can still be used as a S5PC110 development platform so it's not completely useless.
Adsmji said:
I'm sitting here with this exact problem. Anymore insight?
Click to expand...
Click to collapse
I'm afraid I wasn't able to find a solution and that I gave up. I still have the phone, but i haven't tried to fix it again...
xd.bx said:
I had the same problem as the OP. Can enter download mode just fine (thanks to Unbrickable Mod), but fails to print PIT or flash anything. I think the flash is fried, that would explain the problem. The phone however can still be used as a S5PC110 development platform so it's not completely useless.
Click to expand...
Click to collapse
By the way the other choice (in the drop down menu) which is Nexus S, in theory the proper choice, did not lead to a successful fastboot mode, the phone became totally unresponsive. That's presumably because the fastboot code tries to access the flash and gets stuck at this point. Like the OP I gave up.
The reason for the brick in the first place was that I removed the battery while the phone was booting (fresh ROM just installed). I guess there were some flash writes and the sudden power removal left the flash in a bad state. So don't do this.
DISCLAIMER: You will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone, so make sure you are well informed and well prepared before deciding to flash or install anything on your device.
The purpose of this thread is to provide a 'reference site' for anything related to ROMs and kernels, be it original stock, modified stock or custom images for the Samsung Galaxy S4 LTE-A Korean versions, starting with model SHV-E330S.
All comments and feedback are welcome and appreciated.
Reminders:
After flashing a new ROM image, it is highly recommended to perform a cache wipe and factory reset. Please avoid posting about problems repeatedly which can be easily solved by this procedure.
If you find that someone has been helpful in assisting you, then please do not shy away from hitting the THANKS button below their post; this is the preferred action instead of creating a new post just to show your gratitude
Factory Firmware (stock)
samsung-updates.com and www.sammobile.com host stock images.
Devices
SHV-E330S
SHV-E330L
SHV-E330K
Manual Rooting
Rooting Guide by @xenix96
Hints & Tips
Follow this trail...
Proxyme Rooting
Proxyme Guide
Credits & Special Thanks to the following Contributors...
@dc_power!
@xenix96
SHV-E330S Page
SHV-E330S Info Page
Warning:
Do not jump in blindly and flash any stock image you 'like'. PIT files are posted here for your information and to alert you to changes in partition configurations when they are introduced in a specific stock rom release. You MUST follow stock rom upgrade paths in the order they are being released; if you skip a release which contains changes to the partition configuration, problems may arise with any later version you flash.
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
SKT 32GB Model PIT file (Partition scheme from UBMK4 onwards) ... mirror, torrent
SKT PIT file (Partition scheme from UCNB2 onwards) ... mirror, torrent
Pre Rooted stock ROMs
(Unfortunately, flashing these ROMs will trigger KNOX)
Rom images which are preloaded with Proxyme offer the following default functionality:
Default state after factory reset is - not rooted -
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
KitKat 4.4.2
E330SKSUCNJ1 (Proxyme) (Build Date 2014-10-06)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have KSUCNJ1 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included in the zip archive.
uploaded.net
mediafire
torrent, mirror2
E330SKSUCNG9 (Proxyme) (Build Date 2014-07-29)
Same notes for E330SKSUCNC4 apply here.
This package comes with an updated debloat.sh script. Delete the current/old copy, /sdcard/Proxyme/debloat.sh, and reboot the phone to refresh it
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNG9_PROXYME20140807.zip
E330SKSUCNG9_PROXYME20140807.z01
E330SKSUCNG9_PROXYME20140807.z02
E330SKSUCNG1 (Proxyme) (Build Date 2014-07-09)
Same notes for E330SKSUCNC4 apply here
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNG1_PROXYME20140716.zip
E330SKSUCNG1_PROXYME20140716.z01
E330SKSUCNG1_PROXYME20140716.z02
E330SKSUCNF3 (Proxyme) (Build Date 2014-06-23)
Same notes for E330SKSUCNC4 apply here
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNF3_PROXYME20140701.zip
E330SKSUCNF3_PROXYME20140701.z01
E330SKSUCNF3_PROXYME20140701.z02
E330SKSUCNE2 (Proxyme) (Build Date 2014-05-10)
Same notes for E330SKSUCNC4 apply here
The Samsung Chinese IME has been added to this ROM, but do NOT use it (it is buggy) and just turn it off in language settings
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNE2_PROXYME20140519.z01
E330SKSUCNE2_PROXYME20140519.zip
E330SKSUCNE2_PROXYME20140519.z03
E330SKSUCNE2_PROXYME20140519.z02
E330SKSUCNC4 (Proxyme) (Build Date 2014-03-17)
Verify that some time in the past you have flashed stock UCNB2 or a full stock UCNB2 based rom before flashing stock UCNC4 (or this derived image), because UCNB2 introduced changes to the partition configuration.
This image will not clear data, but please consider wiping data/cache manually before posting about issues not related to Proxyme
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNC4_PROXYME20140329.zip
E330SKSUCNC4_PROXYME20140329.z02
E330SKSUCNC4_PROXYME20140329.z01
E330SKSUCNB3 (Proxyme) (Build Date 2014-02-26)
Backup your stuff, this image will implicitly perform a factory reset
mega.co.nz
torrent (Proxyme), mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330SKSUCNB3_PROXYME20140308.zip
E330SKSUCNB3_PROXYME20140308.z02
E330SKSUCNB3_PROXYME20140308.z01
Jelly Bean 4.3
E330SKSUBML2 (Proxyme) (Build Date 2013-12-10) (Only for 32GB model)
Backup your stuff, this image will implicitly perform a factory reset
Display Languages: ko_KR;en_GB;en_US;bg_BG;cs_CZ;da_DK;de_DE;el_GR;es_ES;et_EE;fi_FI;fr_FR;ga_IE;hr_HR;hu_HU;in_ID;is_IS;it_IT;kk_KZ;lt_LT;lv_LV;mk_MK;ms_MY;nb_NO;nl_NL;pl_PL;pt_PT;ro_RO;ru_RU;sk_SK;sl_SI;sr_RS;sv_SE;th_TH;tr_TR;uk_UA;vi_VN;zh_CN;zh_TW;ja_JP;
Input Options: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME
torrent (Proxyme)
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
uploaded.net Part1of3 (Proxyme)
uploaded.net Part2of3 (Proxyme)
uploaded.net Part3of3 (Proxyme)
Jelly Bean 4.2.x and older
BVLGARIAN Blog
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
Chinese Bizzy Beez (You will need to handle Chinese, with or without translation tools)
Credits & Special Thanks to the following Contributors...
@dc_power!
SHV-E330K Page
SHV-E330K Info Page
Warning:
Do not jump in blindly and flash any stock image you 'like'. PIT files are posted here for your information and to alert you to changes in partition configurations when they are introduced in a specific stock rom release. You MUST follow stock rom upgrade paths in the order they are being released; if you skip a release which contains changes to the partition configuration, problems may arise with any later version you flash.
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
KTT 32GB Model PIT file (Partition scheme from MJ8 onwards) ... mirror, torrent
KTT PIT file (Partition scheme from UCNC1 onwards) ... mirror, torrent
Pre Rooted stock ROMs
(Unfortunately, flashing these ROMs will trigger KNOX)
Rom images which are preloaded with Proxyme offer the following default functionality:
Default state after factory reset is - not rooted -
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
KitKat 4.4.2
E330KKKUCNJ1 (Proxyme) (Build Date 2014-10-06)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have KKUCNJ1 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included in the zip archive.
uploaded.net
mediafire
torrent, mirror2
E330KKKUCNC4 (Build Date 2014-03-17)
Backup your stuff, this image will implicitly perform a factory reset
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330KKKUCNC4_PROXYME20140501.zip
E330KKKUCNC4_PROXYME20140501.z01
E330KKKUCNC4_PROXYME20140501.z02
E330KKKUCNC1 (Build Date 2014-03-01)
Backup your stuff, this image will implicitly perform a factory reset
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330KKKUCNC1_PROXYME20140319.zip
E330KKKUCNC1_PROXYME20140319.z01
E330KKKUCNC1_PROXYME20140319.z02
Jelly Bean 4.3
E330KKKUBML1 (Build Date 2013-12-11) (Only for 32GB model)
Backup your stuff, this image will implicitly perform a factory reset
Root toggle instructions are displayed in RootMe app
Display Languages: ko_KR;en_GB;en_US;bg_BG;cs_CZ;da_DK;de_DE;el_GR;es_ES;et_EE;fi_FI;fr_FR;ga_IE;hr_HR;hu_HU;in_ID;is_IS;it_IT;kk_KZ;lt_LT;lv_LV;mk_MK;ms_MY;nb_NO;nl_NL;pl_PL;pt_PT;ro_RO;ru_RU;sk_SK;sl_SI;sr_RS;sv_SE;th_TH;tr_TR;uk_UA;vi_VN;zh_CN;zh_TW;ja_JP;
Input Options: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
torrent
uploaded.net - E330KKKUBML1_FULL_20140103.zip (part 1), E330KKKUBML1_FULL_20140103.z01 (part 2)
Jelly Bean 4.2.x and older
BVLGARIAN Blog
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
TBD
SHV-E330L Page
SHV-E330L Info Page
Warning:
Do not jump in blindly and flash any stock image you 'like'. PIT files are posted here for your information and to alert you to changes in partition configurations when they are introduced in a specific stock rom release. You MUST follow stock rom upgrade paths in the order they are being released; if you skip a release which contains changes to the partition configuration, problems may arise with any later version you flash.
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
LGT 32GB Model PIT file (Partition scheme from MK4 onwards) ... mirror, torrent
LGT PIT file (Partition scheme from UCNB3 onwards) ..mirror, .torrent
Pre Rooted stock ROMs
(Unfortunately, flashing these ROMs will trigger KNOX)
KitKat 4.4.2
Rom images which are preloaded with Proxyme offer the following default functionality:
Default state after factory reset is - not rooted -
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
E330LKLUCNJ1 (Proxyme) (Build Date 2014-10-06)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have KLUCNJ1 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included in the zip archive.
uploaded.net
mediafire
torrent, mirror2
E330LKLUCNF2 (Build Date 2014-06-20)
The same notes for E330LKLUCNC4 apply to this image. Make sure to read them before continuing
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330LKLUCNF2_PROXYME20140717.zip
E330LKLUCNF2_PROXYME20140717.z02
E330LKLUCNF2_PROXYME20140717.z01
E330LKLUCNE2 (Build Date 2014-05-11)
The same notes for E330LKLUCNC4 apply to this image. Make sure to read them before continuing
torrent, mirror1, mirror2
mega.co.nz
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330LKLUCNE2_PROXYME20140523.z02
E330LKLUCNE2_PROXYME20140523.z01
E330LKLUCNE2_PROXYME20140523.zip
E330LKLUCNC4 (Build Date 2014-03-17)
Verify that some time in the past you have flashed stock UCNB3 or a full stock UCNB3 based rom before flashing stock UCNC4 (or this derived image), because UCNB3 introduced changes to the partition configuration.
This image will not clear data, but please consider wiping data/cache manually before posting about issues not related to Proxyme
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330LKLUCNC4_PROXYME201400330.z02
E330LKLUCNC4_PROXYME201400330.z01
E330LKLUCNC4_PROXYME201400330.zip
E330LKLUCNC2 (Build Date 2014-03-02)
If you experience problems after flashing, please try to perform a factory reset
mega.co.nz
torrent (Proxyme), mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330LKLUCNC2_PROXYME20140309.zip
E330LKLUCNC2_PROXYME20140309.z01
E330LKLUCNC2_PROXYME20140309.z02
E330LKLUCNB3 (Build Date 2014-02-20) (Update: wifi issue fixed)
Backup your stuff, this image will implicitly perform a factory reset
mega.co.nz
torrent (Proxyme), mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
E330LKLUCNB3_PROXYME20140309.zip
E330LKLUCNB3_PROXYME20140309.z02
E330LKLUCNB3_PROXYME20140309.z01
Jelly Bean 4.3
E330LKLUBMK4 (Build Date 2013-11-16) (Only for 32GB model)
Backup your stuff, this image will implicitly perform a factory reset
Root toggle instructions are displayed in RootMe app
Display Languages: ko_KR;en_GB;en_US;bg_BG;cs_CZ;da_DK;de_DE;el_GR;es_ES;et_EE;fi_FI;fr_FR;ga_IE;hr_HR;hu_HU;in_ID;is_IS;it_IT;kk_KZ;lt_LT;lv_LV;mk_MK;ms_MY;nb_NO;nl_NL;pl_PL;pt_PT;ro_RO;ru_RU;sk_SK;sl_SI;sr_RS;sv_SE;th_TH;tr_TR;uk_UA;vi_VN;zh_CN;zh_TW;ja_JP;
Input Options: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
torrent
uploaded.net - E330LKLUBMK4_32GB_FULL_RR20131231.zip (part 1), E330LKLUBMK4_32GB_FULL_RR20131231.z01 (part 2)
Jelly Bean 4.2.x and older
BVLGARIAN Blog
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
Chinese Bizzy Beez (You will need to handle Chinese, with or without translation tools)
Credits & Special Thanks to the following Contributors...
@melbournekurt16
Hints & Tips
Operator Hidden Menu Access
Using the default dialer, enter the following number:
319712358
Depending on your phone model, enter one of the following password codes:
Code:
SKT --- 996412
KT --- 774632
LG U+ --- 0821
Other Special Menus
Using the default dialer, enter the following number:
Test and Diagnostics
*#0*#
ServiceMode Signal Info
*#0011#
(Key Input Q followed by 0000 to proceed to MAIN MENU)
SysDump
*#9900#
ServiceMode DIAG CONFIG
*#9090#
Supplemental Downloads
placeholder A
Placehodler B
placeholder B
Placeholder C
placeholder C
Placeholder D
placeholder D
Placeholder E
placeholder E
Placeholder F
placeholder F
Placeholder G
placeholder G
Thanks for opening this thread!
Is the pre-rooted Android 4.3 Rom an SKT one? Or is it a debloated one?
I'm currently running 4.3, rooted. (after bricking it yesterday....! This device, a gift from a friend, has been a real pain for me the last 2 days)
What I'm now looking for is a way to get rid of the SMS 70char. limit, and also a way to enable SMS delivery notification...
i900frenchaddict said:
Thanks for opening this thread!
Is the pre-rooted Android 4.3 Rom an SKT one? Or is it a debloated one?
I'm currently running 4.3, rooted. (after bricking it yesterday....! This device, a gift from a friend, has been a real pain for me the last 2 days)
What I'm now looking for is a way to get rid of the SMS 70char. limit, and also a way to enable SMS delivery notification...
Click to expand...
Click to collapse
It's the SKT (E330S) version and is full stock, with addition of the chinese samsung IME to support full screen handwriting of chinese and korean languages. Debloating (incl removal of knox components) is simple with help of tools like Titanium Backup and ES File Explorer; the reason I no longer upload debloated versions is due to the sheer size of these rom images and the limited storage space and bandwidth I have with my mediafire subscription.
The SMS size limit has been set to 160 and you can enter and send a batch of 5 messages at once, before it changes to being an MMS message. I haven't tested the SMS delivery notification, but I have enabled the menu item to set it.
Haven't tweaked the rom too much and left it in stock as much as possible. Most important was to provide a rooting mechanism without compromising the custom binary counter.
davidcsv said:
It's the SKT (E330S) version and is full stock, with addition of the chinese samsung IME to support full screen handwriting of chinese and korean languages. Debloating (incl removal of knox components) is simple with help of tools like Titanium Backup and ES File Explorer; the reason I no longer upload debloated versions is due to the sheer size of these rom images and the limited storage space and bandwidth I have with my mediafire subscription.
The SMS size limit has been set to 160 and you can enter and send a batch of 5 messages at once, before it changes to being an MMS message. I haven't tested the SMS delivery notification, but I have enabled the menu item to set it.
Haven't tweaked the rom too much and left it in stock as much as possible. Most important was to provide a rooting mechanism without compromising the custom binary counter.
Click to expand...
Click to collapse
OK, implementing the SMS/MMS delivery notification was easy by editing the "feature" file in "system/csc/". I'm pretty sure I can also change the SMS max size limit from there but can't find the right line...
How do you remove Knox components? I had froze everything with "Knox" using Titanium Backup, and the result was s bricked device after a reboot (had to flash a stock 4.3 again). I'm already fed up with all these security notifications
(sorry for these questions, I'm coming from a Note 2 anf this is my first Korean device, I'm not used to it at all)
i900frenchaddict said:
OK, implementing the SMS/MMS delivery notification was easy by editing the "feature" file in "system/csc/". I'm pretty sure I can also change the SMS max size limit from there but can't find the right line...
How do you remove Knox components? I had froze everything with "Knox" using Titanium Backup, and the result was s bricked device after a reboot (had to flash a stock 4.3 again). I'm already fed up with all these security notifications
(sorry for these questions, I'm coming from a Note 2 anf this is my first Korean device, I'm not used to it at all)
Click to expand...
Click to collapse
For max number of sms before switch to mms:
Edit in /system/csc/customer.xml
Code:
<Messages>
<SMS>
<PageLimit>6</PageLimit>
<MsgTypeThreshold>
<ThresholdValue>6</ThresholdValue>
For sms size limit, edit /system/csc/feature.xml
Code:
<CscFeature_Message_SmsMaxByte>160</CscFeature_Message_SmsMaxByte>
To get rid of annoying Knox components, I deleted the following files in /system/app:
KLMSAgent.apk
KLMSAgent.odex
KNOXAgent.apk
KNOXAgent.odex
KnoxAttestationAgent.apk
KnoxAttestationAgent.odex
KNOXStore.apk
KNOXStore.odex
KNOXStub.apk
(No problems rebooting)
Man, thanks for all these good advises!!! I had frozen the same apps with Titanium, but the result was a bricked device. Now I removed the apk and the .odex files as you said, and knox is gone while keeping root!
I now can start really enjoying this S4, thanks to you
EDIT: I now have the "enable delivery Notification" in my MMS settings, but actually, even if enabled, I don't get the notification....I'll have to mess around the feature file again
Are the ROMS for E330K/L/S interchangeable or is there some difference in hardware?
JohnnyInBriz said:
Are the ROMS for E330K/L/S interchangeable or is there some difference in hardware?
Click to expand...
Click to collapse
Modems are different definitely.
dc_power! said:
Modems are different definitely.
Click to expand...
Click to collapse
My understanding is that the modem is part of the Snapdragon 800 SOC....
http://www.qualcomm.com/snapdragon/processors/800-600-400-200/specs
I can't keep my mirror up due to increasing need for more space with all the projects I'm working on, sorry guys.
DOWNLOAD
You can find Odin at:
https://build.nethunter.com/samsung-tools
I am no longer hosting firmware for the Note 3. fw.updato.com provides an alternative, and allows wget/curl. (with --referer="link to the download page"))
Example:
N900W8VLU2DPG1 - MTA clicked on at http://updato.com/firmware-archive-select-model?q=N900W8
Code:
wget "http://fws01.updato.com/GALAXYNOTE3/SM-N900W8/BMC/SM-N900W8_1_20160729160241_v4dg1gvbce.zip" --referer="http://updato.com/firmware-archive-select-model?record=3C39D6E6701111E69B2DFA163EE8F90B"
READ INSTRUCTIONS BELOW, OR IT WON'T STICK AFTER FLASHING!
Each zip file contains a _HOME.tar.md5 containing each flashable partition of your device. You can flash the entire tar.md5 for a complete factory restore, or you can extract individual partitions and re-tar them to make individual flashable partition files. There's a tool for tarring them here:
https://build.nethunter.com/samsung-tools/img2tar.zip
GETTING YOUR FIRMWARE TO STICK
When flashing bootloaders (BL) and modems (CP), you must cold boot your phone for the flash to succeed.
To perform a cold boot into Odin, follow these instructions carefully:
Power down your phone
Unplug any cables from your phone
Pull the back cover off and remove the battery completely
Place the battery back in your phone (there is no need to wait)
Place 1 finger on volume down key, and 1 finger on home key
While holding those keys down, place another finger on the power key
Release the finger from the power key when you feel a vibrate
Release your other fingers once you see the Odin warning screen
You may plug your phone cable back into the phone now, or after the next step
Press volume up key to enter Download mode
SOME ODIN OPTIONS EXPLAINED
Auto Reboot - Once the firmware finishes flashing, the phone will attempt to reboot into your current ROM
Re-Partition - Used to flash a PIT file over the current one. See more information below.
F. Reset Time - Enabled by default. Not entirely sure what it does yet.
Nand Erase All - May have different effects on other devices. On the Note 3, it wipes the just the userdata partition to zeros. (your ROM settings, apps, and internal storage)
Phone Bootloader Update - Doesn't seem necessary to select when flashing bootloaders from cold boot, so unsure of purpose.
Phone EFS Clear - Reformats your EFS partition. This deletes calibration data and some small caches, you will want to flash full stock ROM when using this so it can properly restore itself. It's safe to use, and won't wipe your IMEI.
I advise not touching the other options!
When flashing firmware, you can and should leave the default options selected. Confirm that it is just Auto Reboot and F. Reset Time.
RE-PARTITIONING
Re-partitioning may be necessary in the rare scenario that updating to a newer firmware requires more storage than is available in the current layout.
It is possible to back up your PIT file (partition layout) for flashing in Odin later on or sharing with others that are having trouble flashing firmware that you were able to successfully flash.
PIT files are model specific!
Do not flash a PIT file for N9005 on an N900W8 for example. The partition layout will end up pointing to the wrong locations and you'll end up with a blank IMEI / EFS partition or worse.
If you want to back up your PIT file, you must have a rooted phone or be in TWRP which is an environment already running with root privileges.
Executing these commands will back up your PIT to a file (your-device-name.pit) on your internal storage:
su
dd if=/dev/block/mmcblk0 of="/sdcard/$(getprop ro.product.name).pit" bs=16 skip=1088 count=257
You can open the PIT file in a text editor and make sure it starts with v˜4 to be ensure validity.
Restoring a PIT file is as simple as using the PIT tab in Odin and putting it in the box there, then selecting the Re-Partition checkbox in Options tab. Re-Partitioning will not delete any data, however if your PIT file varies from your previous then partition locations may point to completely different places resulting in a no longer functioning modem or worse, a bricked phone.
WIPING YOUR DATA FOR RESALE
You can use the Nand Erase All option in Odin to make your Userdata partition unrecoverable. When the Userdata partition is nand secure erased, all data on it becomes zeros.
In order for Nand Erase option to work, you need to fill an Odin slot. Flashing your bootloader in the BL slot is usually a safe method.
Most ROMs (kernel boot images actually) can't recover from this and will not boot. In order to fix this you have to boot into a recovery.
In TWRP: Go to Wipe -> Format Data -> type "yes" -> Go
In stock recovery: Use the "factory data reset" option
Both of these perform identical procedures that restore a proper format and ext4 layout to your Userdata partition.
ROMs should now be able to boot.
You can confirm through TWRP that your userdata partition has indeed been secure erased by typing in adb or terminal:
hexdump /dev/block/platform/msm_sdcc.1/by-name/userdata
It should display:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
After a few minutes it should complete. The asterisk means that hexdump found that same last row of data (0000...) repeating.
CHANGES
2016-02-26 - Add Nordic SM-N9005XX firmware N9005XXUGPOK2
2016-01-12 - Add SM-N9005XX firmware N9005XXUGBOL3 and N9005XXUGBOJ2 (modem)
2016-01-01 - Add Mexican SM-N900W8UB firmware N900W8UBU2DOL1 and N900W8UBU2DOK1 (modem)
2016-01-01 - Add T-Mobile SM-N900T firmware N900TUVUFOL1
2016-01-01 - Add Exynos SM-N900XX firmware N900XXUEBOL2
2015-12-18 - Add Exynos SM-N900UB firmware N900UBUEBOK1
2015-12-15 - Add Exynos SM-N900XX firmware N900XXUEBOK7 and N900XXUEBOK3 (modem)
2015-12-15 - Add Exynos SM-N900ZS firmware N900ZSUEBOK3 and N900XXUEBOK3 (modem)
2015-12-15 - Add SM-N9005DX firmware N9005DXUGBOK3
2015-12-15 - Add SM-N9005XX firmware N9005XXUGBOK9 and N9005XXUGBOD3 (modem)
2015-12-15 - Add SM-N9005ZS firmware N9005ZSUGOK2
2015-12-15 - Add KT Corporation SM-N900K firmware N900KKKU0GOK3 & N900KKKUGOJ4 (modem) (thanks to Freyelis)
2015-12-11 - Add SK Telecom SM-N900S firmware N900SKSU0GOK3 & N900SKSU0GOJ4 (modem)
2015-12-11 - Add LG Uplus SM-N900L firmware N900LKLU0GOK3
2015-12-02 - Add Sprint SM-N900P firmware N900PVPUEOK2
Why
fingerprinted said:
Why
Click to expand...
Click to collapse
Maybe I just wanna fit in with everybody else!!!!!!!!11
It just seems like a better idea to make all the latest modems and bootloaders for every variant easily available for people who don't want to wipe their custom ROMs or in case of emergencies.
Everything seems to be spread out among multiple threads, and some variants don't even have firmware threads.
Also this post gives me somewhere to send people to when I need it, regardless of what Note 3 variant they have!
Your profile made me chuckle, interests :single females
fingerprinted said:
Your profile made me chuckle, interests :single females
Click to expand...
Click to collapse
Its kinda look cute and honest. Btw,Thanks for a great work.
You are a very organized man, amazing work. Thank you
+1 very neat thread and you can get the files easily. Oh almost forgot to mention that your guide is very detailed.
There are numerous threads regarding Bootloader and Modems, but none as good as this .
Thanks for the effort mate, while this is supposed to be for Note 3, some information inside has a lot of stuff inside worthy of forwarding people to, pretty much a lot of general Samsung stuff explained.
:good:
EDIT: just wanted to add one thing. Sammy tends to confuse us, and we tend to inherit that confusion to other users. I.e, CP and BL are not consistently the same, we have right now K6 as a BL, but the modem seems still to be K1.
We should have a way to identify the real internals through *OUR* naming conventions.
guys
I am facing very low gsm signals after installing a custom rom
I cleaned flashed it wiping al that was needed
Anyway to check if i am using a wrong modem where i am located?
Question
I am having SM-n900k. Can I flash bootloaders from another model? I am sick of korean language in the download mode.
5.1.1 BL and CP?
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
HazeMC said:
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
Click to expand...
Click to collapse
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
sajmon1983 said:
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
Click to expand...
Click to collapse
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
is there any reason to update to the latest bootloader/modem?
(I use XSP firmware. haven't been able to find or make my own BL or CP files)
jcadduono said:
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
Click to expand...
Click to collapse
I cant find the link for the differences, but apparently they do actually differ, if i'm not wrong, it has something to do with a different development tree. People have reported issues flashing non-nordic roms after the nordic ones itself, but only when the values change.
jcadduono said:
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Click to expand...
Click to collapse
Thanks for a very complete response!
I've realised that the front camera has the same issue recording video, so as far i understand you response, i will try to update the kernel, or try a different rom.
Thanks mate.
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
yes ok
jorioux said:
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
Click to expand...
Click to collapse
If you are on 5.0 LL you have to use DOI2
I guess I finally hard-bricked my N920P trying to install Universal SafetyNet Fix. It was on stock (N920PVPS3DRH1) but I had TWRP and Magisk Canary installed. I was trying to get Zygisk working but couldn't get it properly turn on, even on the stable and canary builds. That's where I had tried to install the SafetyNet fix module. It said it doesn't fully support anything below Android 8.0, but it did finish installing and asked me to reboot. And it never turned back on.
I cannot get into the download mode, recovery or system. Tried all key combos and no life at all. I drained the battery all night long and tried plugging into the PC and now it detects it as an unknown "Exynos7420" device. That was something from the nothing I got before. I tried looking up on how to rebuild the corrupt bootloader but I couldn't wrap my head around on how the process works. There was material on getting a software called "USB_Downloader" and I got all the way to installing the drivers and getting that software recognise the device as a COM port. I did this in a Windows 7 32 bit VM on VirtualBox (VMWare kept crashing my entire USB Host Controller everytime I tried passing the phone's connection to the VM, which was weird).
Now I'm stuck with this software and am unable to understand what I need to do next. There was something about getting the sboot.bin file and creating 4 new files to push through the Exynos COM port to fix the bootloader. There was also something about getting a Hex editor to do this, but I cannot understand what's going on. Could someone please help me get around this?
Thanks in advance!!
Never mind I fixed it. Just posting it here to make sure no one else gets stuck like I did for a long while. So what I had done was I forgot I had a custom ROM installed. It had been based on the N920PVPU3DQC5 firmware. So I downloaded that firmware, extracted the sboot.bin file then went to work with a hex editor (HxD for Windows specifically).
Open sboot.bin in the hex editor and start making new files listed below. The sections are also listed below, you can ensure the size in the bottom of HxD.
Save them as novi1.bin, novi_2.bin, etc...
The offsets I used are:
BL1 or novi1.bin: 0 - 0x1FFF (size 0x2000)
BL2 or EL3 or novi_2.bin: 0x2000 - 0x31FFF (size 0x30000)
EL3 or BL2 or novi_3.bin: 0x32000 - 0x3dfff (size 0xC000)
S-BOOT or novi_4.bin: 0x3E000 - 0x18F100 or end of file (size 0x15110), this will include tzsw.
Next this is the cfg file I used:
Code:
; S Project
; must keep order of binary list
; BL1
DNW_STORE e5250 fwbl1 200 20 novi1.bin
;DNW_WAIT
; BL2
DNW_STORE e5250 el3_mon 2000 20 novi_2.bin
; u-boot
; Wait Re-Enumeration
DNW_WAIT
DNW_STORE e5250 bl2 2000 20 novi_3.bin
;DNW_WAIT
DNW_STORE e5250 bootloader 20000 20 novi4.bin
;DNW_WAIT
;DNW_STORE e5250 tzsw 20000 20 4pt.img
Copy this code and save it as SH-usb-booting.cfg in the same folder as your .bin files. Now you can launch the multidownloader and load the .cfg and select Auto Run. Now press and hold the power button on your phone and connect it to the PC. It should automatically go through the whole flashing process and end up in the download mode screen. You can now flash the firmware from there!
If you have any doubts hit me up!
LOL I'm stuck again. I got into Download mode but my VM was having trouble connecting to the Download mode USB modem and it crashed the USB controller on my PC. I had to reboot the phone and now I'm stuck again in Exynos USB mode. Trying to get back into Download mode using the files I created above but it's not working anymore. I can hear the USB getting disconnected on the host at the AP Re-enumeration step but it isn't disconnecting from the guest VM. I guess I'll have to find a physical PC to try this out on.
EDIT: I had used VirtualBox until this step. After the hanging on Re-enumeration issue, I figured it could be Virtualbox causing the issue so I tried using VMWare, and ta-da, it worked. Read posts below for updates.
So I somehow got myself to get into Download mode consistently. Turned out my VM's USB controller was acting up so I clean installed it and I'm able to send the sboot files and get into Odin mode. But new trouble. Everytime I flash the stock firmware it goes through the process, passes and resets. But it never boots!! Just goes back to the same Exynos mode. I can re-flash the sboot file to get back into Odin mode but I'm stuck like this. I have no idea what to do now...
Progress so far:
I can't remember what custom ROM I had originally. Radeonmaya S8+ N920P ROM was supposed to be based on the DQC5 deodexed stock ROM posted here in the N920P forum.
1. Tried creating new files from DQC5 - SPR sboot.bin: Booted into Download mode, tried flashing the 4 file firmware, no progress, resets back into Exynos mode.
2. Used the DQC5 - SPR sboot.bin to boot into download mode: Tried flashing thr 4 file firmware for the latest firmware that was installed in the phone which was DRH1. No progress, resets back into Exynos mode.
If I'm reading this correctly, the Radeommaya ROM makes changes to boot.img and system partitions. Everything else remains stock, therefore my original bootloader for firmware DRH1 should work. However, I'm not able to get into the system.
I must note that TWRP recovery was installed on the device. The best course of action would be to install the same custom ROM back together with TWRP, but I could not find an Odin flashable tarball for the Radeonmaya ROM. The forum's been dead for a couple of years and the Telegram group is also dead. Looking for ways to make my own tarball using handpicked files maybe.
Currently trying to create new .bin files to boot into Download mode via the Multidownloader from sboot.bin files I salvaged from the XAS (Sprint Unbranded) firmware packages DRH1 and DQE1 (Apparently this firmware has helped someone in the Radeonmaya ROM thread to boot back into the system from a similar hard bricked situation, however I speculate this would not fix my problem because the DQE1 firmware is newer than the DQC1 firmware, which the custom ROM was based upon)
Will post more findings later.
P.S. VMWare could be quite finicky to work with when trying to passthrough the Exynos USB Device to a Windows 7 guest. It caused my AMD Ryzen host to crash its entire USB controller and both my USB mouse and the phone wouldn't connect to the HOST, let alone the guest. It causes a never-ending loop in the code which also stops a proper system restart, hence needing you to force power-cycle the whole computer.
This is because of the unusual nature of the driver being 32-bit only and incompatibility with VMWare. However, it should work when you reinstall VMWare without the Enhanced Keyboard driver, and also reinstalling the Exynos USB driver on the host and the VMWare USB Device (found in the Universal Serial Bus controllers section when you have the USB connection passed through to the VM).
Hey !
I'm posting this small guide for the people who gets bootloops, who can't flashing anything anymore or who gets their smartphone not charging ( after trying to switch the cellphone off it goes to charging screen for a few seconds then reboots, not charging even if you let it on charging the whole day). I had all those issues and I though it was bricked. Fortunately I could flash stock using the latest version of odin but my goal was to make it work using heimdall because, with heimdall, you can flash just the super partition and the program works on linux.
Possible cause of these issues: the heimdall shipped on most linux package managers and even on the official site don't have some patches and my guess is that the tool are corrupting the partitions on a53 and m53 (both have the same model) due to the program not being handling well the partition size even though it completing 100% and reporting no issues during the flashing process.
Simple solution: use a specific patched heimdall version. There is a fork release of heimdall on github, it has, until today, 21 commits ahead of the heimdall official repository, with a commit fixing the way heimdall handles partitions bigger that 3.5G
commits ahead of the official heimdall repository: https://github.com/Benjamin-Dobell/Heimdall/compare/master...amo13:Heimdall:master
commit that probably fixed the issue: https://github.com/amo13/Heimdall/commit/d8a14b556d9a16d1dc4501c1a1db4bc473efd1c1
source code: https://github.com/amo13/Heimdall
Download/release page: https://github.com/amo13/Heimdall/releases/ (you might notice the version is the same of the package managers/official sites but there are many improvements(commits) on this one)
tip: There are many scripts or tools that uses the heimdall binary to, for example, unpack, replace system.img with your custom's rom system.img then rebuild super.img like repacksuper so it would be good if you replace your non working heimdall binary file, on your operating system's binary directory, with the patched one so those tools pick the right heimdall binary during their tasks.
123
Hello! I was using heimdall until I got an odin 4 binary file
I don't have it's source code, it's probably leaked from samsung, but hey, it works like normal odin
Sorry, I didn't see your post before, I was busy