Related
Hi all,
Two weeks ago I dropped my Samsung GT - I9505 S4 ( T -Mobile NL ). The screen was damaged (black), but the phone still worked. I could hear the startup sound and also incoming mail and whatsapp messages. So the phone was alive, but the screen was dead.
So i ordered a new screen and replaced it myself. This was no problem at all. The screen replacement was a succes. The S4 logo came up. I was happy the screen replacement worked. But now i had this problem, the phone was stuck in the bootlogo!
I tried to enter the recovery mode, it didn't work (Volume Up + Home + Power).
Then i tried to enter the download mode (Volume Down + Home + Power). This worked.
Then i tried to install the official firmware. I chose to install the newest firmware (I9505XXUEMKF 4.3). I downloaded it at sammobile model=GT-I9505&pcode=TNL#firmware
I used Odin 1.85, 3.07 and 3.09 on Windows 7 and Windows 8 with all the Samsung USB drivers installed. And also i used the Pit file CSB signed Fusion3 EUR 0325 V2.
The phone is still stuck in the boot screen. After a clean install and pass from odin, the s4 says: "Recovery booting". Recovery mode still not accessible.
When i flash my S4 with the latest CW-Autoroot or Philz Touch, the Phone says:
Recovery booting ....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Download screen info:
ODIN MODE
Product Name: GT-I9505
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled
Any help would be appreciated! I am willing to pay for the right solution.
1. Download a suitable kernel in tar.md5 format -> HERE
2. Download ODIN 3.09
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA/AP button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
11. Try now to install the firmware MKF u downloaded before (without selecting .pit file)
12. Tell me how it works :highfive:
I just followed your steps, one by one.
I have all the versions of Odin, so i used the Odin 3.09 this time, like you said.
I putt my phone in download mode and installed the kernel i downloaded from your link. Odin status: pass.
Status Phone:
Start [224,1440]
BAR [240, 1440]
END [840, 1440]
Odin Status:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-jfltetmo.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
S4 is still stuck in boot logo.
When i try to get in to recovery mode (By holding Volume up, Home + Power), this message comes up:
Recovery booting ....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Everytime i get stuck with the Boot logo, Recovery booting.. or Recovery is not enforcing seandroid.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TNLEMJ6_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Stuck in:
Recovery Booting....
you need a full wipe before flashing stock or custom rom, if you do not do as you get into the boot loop
Nininho1995 said:
you need a full wipe before flashing stock or custom rom, if you do not do as you get into the boot loop
Click to expand...
Click to collapse
How can i do that? How can i do a full wipe? Remember i cannot get into recovery mode at all.
Please help?
do you have a stock rom?
do you have a stock recovery?
do you have a stock kernel?
Nininho1995 said:
do you have a stock rom?
do you have a stock recovery?
do you have a stock kernel?
Click to expand...
Click to collapse
Yes, i have everything stock. Installed from sammobile . com.
ok then'll try a pre rooted rom to flash from djembey. it is not good that you do not get into recovery. then you reflashing the latest philz revovery touch.
so everything should work, take the best pre rooted XXUEML6 because this is the latest.
Nininho1995 said:
ok then'll try a pre rooted rom to flash from djembey. it is not good that you do not get into recovery. then you reflashing the latest philz revovery touch.
so everything should work, take the best pre rooted XXUEML6 because this is the latest.
Click to expand...
Click to collapse
Thanks. I will give it a try.
Is this the file i need? Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>> See below.
http://forum.xda-developers.com/showthread.php?t=2250824
Model: GT-I9505 (4.3)
PDA: XXUEML6
PHONE: XXUEML6
CSC: OXXEMK3 (27 codes) (NOTE: KIES will NOT recognize this FW due to CSC mismatch..)
Kernel: 3.4.0-2082040 (19.12)
KNOX WARRANTY VOID - 0x1
Build Date: 19.12.2013
Changelist: 2082040
Original Stock ROM: Download: <<< Samsung-Updates.com >>>
Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>>
Latest KNOX Bootloader INCLUDED - Completely IRREVERSIBLE back to 4.2.2!!!
DannyPRK said:
Thanks. I will give it a try.
Is this the file i need? Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>> See below.
http://forum.xda-developers.com/showthread.php?t=2250824
Model: GT-I9505 (4.3)
PDA: XXUEML6
PHONE: XXUEML6
CSC: OXXEMK3 (27 codes) (NOTE: KIES will NOT recognize this FW due to CSC mismatch..)
Kernel: 3.4.0-2082040 (19.12)
KNOX WARRANTY VOID - 0x1
Build Date: 19.12.2013
Changelist: 2082040
Original Stock ROM: Download: <<< Samsung-Updates.com >>>
Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>>
Latest KNOX Bootloader INCLUDED - Completely IRREVERSIBLE back to 4.2.2!!!
Click to expand...
Click to collapse
Yes man this is the right one.
DannyPRK said:
Everytime i get stuck with the Boot logo, Recovery booting.. or Recovery is not enforcing seandroid.
Click to expand...
Click to collapse
- Turn off ur phone
- Use the combination (Vol up + Home button + Power button)
- When u see the letters of Samsung S4 in white... drop the Power button
- If u dont do it by this way u will be stucked in the boot logo
- This will go directly to your CUSTOM RECOVERY
Nothing works guys.
I really can't get into recovery mode at all.
When the phone is not flashed with the philz revovery touch, it keeps stuck on the samsung logo or Recovery booting....
When the phone is flashed with philz revovery touch i get:
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Are there more options?
Joku1981 said:
- Turn off ur phone
- Use the combination (Vol up + Home button + Power button)
- When u see the letters of Samsung S4 in white... drop the Power button
- If u dont do it by this way u will be stucked in the boot logo
- This will go directly to your CUSTOM RECOVERY
Click to expand...
Click to collapse
I did this like 1000 times. I'ts getting really frustrating. Could it be that the something is broken?
DannyPRK said:
I did this like 1000 times. I'ts getting really frustrating. Could it be that the something is broken?
Click to expand...
Click to collapse
1- Install the firmware u had (without .pit file). The stock firmware have STOCK recovery that have to work (If u cant go to STOCK recovery follow the step 2)
2- Flash this file with ODIN: HERE
3- Do the same process of post #12
Joku1981 said:
1- Install the firmware u had (without .pit file). The stock firmware have STOCK recovery that have to work (If u cant go to STOCK recovery follow the step 2)
2- Flash this file with ODIN: HERE
3- Do the same process of post #12
Click to expand...
Click to collapse
Just did this. Now i tried it with the I9505XXUEMJ7 (Non brandend NL).
Guess what? Recovery booting....
Is my phone dead?
So basically it comes to this:
- When flashed stock firmware:
Recovery booting....
- When flashed custom firmware:
Recovery booting....
- When flashed stock firmware + philz_touch, openrecovery-twrp or even with recovery-clockwork-touch :
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
DannyPRK said:
So basically it comes to this:
- When flashed stock firmware:
Recovery booting....
- When flashed custom firmware:
Recovery booting....
- When flashed stock firmware + philz_touch, openrecovery-twrp or even with recovery-clockwork-touch :
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Click to expand...
Click to collapse
u have unbranded phone?
Joku1981 said:
u have unbranded phone?
Click to expand...
Click to collapse
I have T-mobile NL, but also with the T-mobile (I9505XXUEMKF) the recovery mode doesn't work, but Odin says Pass.
So i tried it also with NL Unbranded (I9505XXUEMJ7). I think this does not have any effect.
It's strange because before the screen replacement, the phone booted just fine (except i didn't have any screen). Now i have screen and no boot...
Edit:
What could be the problem?
- Bootloader?
- Some other error?
DannyPRK said:
I have T-mobile NL, but also with the T-mobile (I9505XXUEMKF) the recovery mode doesn't work, but Odin says Pass.
So i tried it also with NL Unbranded (I9505XXUEMJ7). I think this does not have any effect.
It's strange because before the screen replacement, the phone booted just fine (except i didn't have any screen). Now i have screen and no boot...
Edit:
What could be the problem?
- Bootloader?
- Some other error?
Click to expand...
Click to collapse
- Go to ODIN
- Untick REBOOT OPTION
- Flash again the MKF and the .pit file u downloaded before
- Click start and wait till finish
- When finish ur phone will be stucked but no worries
- Take off ur battery for 2 min
- Put it in again
- Turn on ur phone normally and let it boot for 10 min (no worries if u think its stucked)
- Tell me if booted correctly when u finish this process
Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?
Anybody? I need my phone back :S
chemell said:
Anybody? I need my phone back :S
Click to expand...
Click to collapse
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.
spamtrash said:
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.
Click to expand...
Click to collapse
But can I use another rom? I don't care if isn't a 4.2.2 rom because I need the phone again doesn't matter with which rom or android version.
If u can boot to recovery flash a custom rom then flash stock via odin
aayushkhajuria2842 said:
If u can boot to recovery flash a custom rom then flash stock via odin
Click to expand...
Click to collapse
I can't, I only got download mode...
Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power
aayushkhajuria2842 said:
Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power
Click to expand...
Click to collapse
Well it doesn't work, when I turn on the phone a black screen with a cellphone, a warning sign and a monitor appears and a text says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
With this screen I can only go into download mode but when I try recovery mode it just puts the screen black and back to the same text and pictures.
Another thing that worries me it's that I can't turn the phone off with the button, only if I pull the battery out.
This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again
aayushkhajuria2842 said:
This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again
Click to expand...
Click to collapse
I've already tried with the rom "I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5" (I believe it's stock rom) and get the odin error that appears in my first post...
Try some other firmware of you own region ......... 4.3 or 4.4 whichever u have for your region .......I think then u will nt get same error
chemell said:
Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?
Click to expand...
Click to collapse
Hi, try to flash through kies emergency firmware recovery.
navdeepavi said:
Hi, try to flash through kies emergency firmware recovery.
Click to expand...
Click to collapse
Hi, I tried, but in Kies I can't get trough the "Connecting..." status so when I choose "Emergency firmware recovery" the list of devices appears empty.
I think u should try flashing some other stock firmware I hav had the prblm before
aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...
It should work I did the same thing but cant say anything
aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
chemell said:
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...
Click to expand...
Click to collapse
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
DELETED, procedure was for I9505 ONLY
you have to follow the procedure form this link instead.
Good luck.
spamtrash said:
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
You will need the PC with not faulty CPU, first.
Then, you have to use the PIT from here
Of course, you will need the Qualcomm drivers as well, from here or this one
Then, you have to follow the relatively simple procedure described here
That shall fix the corrupted bootloader, and I hope that you will not see the described there errors which would point to the hardware problem.
Good luck.
Click to expand...
Click to collapse
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.
Just an observation, you said you have no recovery right? So have you tried just flashing the tar of PhilZ recovery using Odin to get it back?
At least then you'll have a recovery again and can move forward with a custom ROM install
Sent from my GT-I9505 using XDA Premium HD app
lolo9393 said:
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.
Click to expand...
Click to collapse
right. the correct one provided.
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?
edutchz said:
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?
Click to expand...
Click to collapse
Hi bro i have exactly the same problem and try to flash cystom recovires and i tried to back to 4.3 byt odin give me fail
So please if you solve it tell how
try this
1. Boot to recovery, turn off the phone then press Home +
Power + Volume up
2. wipe data / factory reset
3. Wipe Cache partition
4. Remove battery and put it back after 30 seconds
5. Boot to Download Mode, turn off the phone then press
Home + Power + Volume Down then volume up
6. Flash Firmware via ODIN be sure uncheck
AUTO REBOOT and wait to be completed
7 when odin show message 'pass' unplug the cable and Remove battery again and put it back after 30 seconds
8 now switch on the mobile but don't restart it just goto to recovery mode agAin and and follow the the step 1 and 2 again
then reboot
your problem solved
its just like downgrading of mobile but it work
(if this not work the try to install custom recovery like cwm)
note: I am not responsible for any harm or brick of your mobile try it own your risk
this step are my opinion not recommendations
but I had test this method for same problem)
@android_smater bro it's won't boot to recovery at all that is the problem
altayeb hoota said:
@android_smater bro it's won't boot to recovery at all that is the problem
Click to expand...
Click to collapse
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode
android_smater said:
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode
Click to expand...
Click to collapse
i tried to install cwm or twrp but still nothing happen just galaxy grand2 sm-g7102 logo with blue text"recovery booting at the top"
i can't access recovery with stock recovery or any custom recovery at all
and also i can't be able to flash android 4.3 odin gives me "fail" but kitkat flashed fine but when it finished i got the same problem
edutchz said:
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
try to downgrade to NH6 use my thread it will work
http://forum.xda-developers.com/galaxy-grand-2/general/how-to-downgrade-to-nh6-t2913368
Click to expand...
Click to collapse
then take your mobile to service centre. .
please help me.i have this problem with grand 2
i dont know how can i fix it...please tell me..if you resolved.
For anyone who still has this problem on their Galaxy Grand 2, apparently I never found a way to fix it. But after giving up on the phone and giving it to my cousin, he was more patient than me and he left the phone powered on while stuck on the Logo screen and after say 30 minutes to 1 hour the phone booted up.
The phone works normally, however should you power it down..turning it on again will take it roughly 30 mins to an hour to get past the initial Logo screen, am not sure why but that is how it now behaves.
Try connecting it to a charger while you wait for it to boot, hopefully it will work for you as well.
Thanks
I no how to fix the problem is i think u have not downloaded of ur region
Same damn problem here
Problem seems to be related to fake Samsung Phones. I went to the Samsung assistance centre in Guangzhou (China) and they felt quite embarrassed to tell me that although I may accept to pay any fee they charge they cannot fix my phone because it is not made by Samsung and that is easily the reason why it has a faulty boot manager, probably hacked by incompetents.
Either the phone is fake or the official Samsung Service centre here is, in any case there seems to be no way around it.
I a looking now for some way to reload the original boot loader and then restart from there.
I am having exactly this same problem. I actually installed a Custom ROM from here, but the ROM had some bugs and I later decided to go back to the official firmware from Smasung, only to get stuck on the Samsung boot.
i am here with the same problem with some minor changes
my galaxy grand 2 duos showing
Could not do normal boot.
ODIN MODE
PRODUCT NAME:SM G 7102
CURRENT DINARY:Custom
SYSTEM STATUS:Custom
KNOX WARRANTY VOID:0*0
QUALCOMM SECUREBOOT:Enable <CSD>
RP SWREV: S2, T2,R2,A2,P2
SECURE DOWNLOAD:ENABLE
UDC START
AFTER A BIG GREEN ANDROID LOGO
Downloading...
Do not turn off target!!
Has anyone found solution yet? I'm having same problem with my Grand 2 Duos.
only download mode is working. Can't boot to recovery or normal.
After leaving in charging for 15-20 mins, I got white flash-logo( something new then ever).
So keeping it in charging for more time. let's see...!
PS: phone starts with grand 2 logo and then samsung comes up with audio. that's it ! after 3-4 mins later reboots and so on.
in recovery mode it shows android symbal and loading bar.. then it reboots in normal mode. and so on.
I guess you guys have downloaded a wrong firmware. I mean, sure it says it's for Grand 2 but the "Region" is different. Try downloading the one for your region like if you are from India, you gotta need indian version that is INS.
Sent from my SM-G7102 using Tapatalk
My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this
oodjacid said:
My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this
Click to expand...
Click to collapse
take the battery out and try go in to download mode
SoUnd001 said:
take the battery out and try go in to download mode
Click to expand...
Click to collapse
It doesn't go to recovery/download mode without battery
It is okay to downgrade?
Does anyone knows if something could go wrong if I downgrade from lollipop to kit kat?
I'm trying to downgrade to kitkat but doesn't work for sm-g530h :'( :'( :'(
Go here and make sure your flashing the correct firmware for your varient >> http://samsung-firmware.org/model/SM-G530H/
Note: the country code is very important also for correct firmware.
Also: maybe some varients cannot be reverted because of write protected files that once on a newer version, the older cannot over write a later version..I'm new to Samsung, but some Moto devices are this way..maybe research this..
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
mohamedbk said:
I'm trying to downgrade to kitkat but doesn't work for sm-g530h :'( :'( :'(
Click to expand...
Click to collapse
Is Odin3 failing to flash (or) is the device bootlooping..or both.?
Have you tried a "system erase" via recovery, starting anew, clean OS before flashing.?
sent by my: SM-G531M-88 Grand Prime (or)
my: SM-N910C Note 4 (Lollipop 5.1.1)
I just did it today...
... and if you're careful with the baseband model #, and country code, you should be fine. Here's how I did it:
1- go to Sammobile and search for SM-G530H under the firmwares page, and download the firmware for your country region, and watch the PDA and CSC codes, you need to download the ones for your baseband model;
2- Once the firmware is downloaded, make sure you have Odin and Samsung drivers installed in your PC;
3- Open Odin, load the firmware under AP/PDA option. Start your phone in download mode, plug it and once it's recognized, start the flashing procedure;
4- The phone will start, and once the Samsung bootloop screen shows, it will hang/freeze in that screen. That's because Lollipop is still the main system, and Kitkat is trying to update "in" it. So, open your phone and take the battery out, this will turn it off;
5- Place the battery back in, and restart the phone in recovery mode. Wipe cache partition, then wipe the system to factory default. Then restart the phone;
6- It will now boot up Kitkat. It may take sometime, as it is setting up the apps.
Gonna try it now, thanks!
it is safe
Yeah, its safe, I already did it :3
its works... and now i will again upgrade lollipop.. so if im going to setting>about device>system update and this is upgrade lolipop?? plzz tell m
PHP:
Consider this 1. Choose the right baseband to your device 2.after flashing via odin go to stock recovery by pressing vol up power button and home then choose wipe dalvic cache then wipe phone data after that reboot then it should boot normaly with kitkat installed ☺ thats what ido ive no problem encountered when downgrading
Am trying
Hi
Am trying to downgrade my samsung grand prime g530H from 5.0.2 to 4.4.4
every time it fails and said : " secure check fail : aboot "
what should i do ?!
please help me
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> 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)
<ID:0/004> Removed!!
these three buttons together press 5-10 sec (vol(-) button , home button, power button), then a windows open, select the download mode by pressing vol+ button, then from odin flash rom
Flashing on this rom OK G530HXXU2BOH5_G530HSER2BOH5_SER_5.0.zip
but when i select G530HXXU1ANI8_SER1ANI8_Russia_4.4.4_Repair_Firmware this to downgrade .. i got aboot fused error
im getting same type of error too. any alternative method?
I am also trying to downgrade with z3x but fail. try all methods
I maybe a years late or so but I am pretty much sure you can't downgrade from 5.0.2 to 4.4.4. I think the 5.0 bootloader won't allow to downgrade to 4.4.4.
Obviously I maybe wrong since I didn't tried it myself. I only heard it from others. And even if you are able to flash it it will probably go hard brick or something. Do at your own risk.
Hi,
I managed to be brick free since I started reading XDA Developers & modifying my devices starting with my XDA Mini in 2008. Now 6 devices later I finally managed to - hopefully just soft - brick my Note 3 (hlte)
I bet if I search long enough I could try to recover it on my own, and i did so the lasst 15 years, but I am a bit scared now, I really fear to loose the last thread this phone is hanging on, so please hear me out and maybe its an easy problem for the more expiereinced users out there.
Situation before the update:
* rooted
* cwm recovery - latest version
* cm11 latest snapshot
* Encryption enabled
The update:
- Used adb sideload method to load cm12.1 latest nightly
- Phone booted fine, just was completely misconfigured (Xposed not working, root apps lost root access, etc.)
- Wanted to go to recovery, but recovery stopped working. Phone just showed shortly it goes to recovery, then black screen
- So I factory resetted the phone via normal CM settings.
- Everything was fine, I started to install apps and was happy.
- Phone is currenlty NOT encrypted anymore
- I totally forgot to fix the not working recovery mode *DOUH*
- Then I changed the DPI settings in build.prop to 320 as it was under cm11
- Phone never rebooted.
The situation now:
- Phone does not boot normally, shows black screen right after boot mode details in top left corner. No boot logo and such
- Phone can't enter recovery, same as with normal boot
- ADB can not see the device in either normal boot/recovery/download mode
- Download mode seems to be still working *HOPE*
So what to do now?
Can I somehow just fix the build.props?
Can I flash a new recovery using ODIN, and then format/wipe/reinstall?
Can I simply reflash CM12.1 using ODIN?
Or do I have to, as some howto suggested, flash a stock samsung rom? And which one for that matter?
Hope someone can help me,
CySlider
Update: Solved by pushing the right stock rom to the device using ODIN.
Interesting part I learned: You can flash multiple times with ODIN without rebooting the device if flashing fails. You just have to unplug and replug the cable (quickly if Battery is nearly dead). Messages on Screen might get messy with errors that the loading bar got wrong values, but it works.
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
JJEgan said:
Flash stock Samsung rom via Odin .
Can I somehow just fix the build.props? YES if you can see it on your phone.
Click to expand...
Click to collapse
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Cy_the_Slider said:
Ok, which one, Lolipop? or Kitkat? Last stock that was installed before going to Cyanogenmod was Kitkat or even older.
Also will I loose root access this way?
Click to expand...
Click to collapse
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Rosli59564 said:
If you just want a cm rom just flash a kit kat official rom.
Anyway try to go into download mode. When it asks to cancel or continue choose cancel. I saw several members mentioned the phone managed to boot that way.
And off course no root.
Sent from my SM-N920C
Click to expand...
Click to collapse
Ok, thank you. About the tip with Cancel. unfortunately it did not help. I geuss the problem is an invalid DPI setting in the build.props and it will not changed by going to download mode first :/
Ok I will try to locate a stock rom with Kitkat.
Thank you.
No success it seams:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/012> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:1/012> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:1/012> File analysis..
<ID:0/007> SetupConnection..
<ID:1/012> SetupConnection..
<ID:1/012> Initialzation..
<ID:1/012> Get PIT for mapping..
<ID:1/012> Firmware update start..
<ID:1/012> SingleDownload.
<ID:1/012> sbl1.mbn
<ID:1/012> NAND Write Start!!
<ID:1/012> aboot.mbn
<ID:1/012> rpm.mbn
<ID:1/012> tz.mbn
<ID:1/012> sdi.mbn
<ID:1/012> NON-HLOS.bin
<ID:1/012> boot.img
<ID:1/012> recovery.img
<ID:1/012> system.img.ext4
<ID:0/007> Can't open the serial(COM) port.
<ID:1/012> modem.bin
<ID:1/012> cache.img.ext4
<ID:1/012> hidden.img.ext4
<ID:1/012> FAIL! (Size)
<ID:1/012>
<ID:1/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 2)
I used: N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_HOME.tar.md5 and set it to AP setting in ODIN 3.10.7
CAN I leave Download mode to test, if something changed? Or should I better stay in download mode to try again?
Ok, after realizing that I can not flash again without reentering the doanload mode anyway, I restarted.
It showed a new download mode with the message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I searched and found that I should use the right PIT file. I found a combination that seemed to match my device here: (german)
http://www.pocketpc.ch/samsung-gala...1800-anleitung-flashen-dbt-fw-eu-geraete.html
I did hold my breath, and...: Failed again:
<ID:0/012> Added!!
<ID:0/012> Removed!!
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOE9_N9005DBTGBOF1_N9005XXUGBOD3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> cache.img.ext4
<ID:0/012> hidden.img.ext4
<ID:0/012> FAIL! (Size)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, did I finally manage to hard brick? ((
I'm still in this special mode scraed frozen about powering off as I saw messages saying this is the last shot I had. COME ON!!
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Cy_the_Slider said:
What I don't get is. After updating to CM12.1 didn't I got Lolipop bootloader with it? Maybe trying to put on 4.4.2 was wrong after all, b/c of downgrade?
Rop left in download mode is this info:
Product Name: SM-N9005
Current Binary: Custom
System Status: Custom
Reactivation Lock(KK): Off
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enabled
UDC START
anyone?
Click to expand...
Click to collapse
Try non DBT firmware. So you can still enter download mod?.
Sent from my SM-N920C
Rosli59564 said:
Try non DBT firmware. So you can still enter download mod?.
Click to expand...
Click to collapse
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Cy_the_Slider said:
I don't know. Luckily, if I unplug and replug the USB Cable quickly, I seem to be able to flash again without the need to find out, if it will boot again.
I am currently downloading the UK version as I think to remember it was an english phone. (Got it as a present)
I just don't understand why the PIT did not fix this issue. it should have resizeed the partition anyway...
Damn I feel stressed...
Click to expand...
Click to collapse
Can't you just flash a twrp and flash a CM from there?
Sent from my SM-N920C
If you tell me how to flash a twrp via odin. Sure I would try. Is this possible?
The UK Rom download finished. Lets see if htis works.
Ok, Flashing the UK BTU rom worked in the sense that ODIN did not show any errors.
When I try to start it, it starts until it asks for a password?!? then it crashes.
I can enter recovery, but when I factory reset, it does not start at all and recovery is also gone again. Only Downloadmode is luckily still available.
Have I messed up the factory reset feature by applying the PIT file for the german rom maybe?
Update: Seems I made it. The last problem now was the Batery being completely dead as it seems to not be loading while in this broken state. And the USB PC connection was not delivering enough power to survive the phone fully booting. Now its on the loginscreen and charging.
Hopefully I can put a Solved behind this topic soon. Thanks for all input!