Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
Aucun commentaire:
Enregistrer un commentaire