Database Users

[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

[RESOLVED]Recovery help

RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse

As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium

jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.

So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium

when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck

Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?

xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?

Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.

jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!

Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.

jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:

Good deal
Sent from my GT-I9505 using xda premium

Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:

Can not flash mf9 stock firmware.

Ok. After 24hours of no sleep i finally recovered my phone from the soft brick state it was after i flashed the wrong kernel when i was in stock 4.3.Now am back to sacs 8 though no wifi works and phone is rebooting and fc everything. I want to flash back to stock 4.2.2 but odin refuses. If you need any logs to be generated so you might help please tell me exactly what you need and ill provide

tasked28m said:
Ok. After 24hours of no sleep i finally recovered my phone from the soft brick state it was after i flashed the wrong kernel when i was in stock 4.3.Now am back to sacs 8 though no wifi works and phone is rebooting and fc everything. I want to flash back to stock 4.2.2 but odin refuses. If you need any logs to be generated so you might help please tell me exactly what you need and ill provide
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2508411
Sent from my SPH-L720 using xda app-developers app

what did you do? im trying to use KIES but i dont have the serial.. can you msg me your serial so i can atleast get KIES to download the software? msg me

Kies won't work if u updated to 4.3. Kies 3 won't work either. If u soft bricked ur phone flash the cf auto root tar. It will fix ur error. We're just stuck with 4.3 for now.
Sent from my SPH-L720 using XDA Premium 4 mobile app

kies wont do anything. After 4.3 update we can not downgrade. My issue is i cant boot into stock 4.3. I can only flash octos or other roms but with phone not working and problems as such.

ok somehow i fixed this. I followed the instructions using twrp recover. Only difference is that after i recovered modem and radio through custom twrp method, i used cf autoroot to get stock recovery back then used the update.zip posted in another forum, to update through sideload and it worked. Back in stock 4.3.

tasked28m said:
ok somehow i fixed this. I followed the instructions using twrp recover. Only difference is that after i recovered modem and radio through custom twrp method, i used cf autoroot to get stock recovery back then used the update.zip posted in another forum, to update through sideload and it worked. Back in stock 4.3.
Click to expand...
Click to collapse
which update.zip?

slackwaresupport said:
which update.zip?
Click to expand...
Click to collapse
the 4.3 update.zip that got pulled out of someones phone before he fully updated from 4.2.2 to 4.3. You can find the zip file in the General section i think.

I was on stock 4.2.2 got the update and went to 4.3. Then i flashed a 4.3 tw kernel and everything got screwed. After that i went followed the instructions found here http://forum.xda-developers.com/showthread.php?p=47113608#post47113608. First i recovered boot , then system , then modem then radio through twrp using the files found there. After that i booted used the cf auto root to go back to stock recovery. Phone was still doing the boot loop up to this point. Then i figured out that the backup was probably a 4.2.2 backup so i used adb sideload to install update.zip. After that i wipe data/factory reset and it booted just fine. Ok lost everything but phone works now like new.

Philz Touch problem! Please help!

I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)

bounddyy said:
I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
Click to expand...
Click to collapse
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5

leaderbuilder said:
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
Click to expand...
Click to collapse
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?

bounddyy said:
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
Click to expand...
Click to collapse
If you can get into recovery now (philz). You can certainly flash Sac's 4.3. If you want the mf9 modem that is in the dev section too. Check out Unknownforce's post
But I suspect you've taken the mja "firmware" and tripped that Knox counter, and if that's the case I dint believe you can Odin back to mf9.
Sent from my SPH-L720 using XDA Premium 4 mobile app

Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app

bounddyy said:
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
well that didn't workout so i figured out that i shouldnt let my phone reboot after flashing Philz recovery and instead directly force into recovery and it worked but now i need to just flash it thourgh there lol

[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