Post Reply

[Q] Soft bricked SM-N9005...HELP

OP bcsiy

21st May 2014, 07:23 AM   |  #1  
bcsiy's Avatar
OP Senior Member
Thanks Meter: 6
 
103 posts
Join Date:Joined: Sep 2010
More
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted

I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.

I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.

Any help and inputs would be greatly appreciated.
21st May 2014, 07:47 AM   |  #2  
Misterjunky's Avatar
Senior Member
Flag Bakersfield, California
Thanks Meter: 2,682
 
4,770 posts
Join Date:Joined: Jan 2011
Donate to Me
More
Thumbs up re: factory data reset
Quote:
Originally Posted by bcsiy

SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted

I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.

I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.

Any help and inputs would be greatly appreciated.


If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.


Good luck!
Last edited by Misterjunky; 21st May 2014 at 07:51 AM.
21st May 2014, 08:19 AM   |  #3  
bcsiy's Avatar
OP Senior Member
Thanks Meter: 6
 
103 posts
Join Date:Joined: Sep 2010
More
Unhappy
Quote:
Originally Posted by Misterjunky

If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.


Good luck!

I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.
21st May 2014, 08:41 AM   |  #4  
radicalisto's Avatar
Senior Member
Flag York
Thanks Meter: 1,449
 
3,576 posts
Join Date:Joined: Nov 2013
Donate to Me
More
Quote:
Originally Posted by bcsiy

I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.

Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)
21st May 2014, 09:06 AM   |  #5  
bcsiy's Avatar
OP Senior Member
Thanks Meter: 6
 
103 posts
Join Date:Joined: Sep 2010
More
Question
Quote:
Originally Posted by radicalisto

Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)

Thanks for the input, the main issue why I need to flash the stock rom is because the phone doesn't boot and is looping in the Samsung Galaxy Note 3 screen then vibrates as if it turns on again and goes into a loop...

Question is can I flash a custom rom over it for example there's no firnware loaded on the phone or the firmware loaded is corrupted?
21st May 2014, 09:16 AM   |  #6  
radicalisto's Avatar
Senior Member
Flag York
Thanks Meter: 1,449
 
3,576 posts
Join Date:Joined: Nov 2013
Donate to Me
More
You can flash a custom ROM yes, so long as you boot Into your custom recovery, do the wipes. Then installing a custom fw should work OK, once you've done that you can go back to stock or change custom fw without issues

I'm UBER Paranoid
21st May 2014, 11:54 PM   |  #7  
toastido's Avatar
Senior Member
Flag Huntsville, AL
Thanks Meter: 542
 
649 posts
Join Date:Joined: Oct 2013
Donate to Me
More
Quote:
Originally Posted by bcsiy

SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted

I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.

I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.

Any help and inputs would be greatly appreciated.

The reason it wants to boot into recovery is to flash the csc. Make sure you get the correct firmware for your device and region from sammobile.com and odin again, let it do its thing. It sounds like the csc wasn't valid.

Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy Note 3 Q&A, Help & Troubleshooting by ThreadRank