Database Users

Is my phone bricked?

Earlier today I was trying to install the 4.3 Slim Bean Build.1. I was coming from the latest 4.2 Slim Bean ROM. So I did the usual process of wiping everything then installing the ROM and then the GApps. When I rebooted the system from recovery, my phone was just stuck on the Samsung Galaxy S4 loading screen. Now I cannot even boot into recovery, as every time I try to, it will show that the phone is attempting to boot into recovery and then it will just reset. I had TWRP touch recovery installed and everything was working fine until I tried installing this ROM. Are there any suggestions of what I can do/should do? Thanks in advance for any help.

Can you get in download mode(power+vol. Down) if so use odin to flash back to stock.
Sent from my SPH-L720 using XDA Premium 4 mobile app

Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you

klgd said:
Can you get in download mode(power+vol. Down) if so use odin to flash back to stock.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you

On my way to work so cant spend any time helping, but there are sevral guides and you will lose root.
Sent from my SPH-L720 using XDA Premium 4 mobile app

Might just b able to Odin recovery...
Sent from my SPH-L720 using xda app-developers app

Download Odin and the latest firmware for your device,extract firmware zip file,it will extract in tar.md5 file.now extract Odin and run the Odin application and connect the device while it is in download mode. click on PDA and load the firmware extracted file. Don't touch anything other than that click on start and leave for some time to complete.
Samsung lies should be installed before the process start.
Download firmware file from sammobile.com.
Your device will be automatically unrooted.
Sent from my GT-P3100 using xda app-d,evelopers app

youngnick09 said:
Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you
Click to expand...
Click to collapse
yes you will have to start all over. here is a video on how to use odin on the s4. http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&ved=0CDMQtw IwAQ&url=http://www.youtube.com/watch?v=hZTTTk7vbVM&ei=3t05UtijLdTc4APV-YDQBw&u sg=AFQjCNGIjlBz9Xgj57ytF2NCGYchd7V1Xg&sig2=hhLZZzmRyDFyxETPrzCmfw&bvm=bv.522881 39,d.dmg make sure you get a stock .tar file found here http://forum.xda-developers.com/showthread.php?t=2338919. make sure you watch the video before you do anything. also this thread belongs in Q&A.

thank you guys

I have run into a similar issue and was able to get into recovery by pulling the battery for about 5 minutes then using the hardware keys to boot into recovery.
Sent from my SPH-L720 using Tapatalk 4

[Q] HELP! Stuck in soft brick!

Can someone please help me get out of this soft brick because I am really stuck. Currently I am getting the error message that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." but I have done that and it has failed on both mac and windows 7. I have also tried flashing stock build UCUAMDL 4.2.2 firmware via odin 1.7, 1.85 and 3.07 and I have also used the PIT files along with re-partitioning and F. Reset Time. Every single time in odin it has gotten to system.img.ext4 and then failed immediately following. A couple of times I have been able to get into stock recovery mode and it stated an error that the /system partition could not be accessed and I wiped cache/system/data and then tried rebooting and it stayed in the big white galaxy s4 letters and didn't even go to the boot logo. Based on this can anyone help me please???? If there's an existing thread can you please let me know? Thanks!

Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

sounds like you wiped your phone when you wiped system/data, why did you do that
you have nothing to boot
kies don't work with iMac
yeah give all the phone info you have, model, build, etc. build may be on your box
i think you can now only flash stock firmware thru Odin to recover, but if you were mf3, you may need to go to bestbuy and see samsung reps to flash phone. don't have any experience at that or using odin
stay on windows pc to do this
may be tomorrow till you get some help from others
good luck

RAID Xero said:
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sorry I forgot to mention that it's a SGH-I337 as well and I was running the jamal 4.3 AOSP ROM

well then you are with what custom recovery?
and you are not mf3
sounds like the mf3 update was trying to flash. did you not delete the update files with Titanium so the Update would not run
can you boot into recovery and restore a nandroid
---------- Post added 2nd October 2013 at 12:00 AM ---------- Previous post was 1st October 2013 at 11:54 PM ----------
i gotta call it a nite. maybe some west coasters can help since they are 3 hours behind us
but, please don't say you don't have a nandroid--
i think this is fixable--:good:

restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app

Kelevra_96 said:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you have an i337. We don't have fastboot. Our bootloader is locked.
Sent From My SGH-I337 Using Tapatalk 4

What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app

Br4nd3n said:
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?

adambombz said:
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
Click to expand...
Click to collapse
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.

jd1639 said:
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
Click to expand...
Click to collapse
I was running a custom ROM AOSP 4.3 that's all I know sorry

adambombz said:
I was running a custom ROM AOSP 4.3 that's all I know sorry
Click to expand...
Click to collapse
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.

also, if you are running a custom rom you have a custom recovery
cwm or twrp?

jd1639 said:
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
Click to expand...
Click to collapse
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.

rugmankc said:
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
Click to expand...
Click to collapse
They key word here is that I WAS running a custom recovery when all of this started. It was actually the recovery that started all of this. What happened specifically was I tried to update TWRP via goo manager and whenever I tried to go into recovery it gave me the error that at&t has detected unauthorized software on my phone which I thought was weird because I believe that goo manager auto-lokis. Anyway I tried using other apps to add a custom recovery like ROM manager by clockworkmodz and nothing worked. I then tried to flash TWRP 2.6.3.0 via odin and that's what sent my phone into the state that it's in now. Something that confuses me even more is is that whenever I plug in my phone a battery logo comes up that I don't recognize and then freezes.

adambombz said:
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
Click to expand...
Click to collapse
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file

When you get it sorted use twrp 2.5.0.2. I think I posted a zip for you.

jd1639 said:
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
Click to expand...
Click to collapse
Yes I have tried multiple files and builds and I am using .tar.md5

adambombz said:
Yes I have tried multiple files and builds and I am using .tar.md5
Click to expand...
Click to collapse
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.

jd1639 said:
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
Click to expand...
Click to collapse
That is possible, I know what is causing this has something to do with the partitions being messed up since I can't access /system in the stock recovery mode

[Q] So many issues... (Kies, Recovery, Firmware)

Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?

Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app

ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?

whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help

whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup

which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)

leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped

Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app

[Q] Bricked my Galaxy S4, stuck on boot screen

I apologize in advance for my lack of knowledge and understanding. I recently flashed a custom rom on my Galaxy S4, and it worked but I noticed the Wifi wasn't working, so I attempted to get it to work by trying again. It ended up badly, and it's now been stuck on the boot screen for a while. I tried doing a factory reset and wiping the cache partition, but it was still stuck on the screen. I can also still get onto download mode, so I'm hoping that means I can still save my phone.. I'm also not worried if I lose my internal storage, considering I'm just desperate to get my phone working again. I have an SGH-I337 AT&T phone.

What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!

Daze_ said:
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Click to expand...
Click to collapse
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'll try that. Also, this was the first time I've ever flashed a rom, and I'm unsure if you would consider it successful, since the wifi wasn't working, but besides that, I saw no issues.

I had to go this same route when I was messing around and soft bricked like you. It's not hard to recover following the instructions . Odin the NB1 stock tar, let phone boot to ensure it is alive again. Then use the built in recovery to install the NC1 update. Reboot and you are ready to towelroot/supersu/safestrap.
Don't worry. It will be ok!
Sent from my SAMSUNG-SGH-I337 using Tapatalk

[Q] S5 SM_G900F lollipopXXU1BNL9 TWRP install fail

Please help!!!!
I have a SM-G900F S5.
Just updated to XXU1BNL9 Lollipop.
Not clean install, I upgraded it. All official releases from Sammobile, done with Odin 3.09.
Upgrade went all ok, fine, up & running.
Tried to install TWRP 2.8.4.0, also with Odin 3.09
10/10 times it fails with write error.
Any ideas???
Would like to root my phone, so this first step would be really necessary!
Thx!

I fixed Odin fail with a pit file...
Download pit fie for your device...
Open Odin... Flash firmware
When Odin fail... Unplug cable... Plug it back... Uncheck that box with pda (and leave it there) ... Load pit file... And hit start even if the error is still there... After U hit start button It should finish and auto reboot
I USED THIS METHOD JUST FOR FIRMWARE FAIL... I DON'T KNOW IT WILL WORK WITH CWM FAIL in Odin
Also... You should try to download again twrp... Or another source... Version... Etc im sure that the error it's because of the cwm file
Sent from my SM-G900F using XDA Free mobile app lolipop android

Thx for the ideas, I will try them.
I tried to unplug-replug cable, download other TWRP, also from different sources.
Seems as if it was some writing authentication issue of some kind - but no idea, why.
Sent from my SM-G900F using XDA Free mobile app

sandor.korn said:
Thx for the ideas, I will try them.
I tried to unplug-replug cable, download other TWRP, also from different sources.
Seems as if it was some writing authentication issue of some kind - but no idea, why.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
For me... The solution was pit file... Did u tried what I say? Step by step....but instead of firmware u can put Cwm...
Strange I've never seen such a error... With cwm
Sent from my SM-G900F using XDA Free mobile app

terrorblade23 said:
For me... The solution was pit file... Did u tried what I say? Step by step....but instead of firmware u can put Cwm...
Strange I've never seen such a error... With cwm
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
I tried everything else expect the pit file.
I did not find a pit file for the XXU1BNL9 version.
Also, I did not find ClockworkMod for Lollipop, only for 4.4.x
So, I triedTWRP 2.8.1.0 and 2.8.4.0 - both ending the same way: The recover flashing starts with Odin, and then it is almost immadiately fails with some write problem. It seems as if the recovery tar.md5 is not compatibl with the ROM version, or as if some mysterious Samsung protection would reject the recovery flash.
Strange thing is, that all forums (e.g. droidviews, ibtimes, xda, etc.) give a description about rooting this ROM, and not even one mentiones any phenomenon like this.