Database Users

Bricked phone trying to downgrade from froyo 2.2

So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us

superbraut said:
So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us
Click to expand...
Click to collapse
Put the phone in download mode again and run odin again.
Sent from my SPH-D700 using XDA App

Thanks for the tip!

Your gonna want to flash the di18.tar in "pda" with odin and only reboot checked, no pit needed. That gets the di18 firmware back, and the only way.. kernel has nothing to do with it..
Sent from my SPH-D700 using XDA App

I am about to do this too.. and dont want to wipe the data only get back to di18 to get the gps working.. so in that case:
1. I dont need pit file at all
2. which .tar to choose? not the255 mb file?

Mine failed the first time to. I followed the directions from http://forum.xda-developers.com/showthread.php?t=773032
I tried it a second time but used the victory pit that came with odin 1.61 and it worked. I think in the instructions their using an older version of odin.
I'm not in anyway an expert and you may not even need to use a pit like another poster said. It worked for me though. When I got done the phone rebooted and it showed it having the eclair d07 build from there it updated itself to dI18.

I believe you still need the pit file. If you are going back to stock DI18, than use this:
Stock Files
The one you were trying to use was the kernel I believe.
Here is the pit file you need:
pit file
I have flashed back to stock about 14 times and I have used these two files successfully every time.

yeah ive done it te same wasy that swanysto has done it also a lot. it always works for me to. i know some sa you don't need the pit unless just doing a kernel but i always use it. just my 2 cents

pull the SD card out before you go into download mode (not just pull it out, make sure to push down and let it pop up to remove it).

I'm at a loss here with a bricked phone

Odin froze on me looking for pit something. I'm going from rooted only di18 to the new eb13. So I can get into download mode still. Do I just need to keep trying to flash the tar in the pda or do I need to do the pit instead? Thanks
Or should I try the samsung utility, I have that too.

funeralplanner said:
Odin froze on me looking for pit something. I'm going from rooted only di18 to the new eb13. So I can get into download mode still. Do I just need to keep trying to flash the tar in the pda or do I need to do the pit instead? Thanks
Or should I try the samsung utility, I have that too.
Click to expand...
Click to collapse
You need both. Tar in PDA and PIT in ... well PIT!

funeralplanner said:
Odin froze on me looking for pit something. I'm going from rooted only di18 to the new eb13. So I can get into download mode still. Do I just need to keep trying to flash the tar in the pda or do I need to do the pit instead? Thanks
Or should I try the samsung utility, I have that too.
Click to expand...
Click to collapse
bjhill2112 said:
You need both. Tar in PDA and PIT in ... well PIT!
Click to expand...
Click to collapse
If you are using the full system tar, you do not need the pit. The pit is used for flashing kernels and modems.

Since you can still get into download mode, I'd just use the samsung flash tool. Worked great for me, and I came from a rooted DK28 build. It takes care of everything for you, completely wipes the phone, no need to mess around with Odin. I know Odin can be temperamental at times.

abrognlie said:
Since you can still get into download mode, I'd just use the samsung flash tool. Worked great for me, and I came from a rooted DK28 build. It takes care of everything for you, completely wipes the phone, no need to mess around with Odin. I know Odin can be temperamental at times.
Click to expand...
Click to collapse
+1
I agree. Odin is not meant for consumers.

Okay, thanks will try the samsung utility then. Thanks. Will advise on how things turn out....

I can still do this even tho the phone doesn't boot up right? I get that phone and monitor picture. But i can get to download.

The file you need for flashing now, being in the download mode, for updating to EB13, is this: http://www.multiupload.com/F0JFA0487M. This file was posted by Whosdaman, in the Development thread. You won't need the PIT file. Use Odin's PDA box to flash this ROM.
Sent from my SPH-D700 using XDA App

Wow, it freakin worked......now I have to find out how to do a hard reset while I'm at it....

mattallica76 said:
If you are using the full system tar, you do not need the pit. The pit is used for flashing kernels and modems.
Click to expand...
Click to collapse
Duh. Silly me. Sorry for the misinformation.

Here is Odin flashable EF02 upgradable to EF10 Modem with complete package

Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
This allows you to do a firmware upgrade to EF10 also......again, I am using it on Froyo
Edit: I have added a zip file containing the exact files that I am successfully using to flash. Download the zip, extract the files, put the pit in the pit, the modem in the pda and flash.

shiftr182 said:
Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
Click to expand...
Click to collapse
Is This 4 Real ??!?!?!?!?

do i need a pit? there's been debate over this recently

I always use a pit

CARPLUNK - this didn't work

shiftr182 said:
I always use a pit
Click to expand...
Click to collapse
Have one to spare? Apparently, I've been getting very lucky by flashing modems without one.

The Root said:
do i need a pit? there's been debate over this recently
Click to expand...
Click to collapse
NO, but it you can use it.

The Root said:
Have one to spare? Apparently, I've been getting very lucky by flashing modems without one.
Click to expand...
Click to collapse
Here is the pit. Extract from the zip.

heathmcabee said:
CARPLUNK - this didn't work
Click to expand...
Click to collapse
Has this worked for anyone yet?

I just used it(I have flashed a few times to make sure it works) . It works. Im using the old odin.

Playing with both modems now. EF02 was eh ok in my area. 4g was 5.5d 1.6 u. GPS locked faster than i've ever seen. Just pushed to EF10 and rejected it's love of looking for random updates.
Flashed back to EF02 over a thought that they're sacrificing GPS for speed or can't figure out how or why to release them in a modem together. I believe the EF02 amazing modem might be true.
Final verdict: EF02 is the ****. Instant GPS lock and 6-7mbs d/1.6 mbs u on 4g avg. I don't know what went wrong in EF10
Btw, no one got me a pit in time and now I've learned my phone clearly doesn't care.

shiftr182 said:
I just used it(I have flashed a few times to make sure it works) . It works. Im using the old odin.
Click to expand...
Click to collapse
Gonna try using the old Odin to see if I can the update. Thanks for the files though man! i dont have anymore thanks left for today, but will hit you up tomorrow with due thanks.

Make sure you extract the tar from the zip. I was trying all kinds of things to get this to work, and finally got it.

how can i get this EF02 to EF10?
i tried firmware, profile, prl but nothing it say problem while updating try again later am i doing something wrong?

shiftr182 said:
Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
This allows you to do a firmware upgrade to EF10 also......again, I am using it on Froyo
Edit: I have added a zip file containing the exact files that I am successfully using to flash. Download the zip, extract the files, put the pit in the pit, the modem in the pda and flash.
Click to expand...
Click to collapse
Please help. Did I just brick my phone? Here's what I did.
Saved and extracted the pit and the modem to the desktop
Booted phone to Download mode
Opened Odin and selected the PIT in the PIT area and the Modem in the Phone slot.
Click Start.
Odin went through ok.
Phone rebooted. But never came back on.
Only at that time did I realize that the Re-Partition box was also checked.
I know... 2 mistakes. Phone slot instead of PDA and Re-Partition was checked.
Is there anything I can do? I've tried booting normally. Booting to download mode. Booting to CWM. First night of rooting and it was going so well until I started to try different modems.

romowens01 said:
Please help. Did I just brick my phone? Here's what I did.
Saved and extracted the pit and the modem to the desktop
Booted phone to Download mode
Opened Odin and selected the PIT in the PIT area and the Modem in the Phone slot.
Click Start.
Odin went through ok.
Phone rebooted. But never came back on.
Only at that time did I realize that the Re-Partition box was also checked.
I know... 2 mistakes. Phone slot instead of PDA and Re-Partition was checked.
Is there anything I can do? I've tried booting normally. Booting to download mode. Booting to CWM. First night of rooting and it was going so well until I started to try different modems.
Click to expand...
Click to collapse
Sorry. Found out a way to fix.
(Take battery out. Hold 1 + Power. Put battery back in).
Was able to reload everything back to stock.
Thought the phone was a goner. Had no signs of life at all.

[Q] Bricked - Please Help (SOLVED)

Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!

IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.

@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.

leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03

Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!

leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03

SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03

Soft bricked from failed ota update, odin failing me, any help for a noob?!?

Been having an issue with my ATT S7 when it goes to do some kind of OTA update and fails, then my apps start randomly crashing and of course I decide to reboot. When I reboot I get stuck on the white att screen. This is the second time is has happened, first time I just did a factory reset and was back up and running. Well today it went to do an update, update failed and I am back at a white screen again. I decided to start researching what the newest firmware was and can’t seem to get a straight answer. I also have no idea what bootloader I am on and so on…From what I can tell is PK1 is the newest firmware am I right?!? No idea where to check what bootloader I have…
So I decided I was going to just install everything from this thread in hopes to cure my issue https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168
I downloaded all the files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis. I’ve done the normal dumb stuff like latest drivers, get the same error on Odin 3.10.6 and 3.12, ran Odin as admin first then set phone to download and plugged it in. Odin is definitely recognizing my phone as it says added. Just can’t figure out what I’m doing wrong and want to get this damn phone on the latest everything so it will quit downloading updates and taking a **** on me. Any help is much appreciated!

Sorry about this replied to wrong phone.
Sent using SM-G891A & MultiCam Black Tapatalk.

jermo said:
Been having an issue with my ATT S7 when it goes to do some kind of OTA update and fails, then my apps start randomly crashing and of course I decide to reboot. When I reboot I get stuck on the white att screen. This is the second time is has happened, first time I just did a factory reset and was back up and running. Well today it went to do an update, update failed and I am back at a white screen again. I decided to start researching what the newest firmware was and can’t seem to get a straight answer. I also have no idea what bootloader I am on and so on…From what I can tell is PK1 is the newest firmware am I right?!? No idea where to check what bootloader I have…
So I decided I was going to just install everything from this thread in hopes to cure my issue https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168
I downloaded all the files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis. I’ve done the normal dumb stuff like latest drivers, get the same error on Odin 3.10.6 and 3.12, ran Odin as admin first then set phone to download and plugged it in. Odin is definitely recognizing my phone as it says added. Just can’t figure out what I’m doing wrong and want to get this damn phone on the latest everything so it will quit downloading updates and taking a **** on me. Any help is much appreciated!
Click to expand...
Click to collapse
When i flashed the APK1 files it hung on file analysis for about a good 5 min. I was fixing to reset and try again and it finally got past that part. I'm not sure why it took so long. The APK1 files are the latest files for the G930A. It is bootloader 4. What version of odin are you using.

dirtydodge said:
When i flashed the APK1 files it hung on file analysis for about a good 5 min. I was fixing to reset and try again and it finally got past that part. I'm not sure why it took so long. The APK1 files are the latest files for the G930A. It is bootloader 4. What version of odin are you using.
Click to expand...
Click to collapse
I've tried using odin 3.10.6 and 3.12.3...both always hang and i've waited way past 5 mins. I'll try again though and let it go for a long time, you do all 4 of them at a time right? Or do you do BL first, then AP and so on?

jermo said:
I've tried using odin 3.10.6 and 3.12.3...both always hang and i've waited way past 5 mins. I'll try again though and let it go for a long time, you do all 4 of them at a time right? Or do you do BL first, then AP and so on?
Click to expand...
Click to collapse
I did all of them at the same time. The only thing i did different than you was that i extracted the .rar instead of renaming it.

dirtydodge said:
I did all of them at the same time. The only thing i did different than you was that i extracted the .rar instead of renaming it.
Click to expand...
Click to collapse
Oh man that's exactly what the problem was lol I feel super retarded right now...anyway extracted the md5 files and it went through fine. I knew it had to be something ridiculous, thanks again everyone!

jermo said:
Oh man that's exactly what the problem was lol I feel super retarded right now...anyway extracted the md5 files and it went through fine. I knew it had to be something ridiculous, thanks again everyone!
Click to expand...
Click to collapse
I thought you just extracted the zip files to a folder and used them then to put into Odin slots. After unzipping they are MD5 files. At least that is what mine say after unzipping. CORRECT????

tailgunner9 said:
I thought you just extracted the zip files to a folder and used them then to put into Odin slots. After unzipping they are MD5 files. At least that is what mine say after unzipping. CORRECT????
Click to expand...
Click to collapse
I figured that was the case too but odin doesnt recognize .rar files. I looked at the files i downloaded and they were named '.tar.rar'. Odin recognizes .tar files so i figured id just delete the .rar and it would work but nope you have to open the rar files in WinRar or whatever program you like and extract the MD5 files. Then plug those MD5 files in odin and it will go through just fine. PK1 feels pretty sexy so far!