S4 soft brick - Android Q&A, Help & Troubleshooting

Hi, and I'm sorry if there is already solution but I wanted to make new thread so more people see this...Cause I don't want to do more damage...I have galaxy s4 GT-I9505 with android 4.3...Firstly I wanted android 6.0 so I installed CWM app from Google play to make backup but it cannot make it cause my phone wasn't rooted (this was all in app while phone worked normally)...So, I wanted to root it following this thread: http://forum.xda-developers.com/showthread.php?t=2219803 ...But, Odin showed Fails error (I attached error in post). I exited it and disconnected the phone...Now phone showing firmware issue, and I can enter into download mode and Odin recognizes it (version odin 3.10.7). I just want phone to work again with stock ROM, I don't want any new firmware anymore Can someone suggest what to do step by step? Again, ODIN fail error for root try is attached. Please help me. Thank you very much in advance...

Related

[Q] Galaxy S2 to stock - how to

Dear Xda-Developers and forum members,
I have some problems with my galaxy s2 and want to give it back for repair.
Therefore it is necessary to unroot the device, reset the custom rom counter and remove everything what's not stock.
I want to get the device back to android 2.3.4 and need help.
This is what I have tried :
Odin Flash Kernel (fail -> screenshot attached)
Odin Flash stock rom (fail -> same as last screenshot)
Kies firmware recovery (weird japan/chinese error message I could not ready?!)
Now I cannot use the phone at all, because it shows an firmware upgrade issue. (screenshot attached)
Can you please tell me what to do?
A step by step instruction would be great. For personal support (via im or skype) I can offer a small donation
Thank you in advance.
Tibhar said:
Dear Xda-Developers and forum members,
I have some problems with my galaxy s2 and want to give it back for repair.
Therefore it is necessary to unroot the device, reset the custom rom counter and remove everything what's not stock.
I want to get the device back to android 2.3.4 and need help.
This is what I have tried :
Odin Flash Kernel (fail -> screenshot attached)
Odin Flash stock rom (fail -> same as last screenshot)
Kies firmware recovery (weird japan/chinese error message I could not ready?!)
Now I cannot use the phone at all, because it shows an firmware upgrade issue. (screenshot attached)
Can you please tell me what to do?
A step by step instruction would be great. For personal support (via im or skype) I can offer a small donation
Thank you in advance.
Click to expand...
Click to collapse
sad to say but you have bricked your phone
if you can go to download mode then please do so and just flash another stock firmware from sammobile.com
PM me if you need help right away, i will go online on skype
other solution
saywhatt said:
sad to say but you have bricked your phone
if u can go to download mode then please do so and just flash another stock firmware from sammobile.com
PM me if you need help right away, i will go online on skype
Click to expand...
Click to collapse
Hi saywhatt,
Thank you for the reply. I habe found my problem, instead oft selecting PDA I had PHONE.
Wirth the new aosp rom my problems are gone. I dont have to give it back.
I will try to reset the counter and if it doesnt work I will let you know

[Q] rooting Samsung Galaxy Pocket Neo GT-S5310

Hello,
I've been trying to root a Samsung Galaxy Pocket Neo GT-S5310 and I followed the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=2433263
I guess the same instructions have been re-written here:
http://honai-android.blogspot.jp/2014/02/how-to-root-galaxy-pocket-neo-s5310-on.html
And someone also made a youtube video:
http://www.youtube.com/watch?v=slnvvp4gyQQ
I follow the guide and everything seems to work fine. However when I get to the last step, I get the message
Code:
E: failed to verify whole-file signature
E: signature verification failed
I guess Thailandian in the first thread that I linked to experienced the same problems, however he didn't post whether he got around the problem. It seems to me that I get the Samsung recovery instead of CWM, even though during running ODIN I get properly everything that the guide describes.
The only thing that I can think of is that when I first started my phone, I did some Samsung update, so now my splashscreen looks a bit different than the splashscreen in the youtube video above. So I'm wondering whether the provided files are not valid any more, even though my android version is still 4.1.2.
Any ideas what I am doing wrong?
Thanks a lot!
I'm guessing I posted in the wrong forum. Could someone move it to "Upgrading, Modifying and Unlocking ". Thanks.
Turn off the option to auto reboot the device on Odin and, after you flash the new recovery, reboot straight to the new recovery and flash through it.
Your device rewrites the recovery with the original one on every boot, but you can always use a custom recovery with Odin like that.
Easy way to root Samsung Galaxy pocket neo
jntesteves said:
Turn off the option to auto reboot the device on Odin and, after you flash the new recovery, reboot straight to the new recovery and flash through it.
Your device rewrites the recovery with the original one on every boot, but you can always use a custom recovery with Odin like that.
Click to expand...
Click to collapse
hey bro
Try this easy and simple method to root Samsung galaxy pocket neo http://forum.xda-developers.com/showthread.php?t=2574956
thanks to dhinesh77
Thank you. That works perfect!

[Q] Galaxy S4 firmware error! Please help!

hello forum,
im new here so sorry if this is in the wrong section!
So my problem starts here, i previously Flashed a custom OS onto my phone, Cyanogen Mod 11, when i got bored of it i decided to download the Stock touchwiz android for my Samsung Galaxy S4 i9505, i proceeded to download Odin307, once i had the OS and Odin i opened Odin in Administrator, i choose my file which was extracted and i used the PDA option to choose it, all was fine until it encountered this error (<ID:0/006> Complete(Write) operation failed.)
once that failed i tried to boot the phone where it says "Firmware upgrade encountered an issue. please select recovery mode ion Kies and try again" SO basically i can still get into the Download mode and can get to the Firmware upgrade error screen, that is all, is there a way to fix it? ive tried countless times to flash the stock touchwiz but get the same error message on odin! Please help!
What is the stock version you tied to flash?
Is the drivers installed and phone get recognised in the ODIN and device manager when in download mode?
Have you mistakenly or intentionally ticked re-partition in ODIN?
Did KIES run in background?
there is lot of threads here on XDA on same problem, try one of those our users have suggested like without closing ODIN and reflashing again.
try with another firmware file or ODIN version. here are some links I thought useful. google would help on searching "complete(write) operation failed".
http://forum.xda-developers.com/showthread.php?t=2516513
Flashing
- I tried to flash the vesion 4.3 for samsung galaxy s4 i9505 telstra.
- yes they get recognised and so odes the phone
- after various tries i tried the re-paritition btu initially i did not, only the auto boot.
- didnt have kies installed at the time of flashing
Thanks for the help, ill try tonight to get it sorted.
Mttogo said:
- I tried to flash the vesion 4.3 for samsung galaxy s4 i9505 telstra.
- yes they get recognised and so odes the phone
- after various tries i tried the re-paritition btu initially i did not, only the auto boot.
- didnt have kies installed at the time of flashing
Thanks for the help, ill try tonight to get it sorted.
Click to expand...
Click to collapse
okay, let us know update. repartitioning with pit file is last resort. its better not to play with it. bt if anything doesn't solve this, repartitioning with PIT file would be the last option to try. bt I would rather go for warranty if you have binary counter reseted.
and if you are trying to flash a rom without knox bootloader on a device that had been on knox this error is occurs mostly.

[Q] Flashing back to stock ROM from a bootloop/possible brick.

I have a Verizon galaxy note II, and had been running AllianceROM.
AllianceROM seemed to be running pretty good until one day when my accelerometer stopped working. I thought it may be a software bug, so I tried to reflash the ROM. I got a bootloop, and tried again.
I tried to flash cyanogenmod 11 and still got a bootloop. Then I realized I didn't have a safe backup.
I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm.
In the end, I'm stuck with a note II that can't boot. When I try to turn it on, I see the galaxy note II logo, but then the screen goes black (not off, I have to pop the battery out before I can try again.) Power+home+volume up now brings me to android system recovery/manual mode, and power+home+volume down gets me to ODIN mode.
Any suggestions or help would be greatly appreciated. I really wasn't planning on getting a new phone at this point, so I hope it's not beyond fixing! Thanks in advance.
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
mattnmag said:
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
Click to expand...
Click to collapse
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Ethan.S said:
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Click to expand...
Click to collapse
Yes, there's still hope to fix it if you can get the phone into download mode.
Here's some info to clarify before you try something else.... What firmware did you try to install when you used Droidstyle's guide? Also, in your initial post, you said "I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm." What firmware did you flash at that point.... was it one of the Verizon stock firmwares? And what build number was it ( 4.1.2 VRAMC3 , 4.3 VRUEMJ9, 4.4.2 VRUFND7)?
I ask this because, if you flashed 4.3 or 4.4.2, then you can no longer restore back to 4.1.2....you would have to restore back to one of those newer versions (and those newer firmwares actually lock the bootloader and install Knox security features... so that's why I was suggesting not to use them--- unless you already did before you had placed your original post for help).
If you can't restore the phone through ODIN using Droidstyle's guide, then you might try the emergency firmware recovery feature that's available through the Samsung Kies program. You can find Kies at this link: http://www.samsung.com/us/kies/
**The KIES instructions say to use Kies version 2.6 for Firmware recovery back to 4.1.2, and use Kies version 3 for Firmware 4.3 and 4.4.2.
Here's a link to Kies 3 FAQ as well: ( http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00059191&fm_seq=81528 ). Scroll down under Basic Functions and look for the link to "How do I Perform an Emergency Firmware Recovery..." The process should be similar if you plan to use KIES 2.6 instead - (that's only if you're able to restore back to 4.1.2 and you never Odin flashed one of the newer 4.3+ firmwares) .
I hope you can get it fixed. If you're not sure of things, I would suggest researching more and asking more questions before going forward. There is risk that we all take whenever we start modifying our phones, and the more knowledge we can get, the better chances of recovering from errors when we mess something up. (I know I've made plenty of errors as I've tried to learn... I even bricked my Tranformer Prime tablet shortly after receiving it from EBay :banghead: ). If worst comes to worst, you might end up having to pay someone to do a Jtag repair to unbrick it.... but let's hope it doesn't come to that.
Also-- you could try Verizon's Software Upgrade/Repair Assistant found here: ( http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/ ). I have no idea what the differences are between Verizon's software repair assistant and Kies.... **

[RESOLVED] Help upgrade a SHV-E160S 4.0.4 IMM76D.VH29 to latest??

Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Hello guys, any ideas? Thanks!
jakeortega said:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Click to expand...
Click to collapse
Hello guys, any ideas? Thanks!
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
es0tericcha0s said:
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
Click to expand...
Click to collapse
Thank you es0tericcha0s for this information.
What I'm trying to do right now is updating my SHV-e160s from 4.0.4 to 4.1.2 using Kies v2.6. Unfortunately, I'm getting this error "Failed to run firmware upgrade: unknown error.". Until now, I'm afraid to update my firmware manually as I don't have much knowledge to do that.
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Alright, I'll try these steps immediately and will comeback for the result. Thanks again.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Hello, sorry I forgot to ask, will this root my device? I'm afraid I might bricked it.
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
es0tericcha0s said:
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
Click to expand...
Click to collapse
Hello again es0tericcha0s, I haven't tried the instructions that you gave me yesterday as I'm still downloading the firmware, last night I encountered an issue after enabling my Bluetooth, something like "NFC Service has stopped." just keeps on popping up. So I turned off the bluetooth then restarted my phone, it went well for a while.
After that, I enabled my 3G Cellular Data to check what was NFC service error is, after a few minutes, I lost my signal, phone turned to No Service, then in Settings -> About Phone, I got an Unknown Baseband.
EDIT
I got No Service since last night up until now.
EDIT Oct. 13, 2015 9:49 AM +08:00 Manila Time
I manage to update my phone from ICS 4.0.4 to JB 4.1.2. But still, my baseband is Unknown and I have no signal.
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
es0tericcha0s said:
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
Click to expand...
Click to collapse
I also though of that, hopefully not.
When I first got the phone, my gf sent me our pictures via bluetooth , no issues occured. After a while, I noticed that there are so many photos of the previous owner (around 1000+) and mp3s (around 1000+ also). So I connected the phone via usb to my pc and deleted all those pictures and mp3s inside the My Computer -> SHV-E160S -> Phone (Computer\SHV-E160S\Phone). After doing so, I started to encouter some issues, when enabling the bluetooth, the phone hangs and reboots then the error 'NFC service has stopped' keeps on popping up, until it went Unknown Baseband.
Now, the phone keeps on rebooting similar to the symptoms that it gets when baseband version is unknown.
I'm looking for solutions to fix the unknown baseband and saw the Back up and Restore EFS, I just need to root the device to try this fix. Maybe I'll post an update whether if I manage to solve this problem or not, if it didn't fix the issue then maybe the problem is the baseband chip. what a crap!
This is my reference for the EFS Fix
http://techbeasts.com/2014/07/13/fix-samsung-galaxy-unknown-baseband-version-guide/
Thanks!
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
es0tericcha0s said:
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
Click to expand...
Click to collapse
So I need to install TWRP first before rooting the device? Also I'm planning to use a rooted stock firmware which is 4.1.2, I just don't know the difference between UH24 and MH2, I've read that UH24 is already old and it's better to use a MH2 build and what is the Recovery UH24/MH2?
EDIT:
I forgot, I cannot check my current Baseband since it is still unknown.
EDIT: 12:30PM +8:00
I managed to get my Build#, it is MH2, I'm currently looking for a rooted 4.1.2 MH2 download link.
Way faster and easier to use the method I outlined, but either way should work.
es0tericcha0s said:
Way faster and easier to use the method I outlined, but either way should work.
Click to expand...
Click to collapse
Sorry, I'm really a root virgin here. While following your advise, I'm also currently looking at this guide -> http://forum.xda-developers.com/showthread.php?t=1924535. I'm done downloading Tegrak for MH2, a small problem I encountered here is I don't have a folder named 'sdcard' in my phone, so I created one and copied the 'Kernel' .zip, also I copied it to usbStorage folder.
I'm about to flash the 'Recovery' .tar to my phone. Hoping a success result
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
es0tericcha0s said:
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
Click to expand...
Click to collapse
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
jakeortega said:
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
Click to expand...
Click to collapse
Finally! I'm done rooting my phone, though I encountered another issues again. My Menu Button and Back Button does not work.
UPDATE: 4:08PM +8:00GMT
I think I found the problem as to why my Menu button and Back button doesn't work. I'v check my Baseband and it is -> E160SKSJMH1 and my Build # is -> JZO54K.E160SKSJMH2. Am I using a wrong FW as supposed to what I should be using? Which build should I install, the MH1 or the MH2?
Also, the Tegrak Kernel I've used is Build 48 for SHV-E160S MH2. I've also tried factory resetting the phone but the issue still exists.
Thanks!
UPDATE: 4:41PM +8:00GMT
Managed to fixed the issue by updating my Touch Firmware. Cool!

Categories

Resources