Database Users

[Q] SM-N9005 bricked, help needed!

I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?

k3000 said:
I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
Click to expand...
Click to collapse
try a different odin

jaythenut said:
try a different odin
Click to expand...
Click to collapse
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.

k3000 said:
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
Click to expand...
Click to collapse
Try 3. what ever the number is i think it's better

jaythenut said:
Try 3. what ever the number is i think it's better
Click to expand...
Click to collapse
Odin3v185
That's the one I used.

k3000 said:
Odin3v185
That's the one I used.
Click to expand...
Click to collapse
No not that one v 3.07

jaythenut said:
No not that one v 3.07
Click to expand...
Click to collapse
Just tried it again with ODIN v3.07 and got the same error message in ODIN
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

This is getting really frustrating...
I tried different ODINs running on XP, Win 7 and Win 8.
I ran ODIN as Admin or Standard user and I used different USB ports and cables.
Nothing seems to help.
For example, trying to flash stock ROM gives me this error in ODIN:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....

toker_X1 said:
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
Click to expand...
Click to collapse
There is no error message on the display... that's exactly the text I see as well.
The only things that happens on the display the moment ODIN displays "FAIL", the blue progress bar freezes... I'd day it doesn't get further than 1-2%.

Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.

toker_X1 said:
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
Click to expand...
Click to collapse
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Why didn't you use ODIN 3.09 like guide here on XDA says?
Have you tried with that version?

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.

toker_X1 said:
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
Click to expand...
Click to collapse
Just tried... I get stuck at 2) again trying to flash the Kernel.

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
try stock firmware from www.samfirmwares.com with odin v3.09

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
Uhm, probably a dumb question, but did you use the CSC file as well? Didn't see that in the SS.

nabilsweet007 said:
try stock firmware from www.samfirmwares.com with odin v3.09
Click to expand...
Click to collapse
Unfortunately, no progress. Fails at the very same stage all where all my other efforts have failed, too.
Note: I am using the standard USB 3.0 cable which came with the Note 3. I have tried about 5 different USB 2.0 I have at home. Windows would not recognize a USB device being connected, but the Note 3 itself starts to charge the battery.

What was the csc of the phone before you tried the first flash?
Sent from my SM-N9005

SUCCESS!!
I went to the basement and dug out an old Win XP laptop, approx. 2002 vintage, which has not been used since probably 2005.
Plugged in my Note 3 with the USB 3.0 cable (of course at USB 1.0 speeds), re-ran Root de la Vega from scratch and voilà, it worked!
LESSON LEARNED: Do not use VMWARE FUSION/MAC to root. IT WILL BRICK YOUR PHONE.

[HELP] i9505 Stuck in Boot (serious problem)

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

Odin Fail

I have been trying to root my note 3 SM-N900 for several hours today and I am getting quite frustrated.
dropbox.com /s/tmwphjs3muyhad9/tempFileForShare_2015-09-09-17-41-40.jpg?dl=0[/IMG]
Here are the steps I have followed.
Enabled USB debugging.
Started Downloaded mode & connected to oden.
Tried to flash CMW recovery (ticked only "F.Reset Time" checkbox & added cmw file to AP).
Product name:SM-N900
Current Binary: Samsung Official
System Status: Official
Reactivation Lock(KK) : ON
Secure Download : Enabled
KNOX Warranty void : 0
RP Swrev: A4
The program shows this:
Code:
<ID:0/003> recovery.img
<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)
Any ideas? Am I using the wrong Odin version? Or am I downloading the wrong recovery file ? Is my phone too up-to-date to be rooted? Any help is appreciated.Thanks.
1. ODIN : sh.st/cxfh7 - Odin3 v3.10.0.exe
2. CWM Recovery : sh.st/cxfvM - n900-cwm-recovery-6.0.5.0-kk(0812).tar
3. Samsung USB Drivers :sh.st/vHIqL
I used this video as a reference.
youtube.com/ watch?v=eDHSXn5KwAw

Reactivation lock must be off

Rosli59564 said:
Reactivation lock must be off
Click to expand...
Click to collapse
Thanks, but how can I do that?

I can't remember. Try google. Somewhere in the setting

Thanks

Thanks Rosli59564. Successfully rooted.

Dumb newb softbrick, Flashes dont take

got a little overzealous with some settings and made it so my phone doesn't boot past the Verizon screen. I wiped cache and didn't help, factory reset, didn't work. Tried to flash back to 0k3, finally tried to flash back to pb1. When I try pb1, it hangs at the samsung animation and when I go into recovery mode it still says system recovery is 0k3. Every rom I try to flash does not change that so I dont think my falshes are actually flashing. I'm using odin 3.10. I really just want a complete clean re-install, but cant seem to figure out how to get that to work. It's probably something very easy, but I cant find a thread that sounds 100% similar

So everything during Odin flashes looks normal, but it still doesn't take? This is very strange behavior.
Try using another USB cable/port, and if you have access to one, another computer.

Odin logs? Screenshots? Not really enough information. Maybe find a new .tar.md5?

Everything looks like it flashes normal. I've used the same files on a different device with same files and hardware and that's worked fine. It passes but when I reboot to softloader it's still ok3

kinsleia said:
Everything looks like it flashes normal. I've used the same files on a different device with same files and hardware and that's worked fine. It passes but when I reboot to softloader it's still ok3
Click to expand...
Click to collapse
Is Reactivation Lock enabled?

Nandr0idC0nsumer said:
Is Reactivation Lock enabled?
Click to expand...
Click to collapse
Its not something I've ever set and I don thave an account with Samsung. Would Odin report a "Passed" flash if it were set? I guess I'm screwed if it did get activated somehow, right?

kinsleia said:
Its not something I've ever set and I don thave an account with Samsung. Would Odin report a "Passed" flash if it were set? I guess I'm screwed if it did get activated somehow, right?
Click to expand...
Click to collapse
In Download Mode, it will say
Code:
REACTIVATION LOCK (KK): OFF
or
Code:
REACTIVATION LOCK (KK): ON

Nandr0idC0nsumer said:
In Download Mode, it will say
Code:
REACTIVATION LOCK (KK): OFF
or
Code:
REACTIVATION LOCK (KK): ON
Click to expand...
Click to collapse
Okay, its off, so not that.
Rest of info in that screen is
Product Name: SM-g900v
Current bin: Samsung official
System Status: custom (not sure what that means but it does display "Custom" with a big unlocked lock when booting, but it was doing that before it stopped working)
Qualcomm Secureboot: Enable (CSB)
rp swrev: s1, t2, r1, a2, p1
Secure Download enable
UDC start

here is my Odin log, not that I see anything unusual here:
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

kinsleia said:
Okay, its off, so not that.
Rest of info in that screen is
Product Name: SM-g900v
Current bin: Samsung official
System Status: custom (not sure what that means but it does display "Custom" with a big unlocked lock when booting, but it was doing that before it stopped working)
Qualcomm Secureboot: Enable (CSB)
rp swrev: s1, t2, r1, a2, p1
Secure Download enable
UDC start
Click to expand...
Click to collapse
Try downloading the full stock PD1 Marshmallow tar from sammobile and flashing that thru odin (slow download sry)

Nandr0idC0nsumer said:
Try downloading the full stock PD1 Marshmallow tar from sammobile and flashing that thru odin (slow download sry)
Click to expand...
Click to collapse
Will I still be able to root with stock pd1?

What is your CID? 15 or 11

Having trouble getting adb commands to work. Can only seem to get it recognized if I go into "apply update from ADB" and then its only sideloaded and flashboot just "waits for device." is their another way I can get that info without being able to boot the device up fully?

kinsleia said:
Having trouble getting adb commands to work. Can only seem to get it recognized if I go into "apply update from ADB" and then its only sideloaded and flashboot just "waits for device." is their another way I can get that info without being able to boot the device up fully?
Click to expand...
Click to collapse
Okay, so download finished and I applied it, had to reboot several times but it did come up and is now on PD1. So I guess now my question is there a way to root right from where I am, or do I have to downgrade

j7 pro cannot flash neither BL nor CSC --- AP and CP are OK

Hello
My J730G/DS was stuck in a bootloop. It wouldn't charge, and on connecting the cable it would show the Samsung-android-white-on-black and do a brief vibration, and twelve seconds later shut down and restart that.
I downloaded J730G Firmwares from sammobile.com. At one point I could flash everything in odin as PASS, but the bootloop stuck.
Then I flashed TWRP, and a new error-on-cyan appearead.
Now the phone doesnt bootloop, the screen flashes white once and goes of. I can activate odin when plugging in the cable, and it goes directly to "downloading" without pressing the up button
(Edit: I am using Odin 3.13)
Odin reads:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-730G
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
OEM LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWEV: B:3 K:0 S:1
SECURE JTAG DISABLED! ! !
Any ideas?
The phone got into the boot loop after a screen replacement. Before the replacement it was "ok" but with a broken screen after a fall

On flashing BL
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 5 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> FAIL!
On flashing CSC
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 187 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> cache.img
<ID:0/007> hidden.img
<ID:0/007> FAIL!

UPDATE: in a weird cyan-only screen that I have for recovery I get text feedback when flashing in odin
A) Flashing Flashing TWRP throws "Custom Binary (RECOVERY) Blocked by FRP Lock
B) While AP and CP are always flashable, BL and CSC mostly fail and sometimes they pass.
***
Edit: Well, after trying some many times, I declare the mobo as dead. BL flashing fails almost everytime, phone won't take a charge, and there is no stock recovery.

pppppp said:
UPDATE: in a weird cyan-only screen that I have for recovery I get text feedback when flashing in odin
A) Flashing Flashing TWRP throws "Custom Binary (RECOVERY) Blocked by FRP Lock
B) While AP and CP are always flashable, BL and CSC mostly fail and sometimes they pass.
***
Edit: Well, after trying some many times, I declare the mobo as dead. BL flashing fails almost everytime, phone won't take a charge, and there is no stock recovery.
Click to expand...
Click to collapse
You're probably just flashing the wrong firmware. You need to post a screen shot of the screen after flashing with Odin.

pppppp said:
Hello
My J730G/DS was stuck in a bootloop. It wouldn't charge, and on connecting the cable it would show the Samsung-android-white-on-black and do a brief vibration, and twelve seconds later shut down and restart that.
I downloaded J730G Firmwares from sammobile.com. At one point I could flash everything in odin as PASS, but the bootloop stuck.
Then I flashed TWRP, and a new error-on-cyan appearead.
Now the phone doesnt bootloop, the screen flashes white once and goes of. I can activate odin when plugging in the cable, and it goes directly to "downloading" without pressing the up button
(Edit: I am using Odin 3.13)
Odin reads:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-730G
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
OEM LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWEV: B:3 K:0 S:1
SECURE JTAG DISABLED! ! !
Any ideas?
The phone got into the boot loop after a screen replacement. Before the replacement it was "ok" but with a broken screen after a fall
Click to expand...
Click to collapse
did your phone show "SECURE JTAG DISABLED"??? Because my phone didn't show that one

Tomjerryrocket said:
did your phone show "SECURE JTAG DISABLED"??? Because my phone didn't show that one
Click to expand...
Click to collapse
"SECURE JTAG DISABLED! ! !"
Well, it says so!
Did you have a similar issue with your phone? not charging and on bootloop?

pppppp said:
"SECURE JTAG DISABLED! ! !"
Well, it says so!
Did you have a similar issue with your phone? not charging and on bootloop?
Click to expand...
Click to collapse
actually no:angel: