Few days back, i decided to get busy with my Samsung galaxy note, precisely the Korean version shv-e160s.
My main intention was to root the phone and possibly install any custom rom like i successfully did with the Sony Ericsson xperia x10i. Normally, rooting any device isn’t a big deal for me.
The Sony Ericsson Xperia x10i proved it so. I even ended up bricking that device twice and i fixed it. Easily installed custom roms and more. I can actually attest to the fact that i really did a lot of tweaking on that smartphone device and enjoyed it before it was stolen few months after purchase.
I actually wanted same for the Samsung galaxy note and that’s why i had to resort to rooting first. As usual, i did a lot of research over the internet and all steps seem the same. Guess they all copied from xda forum but guess what, they didn’t work for me.
Now, just before i commenced the rooting process, i wanted to update the software version of the phone. Since i couldn’t achieve that using the inbuilt OTA update functionality, i thought about using the Samsung Kies software on my laptop computer.
I downloaded and installed Kies from the Samsung website because the phone cannot be detected when connected to the computer via usb without the kies and drivers installed hence, installing kies was a necessity.
Upon successful installation and launching, i connected the samsung galaxy note shv-e160s phone to the PC via USB and on the samsung kies software, i got a prompt message stating that a firmware update for the phone was available. Without hesitating, i quickly choose to update.
As expected, the software needed to download the firmware update version for the galaxy note via its servers and this took quite a long while. Just when the update was to be transferred to the phone, an error prompted up and my phone stopped working.
By then, i knew the phone was probably bricked. All that was shown after the odin mode and phone model details was a symbol of a phone and computer with a connection interrupted sign in-between.
There wasn’t a need to picnic and Samsung kies software called for an emergency firmware restore. I wasted no time and choose the option. This took another long while but nothing changed. I repeated same process like twice and burning off over 2GB of data bundle yet nothing changed.
Okay, at this point i was a little scared that i must have spoilt the phone but then, i knew there was always going to be a solution and for that, i had to go using a method i would term as ‘trial by error‘.
At that point, i had nothing to lose but maybe something to gain. So, it’s game on!
How I Fixed/Repaired BrickedSamsung Galaxy Note SHV-E160S/L/K Stock Firmware
Now, i know i probably bored you with a long story there but I won’t be doing that on this part. I am just going to state how i fixed it and if you are in same situation, you should follow my steps.
- First, i downloaded Odin v1.8 here and extracted it to a folder on my laptop computer.
- I also downloaded the phone model-specific Tegrak “Recovery” file for the galaxy shv-e160s using my PC.
- Next, i fixed the galaxy note on download mode by pressing the volume down button + home button + power button together. It came up with some Korean writings and I simply press the volume up button.
- Next, i connected the phone to the computer using the usb cable and waited for it to signify on the Odin software. At this point, i had completely closed samsung kies software. Looking at the odin software, you should find a yellow “0:[COM__] which signifies the device has been detected.
- Moving on, i made sure only the “Auto Reboot” and “F Partition Time” are checked
Next, i clicked on PDA and selected the tagrak recovery file i had downloaded on my computer
- After successful selection, i clicked on start and waited for the process to be completed till the galaxy note phone reboot automatically with a PASS signal clearly shown on odin and this time, the phone worked well again.
Now, this same step can be applicable in fixing the galaxy note shv-160L and K versions. All you need to do is download the specific Tegrak “Recovery” file for your phone model. You can verify this by navigating to settings > about device.
Experiencing an SMS limit on the Shv-e160s? There is a fix for that here.
In the process of trying to root my samsung galaxy note shv-e160s, the phone stopped working. How Do I Fix it?
Simply follow the whole repairing process above. I have specifically confirmed this working on my Samsung galaxy note shv-e160s and it worked fine in repairing the stock firmware of the galaxy note device. If you’ve got any questions, I am sure you know what to do :).