Related
I flashed my fascinate back to stock with odin and now when i boot up i just get a ton of force closes and they keep coming up and wont let me continue. Any help would be appreciated. Thanks
You should have posted this in the General section.
Now, what did you flash to stock from? Were you using voodoo beforehand?
IME, FC hell after an odin restore is due to the PIT file not being used.
Open Odin
Go back into Download Mode on your phone.
Hit the PIT button and select the PIT file you downloaded from the OP of the odin topic.
Hit the PDA button and select the "system" tar you downloaded from teh OP of the odin topic.
Hit Start.
Wait for it to finish (system takes a bit).
Reboot into recovery and wipe data/cache.
Sorry for posting in the wrong section and i was on vodoo and removed it and flashed a differernt rom was most recently on the zinc rom. i also tried to re run odin with pit and still force closeing. thanks for the help so far
swerve12 said:
Sorry for posting in the wrong section and i was on vodoo and removed it and flashed a differernt rom was most recently on the zinc rom. i also tried to re run odin with pit and still force closeing. thanks for the help so far
Click to expand...
Click to collapse
Only other thing I can think of off the top of my head is wiping data/cache from both Stock and CWM recovery. You could also try wiping dalvik cache (CWM-advanced) or nuking the contents of dbdata...but that requires either adb or root access and a phone that isn't constantly fc'ing on you.
Have you tried restoring a nandroid backup?
If he was on vodoo then he write have to flash back to a vodoo kernel and then make the disable lagfix folder and reboot. Then revert to stock kernel right?
Sent from my SCH-I500 using XDA App
I think that a good question here would be whether or not you had voodoo installed. Tell us what you are/where running so we can diagnose and help u work through the problem. No worries though, this can be fixed.
Sent from my SCH-I500 using XDA App
ok so orignally flashed vodoo and when it was first put out then i (what i thought was) removed vodoo and flashed the Zinc V2.1.3 Fascinate Rom then i went from that to Blackhole Version 1.2 Rom after i flashed to blackhole and before i did any restore of apps i had 0 internal mem left and couldnt figure out why so i decieded to run odin to put the phone back to 100% stock and now all fc's
I had the same issue today, to gix it I booted to recovery and did "factory reset" it wiped the data and no issues since. I have also changed to the atupid fast kernel instead of voodoo. Hope it helps. I suggest you try it...
Sent from my fascinating fascinate
Hey guys, new rooter here, hopefully somebody can help me out...
So I was running stock DL18 Eclair, decided to flash Baked Snack 1.6 (babystep.zip).
I rooted, installed Clockwork Recovery, made a backup and everything, as well as backed up with Titanium backup.
I loaded babystep.zip onto my sdcard and flashed using Clockwork. Install was successful, but when I rebooted the phone it hangs on the Samsung loading screen. I tried reflashing, to no avail. I also tried step2.zip, another kernel version of baked snack, no go.
So then I tried reflashing my backup from clockwork recovery. That didn't work either, same problem, just hangs on the Samsung screen.
Does anybody have any advice, or did I brick my phone and now I have to do a factory reset using odin?
anti09 said:
Hey guys, new rooter here, hopefully somebody can help me out...
So I was running stock DL18 Eclair, decided to flash Baked Snack 1.6 (babystep.zip).
I rooted, installed Clockwork Recovery, made a backup and everything, as well as backed up with Titanium backup.
I loaded babystep.zip onto my sdcard and flashed using Clockwork. Install was successful, but when I rebooted the phone it hangs on the Samsung loading screen. I tried reflashing, to no avail. I also tried step2.zip, another kernel version of baked snack, no go.
So then I tried reflashing my backup from clockwork recovery. That didn't work either, same problem, just hangs on the Samsung screen.
Does anybody have any advice, or did I brick my phone and now I have to do a factory reset using odin?
Click to expand...
Click to collapse
How long did you give it on the first boot? Sometimes the first bootup takes a really long time.
Worst case, just do an odin restore with DI18 and then restore with your clockwork backup. Would take like 15 min and you'd be right back to where you were.
How long is really long? I probably gave it a good 5 minutes before restarting.
And I was on my way to doing a factory reset with odin now... where do I insert the .pit into odin? I don't see a pit section
I'm not too familiar with Baked Snack.. is that the kernel file or the rom that you were flashing? Or does it only need the one .zip file?
Sent from my SPH-D700 using XDA App
Baked Snack is a kernel only, it uses the stock Dl18 rom.
Honestly by this point I'm just trying to do a factory restore, cause after re-flashing with my clockwork recovery (which also didn't work) I can't even access my sdcard anymore.
Odin recognizes my phone but I don't see anywhere to insert the .pit file... I'm using Odin Multi Downloader 4.3, is that the right program?
Edit: If somebody felt like helping me over AIM, it would be much appreciated! S/n is anticrombie0909
I dont know what you are using but u should be usind odin3 v1.61 and the pit file goes right above the pda but you dont need the pit file. Just use the tar file and make sure its the approp. Size. Depending on what stock rom you downloaded it should at least be 255mb. And insert the rom in pda section and make sure only reboot is the only thing checked.
Sent from my Evo killer!
Can someone please link me to that version of odin? And why don't I need the .pit file? Finally, do I need to reflash the entire ROM, or only the kernel?
Odin MultiDownloader is an older tool than Odin3 that really isn't meant to be used with our phones. Use Odin3 1.61.
And you should be able to get by without a pit as long as your partitions are still properly partitioned.
Ok, so I managed to do a factory restore using odin, back to stock.
I tried reflashing baked snack again, but it looks like it's hanging on the Samsung screen again... here's exactly what I did, step by step.
1. Wiped my phone, clean Dl18 stock install.
2. Installed Rom Manager, flashed clockworkmod install. Loaded babysteps.zip (the kernel file) onto sdcard.
3. Ran clockwork manager, picked "select file from sdcard," flashed the kernel, which was successful.
4. Went back to clockwork manager's main menu, selected "reboot phone."
Once again, it's hanging on the Samsung loading screen. I've let it sit for about ten minutes now, no change. What am I doing wrong?
You're flashing babysteps, which doesn't work with all phones. Do something a little more mild. Also there is a rom, you know, and the kernel runs better with his custom rom.
Sent from my SPH-D700 using Tapatalk
So should I try something like worksforall.zip? Or should I just go ahead and install the whole bakedsnack1.6 rom + kernel combo? And if I do the latter, is it the same process (load onto sdcard, go to clockworkmod, install and reboot)?
be careful with it. I did works for all and then rebooted to do step 2 and mine hung samsungmobile.com screen. It took me about a week to fix it as i was having checksum errors, odin screwups, driver issues, clockwork problems, boot problems. Any problem that could happen happened to me. Im currently fixed and restoring my nandroid after using odin, im probably gonna wait for a better build and i suggest you do the same, but it would be probably easier for you to fix yours than me to fix mine
So I ended up installing the entire Baked Snack 1.6 kernel + rom, which seems to be working great now. Thanks for your help everyone, this thread can be deleted.
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
**EDIT**: Just did format on /data on stock recovery and it seems to have booted... False alert guys. Soft bricked, but nothing else.
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Blaze9 said:
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
Click to expand...
Click to collapse
Did you try factory restore / reset in recovery?
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
goobieracing said:
Did you try a factory reset in stock recovery? Or maybe try odining the pit file also that somewhere on the forum. Maybe your partitions got corrupt flashing some how.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
goobieracing said:
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
scott14719 said:
Did you try factory restore / reset in recovery?
Click to expand...
Click to collapse
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
Click to expand...
Click to collapse
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
I had to do a stock reset recovery the other day for something like this. Probably just left over files from previous stopping it from booting.
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
Click to expand...
Click to collapse
Sorry I learned something new today. Back in the infuse 4g days whenever I'd odined back to stock I always used the pit. I was under the influence that set everything up the way it came stock. Hope to see some of your work coming to sthe s4. Maybe you help the sense port going on in the international thread lol. Not trying to add work to ur day but I OK know if u, jt, and entropy can bring ICS to a out dated phone u might have the skills to ad your 2 cent.
Sent from my SGH-M919G using XDA Premium 4 mobile app
---------- Post added at 02:18 AM ---------- Previous post was at 02:01 AM ----------
Blaze9 said:
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Click to expand...
Click to collapse
I had to Odin to stock the first time two days agao but mine booted and I only had stock recovery. When it started up the ROM everything was crashing and that's what fixed it. Glad you fixed it though.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
gerard0986 said:
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
Click to expand...
Click to collapse
The PW TWRP asks for? IT's just TWRP, if I remember correctly.
I have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
csrredcoat said:
I have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
Click to expand...
Click to collapse
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
csrredcoat said:
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
Click to expand...
Click to collapse
Take out battery. Put in back in. Go to stock recovery (by pressing volume up and power button and letting go when you see tiny blue letters) from there just do a factory reset then reboot. Dont worry if you a dead android its ok. Then you should be ok.
---------- Post added at 11:28 PM ---------- Previous post was at 11:12 PM ----------
csrredcoat said:
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
Click to expand...
Click to collapse
Well from my understanding we should not have repartition checked. Dont know the outcomes tho but im pretty sure now you need pit files for gs4 sprint to remap the partitions for your phone back the way it was. Should be here in xda but if you cant find them then just odin again a stock tar and do a factory reset in stock recovery. See if that works.
Back to Stock but have a question
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Software/Baseband Version MDC to MF9
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
csrredcoat said:
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Click to expand...
Click to collapse
Im not so sure on CWM since ive been using twrp so I can help you there.
csrredcoat said:
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
Click to expand...
Click to collapse
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
ROMANTiC KiD said:
Im not so sure on CWM since ive been using twrp so I can help you there.
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
Click to expand...
Click to collapse
OK, I am confused but eager to learn. I just did a ODIN back to stock, I am now unrooted. I did a factory reset in stock recovery. Now I think I should be able to click update firmware to get to MF9 but it says no updates found or I am up to date. I don't get this. Why is it not finding any updates?
Even More Confused!
edit
Ok, it is downloading MF9 in background now. Not sure why it initially said no updates found. I should be good now. Thanks!
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
doesntmatterx said:
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
doesntmatterx said:
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
Click to expand...
Click to collapse
:good:
xBeerdroiDx said:
:good:
Click to expand...
Click to collapse
I take it back, stuck in a boot loop even after 2 fresh ODIN unroot tasks. Nothing I do gets me out of this, been a long day getting longer now
Can anyone help? Been at it for hours, I have tried everything, phone still reboots at the Samsung logo (the bluish one )
Unrooted 3 times
Launched stock recovery, wiped factory reset
wiped partition cache
removed battery
Cannot connect to Kies for Emergency restore.
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
seanpr123 said:
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
doesntmatterx said:
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
Click to expand...
Click to collapse
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Should I ODIN with the RE-Partition Option?
Just Odined again and no dice. I booted into stock recovery and noticed after wiping factory I get "Can't open /efs/log/boot_cause" which pointed me to this fix someone on the Galaxy note forum said they did and it worked but I dont understand the steps, need some elaboration.
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
jd1639 said:
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Click to expand...
Click to collapse
Yep did that mulitple times, also did wipe cache partition in the same stock recovery. I get to the Samsung logo where the blue halo spins around the name, then it freezes there and reboots.
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
seanpr123 said:
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
Click to expand...
Click to collapse
LOL thanks, yes I may have to do that. I had a backup and it was wiped.
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Try flashing using cwm. It'll probably work fine. Then you can go back to twrp. That's worked on other devices. Seems one you flash it once with cwm then twrp works from that point forward. Idk why
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I tried flashing with a PIT file I found online but it fails through ODIN everytime. I tried on multiple versions of ODIN as well. I also cant seem to find readily available PIT files to test as well, (perhaps the one I used does not work). Also I did try to flash a CWM through ODIN but failed, but again there isnt anything that I have read that says "hey you can do this that way and it will work".
From what I understand I need to be rooted to install CWM or TWRP, and since I unrooted to try and fix the problem I cannot root myself through conventional methods. Everything I found online requires the phone to completely start up. (to the menu screen etc)
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
jd1639 said:
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
Click to expand...
Click to collapse
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
doesntmatterx said:
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
Click to expand...
Click to collapse
Do you know what firmware you were on? Was it mdl or mf3?