So you created a nandroid backup and then restored it successfully?It was a FULL Restore ... everything.
Peter
I hope this works via external SD as well
Sent from my SM-N900W8 using Tapatalk
So you created a nandroid backup and then restored it successfully?It was a FULL Restore ... everything.
Peter
I forgot to mention yesterday that I have restored successfully from internal and external sd. Also flashed my rom from both. All good. 9005 by the way.So you created a nandroid backup and then restored it successfully?
I hope this works via external SD as well
Sent from my SM-N900W8 using Tapatalk
Thank you for your feedback.I forgot to mention yesterday that I have restored successfully from internal and external sd. Also flashed my rom from both. All good. 9005 by the way.
Sent from my Sweet Rom powered SM-N9005
I have not met you this situation, I just tested a few times, after the update app process, the phone can start properly .In my testing and messing around with the CWM on 2x Note n9005 I found out that the Wipe Cache And Wipe Dalvik Makes the units do 3X Bootloops or even continues bootloops. Don't Use the Wipe Cache And Wipe Dalvik . The good news is if you have a nandroid backup before the Wipe Cache And Wipe Dalvik the will fix the bootloops. Hope that helps !
Can't confirm this. I wiped cache and dalvik and had no bootloops.In my testing and messing around with the CWM on 2x Note n9005 I found out that the Wipe Cache And Wipe Dalvik Makes the units do 3X Bootloops or even continues bootloops. Don't Use the Wipe Cache And Wipe Dalvik . The good news is if you have a nandroid backup before the Wipe Cache And Wipe Dalvik the will fix the bootloops. Hope that helps !
Boot back in download mode and flash stock fw for your deviceGuys my Note 3 is stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVIATION LOCK: ON
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
Any advise?
Tried Skies 'Emergency Recovery' - FAILED
ODIN - Official Firmware - FAILED
I had the same thing happen to me just from flashing a recovery via Odin. It froze half way on flashing, so i pulled the plug and got that error. I just booted back in download mode, and in my case re-flashed the recovery and it passed, booted back up fine.This is the only mode I can boot to.
I can boot to 'Download Mode' now, had to pulled out the battery.I had the same thing happen to me just from flashing a recovery via Odin. It froze half way on flashing, so i pulled the plug and got that error. I just booted back in download mode, and in my case re-flashed the recovery and it passed, booted back up fine.
What exactly caused your softbrick? Did you flash anything or do a restore?I can boot to 'Download Mode' now, had to pulled out the battery.
Skies - Recovery still fails
ODIN - Original Firmware fails too - screenshot posted
I think I may have soft-bricked my phone![]()
1) I rooted using 'Root de la Vega', flashing 2 files AP and CSC - This went fine and the Note 3 was rooted.What exactly caused your softbrick? Did you flash anything or do a restore?
Sent from my SM-N900T using Tapatalk 2
Pull battery put battery back In and restart the device from download mode1) I rooted using 'Root de la Vega', flashing 2 files AP and CSC - This went fine and the Note 3 was rooted.
2) Flashed 'Vega' ROM' SM-N9005XXUBMJ3-OXABMJ1-ROOT-DE-LA-VEGA-ODEX - As I wanted to removed Samsung bloatware - This went fine
3) Flashed CWM - n9005-cwm-recovery-6.0.4.4(1011).tar - As I want to flash custom roms - This went fine
4) Flashed ' X-NOTE build 2.0 N9005 MJ1 (europe)' - Wanted to try this rom, this went fine
5) Flashed back to 'Vega' ROM' SM-N9005XXUBMJ3-OXABMJ1-ROOT-DE-LA-VEGA-ODEX - This went fine
6) Ran 'Samsung GALAXY Note 3 Cleaner v0.4' - This went fine, no errors (Samsung Apss removed)
7) Flash CWM - n9005-cwm-recovery-6.0.4.4(1011).tar - As I want to flash custom roms - This errored 'Must let Reactivaion Lock off first(Settings--General--security) - I did this but the system settings crashed several times.
Since then I have tried Skies Emergency Firmware Recovert with Code and Odin 3.09 - Stock Firmware - Both Failed.
I think the device is in write-protected mode.
Status of by boot screen
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVIATION LOCK: ON
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
And a red line comes up after the failed flash attempt
SECURE CHECK FAIL[FMM] : cache
I have done that. - Skies and ODIN still fails.Pull battery put battery back In and restart the device from download mode
Sent from my SM-N900T using Tapatalk now Free
Hmm good thing that's unchecked for me by default, I actually forgotten about that myself! So it stays unchecked correct?yes because you have forgot too uncheck reactivation lock in setting.
"REACTIVIATION LOCK: ON"
The best course of action would be to factory reset and/or reflash stock firmware after all that bad flashing and start over from scratch. And dont forget to uncheck reactivation lock when your done! But glad your booting up now.OK - I did deselect that but the settings application crashed several times, so that wasnt deselected.
I have flashed Stock Kernel MJ3, the phone boots normally but requires 'Reactivation'. Dont remember activating previously, but the phone is unstable, I cant enter an email / password as the Samsung Keyboard crashes.
I will continue tomorrow.