Database Users

i need help flashing back to stock bell firmware please

i have been searching for 2 days for the original bell galaxy s jh2 firmware so i can flash my phone back to 100% stock and exchange it for a new one (mine wont boot into recovery with the 3 button combo).
i am looking for the bell version, including all of the pre-installed bell crapware, etc. can anyone provide a link to either an update.zip file or the files needed for odin? i was trying to un-root my jh2 software yesterday morning and couldnt do it, so after a bunch of flashing, and two near brickings i am now on jm6 firmware but now kies wont connect to my phone. all of the drivers are there, and i have uninstalled and reinstalled kies already but my phone will no longer connect.
i downloaded the jh2 files from http://www.samsungflash.com/wiki/I9000 and tried to flash with odin but it left my phone in a bricked state. the files provided were only the pit and pda file and the flash just wouldnt work. i have only been successful with odin when using separate pda, modem, and csc files. any help would be appreciated

When you turn on your phone what does it do exactly? Does it boot into the OS, or just stay on the Samsung screen?
Have you tried using the Bell firmware (JH2) found here. That is the provider file. So if you can find the PDA and PHONE file you like then that file should return it to stock.
Post back with results.

gold_sprinter said:
When you turn on your phone what does it do exactly? Does it boot into the OS, or just stay on the Samsung screen?
Have you tried using the Bell firmware (JH2) found here. That is the provider file. So if you can find the PDA and PHONE file you like then that file should return it to stock.
Post back with results.
Click to expand...
Click to collapse
my phone boots up fine, it was completely screwed up yesterday but i actually ended up flashing to the software you linked to. that software doesnt have any of the bell stuff in it.
thanks for trying, though
edit
i forgot to type in the code at the end of those instructions and it hard reset my phone but now the bell stuff shows up. thanks! the only problem is that the software doesnt show up as jh2, but the apps are there. one step closer

If you are to return it to bell in this state, would they really look to see what firmware was flashed to it. Especially if you are returning it because of the 3 button problem? As long as it boots up and they can see you have not broken it, this should be sufficient.
Correct me if I am wrong.

gold_sprinter said:
If you are to return it to bell in this state, would they really look to see what firmware was flashed to it. Especially if you are returning it because of the 3 button problem? As long as it boots up and they can see you have not broken it, this should be sufficient.
Correct me if I am wrong.
Click to expand...
Click to collapse
i just dont need the hassle if they notice it is rooted and dont want to take it back.
member Richthofen sent me a link to the files and i used odin to flash back. it is now 100% stock.

That is awesome, glad to see it worked for you. Would you mind linking to the files so others with the Bell brand can do the same?

http://www.multiupload.com/N62CDNXXXK
this is a link to the files needed to use odin to flash back to 100% stock bell firmware. thanks to richthofen for the file

Sorry to revive an old thread but I think this is the ideal spot to put this question. My SGS I9000M is stuck on the boot screen so this will be my first try with ODIN.
I have installed ODIN 4.03, and I have downloaded the above file and unzipped it with 7ZIP. It contained one .tar file. I put my I9000M into downloading mode, launched ODIN and plugged in the phone. It was detected and says com port mapping 1 (COM5) on ODIN. I ticked the One Package option box and selected the .tar in the One Package address box. Already selected were Reboot, Protect OPS and Reset Time (300 ms). I clicked start and a popup said "Check Image Files!!". I clicked okay. The log box to the left indicates "Download Start..." but nothing appears to be happening, and the start button is available to be pressed again.
Did I miss something?
Thanks!
_____________
UPDATE: Okay, Looks like you need ODIN 3, version 1.0, as far as I can tell, so I have installed that, put phone in download mode, plugged it in and ODIN detects is (0(COM5)) There is no One Package option so I went with PDA.
The following appears in the log window:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> dbdata.rfs
The phone screen went blank and is non responsive. There is no apparant change in ODIN. I'll let it sit for a while unless someone can redirect me on this?
Thanks.

Mad Medik said:
Sorry to revive an old thread but I think this is the ideal spot to put this question. My SGS I9000M is stuck on the boot screen so this will be my first try with ODIN.
I have installed ODIN 4.03, and I have downloaded the above file and unzipped it with 7ZIP. It contained one .tar file. I put my I9000M into downloading mode, launched ODIN and plugged in the phone. It was detected and says com port mapping 1 (COM5) on ODIN. I ticked the One Package option box and selected the .tar in the One Package address box. Already selected were Reboot, Protect OPS and Reset Time (300 ms). I clicked start and a popup said "Check Image Files!!". I clicked okay. The log box to the left indicates "Download Start..." but nothing appears to be happening, and the start button is available to be pressed again.
Did I miss something?
Thanks!
_____________
UPDATE: Okay, Looks like you need ODIN 3, version 1.0, as far as I can tell, so I have installed that, put phone in download mode, plugged it in and ODIN detects is (0(COM5)) There is no One Package option so I went with PDA.
The following appears in the log window:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> dbdata.rfs
The phone screen went blank and is non responsive. There is no apparant change in ODIN. I'll let it sit for a while unless someone can redirect me on this?
Thanks.
Click to expand...
Click to collapse
Disconnect phone from pc if not done already.
1) restart Odin
2) tick "repartition"
3) choose 512 pit file
4) put phone in download mode, connect phone to pc, click START in Odin
5) Once Odin says "PASS", disconnect phone
6) remove and replace battery
7) In Odin click "reset", untick "repartition", put tar file in "PDA"
8) put phone in download mode, connect phone to pc, click START in Odin
9) Once Odin says "PASS", disconnect phone and just let it reboot
10) Voila, you're back to 2.1 stock
Good luck!

donkeyhitman said:
Disconnect phone from pc if not done already.
1) restart Odin
2) tick "repartition"
3) choose 512 pit file
4) put phone in download mode, connect phone to pc, click START in Odin
5) Once Odin says "PASS", disconnect phone
6) remove and replace battery
7) In Odin click "reset", untick "repartition", put tar file in "PDA"
8) put phone in download mode, connect phone to pc, click START in Odin
9) Once Odin says "PASS", disconnect phone and just let it reboot
10) Voila, you're back to 2.1 stock
Good luck!
Click to expand...
Click to collapse
I had black screen after s logo boot.
So I used Odin 7 new to re-flash jk3 the bell version. And when it booted up first time I get mount error and vol + home and power does not work only download mode works. I flash like 15 times same ****. Even used different check marks repartition and boot loader all did not held any results.
Now that I sent it back to bell, I wonder if I had used Oden 1.3 instead of Oden 1.7 if that would have helped at all
I think it's the defective internal sd memory, as my phone is bell phone and I keep reading problems with the internal sd memory.
Do you think it could have been revived or am I right it is defective memory.
So I sent it back

[Q] Tab won't flash kernel

Hello,
I recently flashed the Overcome ROM/Kernel (I'm still quite a noob though). After call volume issues I tried to flash the stock rom using the files from samfirmware.
I can flash the PIT successfully, it's when I try to flash the PDA file (either overcome kernel or stock firmware) I get this:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me or am I now the not so proud owner of a expensive and stylish paperweight?
Any help would be greatly appreciated.

First let me get this right. You would like to go back to sgt stock rom after flashing the overcome kernel?.
As long as you can boot into download mode. There is still hope. If odin is giving you problems try Heimdal to flash zimage modem and other files from the samfirmware archive. If you still want to use odin. Try doing a factory reset and a wipe from recovery (vol up and power).
Just a word of caution samfirmware roms might have signed bootloaders. Which can be a hinderance for flashing custom roms in the future.

Heimdal doesn't want me to click start (it's greyed out).
I've put the pit, pda, modem and CSC files in and it's still greyed. Am I doing something wrong? I installed the drivers as stated in the read me.
Edit: Got a bit of life out of it, when I uncheck everything but PDA it allows me to click start but throws: Failed to access device. Error: -12

Then Try a factory reset and a wipe from the Recovery mode. Wipe it clean and start fresh.

I couldn't get into recovery.
I've just changed the driver to the unsigned ones (not the originals as stated in readme) and it seems to be working at the moment....
fingers crossed

It wouldn't go past the galaxy tab screen so I tried again and the same I get an image of a phone, exclamation mark in a triangle and a pc. I think this is like download mode as I can still access via odin which allows me to flash the PIT and get download mode back.
It seems a problem with the zimage process, I've tried 3 different versions with no luck

Thing seems dead now. It made a loud beep when I plugged it in to the PC but that's it

Plug in your wall charger and see if Tab charges. If it charges fully charge the tab and try a RESET. You might want to try ROTO ROMs at development section first to get your tab started before going into any trials with stock ROMs.

Personally i use odin. Find it easier.
If you followed the instructions for overcome, clockworkmod recovery is installed by default
All you have to do is copy the Overcome rom zip file (200+meg) to your ext sd card.
Boot to clockworkmod recovery (power+up buttons)
Clear all caches
Select install rom from sd card
Choose overcome zip file
Install
Reboot kernel is installed with rom
______________________
Overcome 1.2.1 at 1.4GHz
Quadrant 2290

it doesn't want to charge, it seems it can't draw enough power from USB to even run off that.
When plugged into the wall I get the phone, triangle, computer screen and it constantly restarts after less than a second.
Think I'll just have to take it back to PC world and act dumb (like the staff)

Left plugged into the wall over night, the battery is still dead.
I'll faf around a bit more today and if no progress I'll just return it to the store.
Thanks for your help

Tired plugging into rear usb and after a while it turned on and went to the phone - triangle - computer screen (some sort of alternate download mode) flashed PIT with odin, this enabled me to actually get into download mode (or see the galaxy tab logo til the battery dies if I want to). Then flashed rest of the files with Heimdall, still the tab doesn't allow me to turn on. Thinking it might be due to low power I plugged into wall charger, usually when the tab is charging when turned off you see the battery image with the green level indicator, all I see is an empty battery with the sort of loading thing in the middle of it (though it isn't going round). Still doesn't seem to want to charge (or turn on) is the charging process governed by the kernel?

Just called PC World support, told them I turned it off last night to charge and when I turned it on it just showed the galaxy tab screen. They said just take it instore and they'd swap it

[Q] AT&T Galaxy S5 Update G900AUCU2ANG3 - Issues after update

I have tried searching and do not see anyone with a similar issue. I was previously rooted with TowelRoot, but somehow my phone not only allowed the G900AUCU2ANG3 update today to download, but also allowed it to install. I know I should have removed TR before continuing, but stupid stuff like that happens when you see the update waiting when you first wake up and don't have contacts in or glasses on...
I can fully restore my phone to normal use, other than wifi. For whatever reason, the failed update shows to have changed the baseband, but I have no ability to connect to a wifi network, and despite about 15 factory resets since this morning, my device status still shows "Custom." Here is exactly what I see when I go into Download Mode (or as close as I can replicate it):
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
At this point, I can't find anyone with an NG3 stock firmware to use with Odin, and Odin keeps failing because the old firmwares won't pass the authorization stage. I attached the Odin screenshot to this post in case someone has other ideas. I can actually use my phone (not bricked), but wifi will not connect even though it can see various open and secure networks. I get an error stating "Failed to Obtain IP" when trying to connect to networks with "Very Strong" signal strength (I can see the AP from my desk).
Thus, I really need to be able to do 1 of 2 things:
1) Restore it to stock myself so I can have wifi, or
2) Be able to get it to show "System Status: Official" so that the local AT&T Device Service Center I drive by twice a week taking my kid to hockey practice will plug it in and update it and restore it. They managed to save my wife's Note 3 from a fairly bad soft brick / boot loop issue, but I also know that the "Custom" thing will pretty much guarantee they don't work on it.
Thanks in advance.

..

fffft said:
Writing a full stock firmware image, followed by a factory data reset will remove the custom status. So that would satisfy No. 2.
As to your first wish, I find it hard to believe that you couldn't find an ATT firmware image anywhere. There are dozens of firmware sites and I can only assume that you just did a short or cursory search. If you spend a few minutes with Google you can surely locate any ATT firmware version that has been release longer than one day.
Either way, use Odin to write a firmware image as the fastest way to resolve the situation. If you have difficulties, try this guide
If the problem persists, then you need to provide us with more details. Notably, the verbatim Odin error log, along with the exact file name you are trying to write and a detailed, step by step description of how you are using Odin.
.
.
Click to expand...
Click to collapse
I definitely have searched high and low for a stock version (both before the original post and just now) that will work with the failed update G900AUCU2ANG3. No one has a stock firmware I can find, and I cannot find any method by which to downgrade to an older version that I can find, such as G900AUCU1ANCE.
Here is what my phone says in Settings --> About device:
Baseband Version:
G900AUCU2ANG3
Build Version:
KOT49H.G900AUCU2AND3
File name I'm trying (but know won't work...not the newest baseband): G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar
Odin Error Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

..

fffft said:
The additional information definitely helps. But it's still a drop in the bucket. You didn't give us a detailed, step by step description of how you are using Odin e.g. what version of Odin you are using , which line you entered the firmware file line on (e.g. AP, PDA, etc) and so forth. And most importantly, did you try the procedure that I linked to in my last post?
We can't see your phone and these details are important as any one of them could cause failure. So we need to check off each item that you are doing.
Nominally the Odin error you posted says that your bootloader refused the firmware version you tried to write. More likely it is a timing error from a marginal USB cable or port. Odin is well known as tempermental with respect to USB timing. Try a different USB cable (yes, really. and yes, it is important. don't skip this step) and different USB port.
Most critically, ensure that you are entering download mode by removing the phone battery, then replacing it and using the volume down + home +power key sequence. And also important, if the first Odin write fails, do not close the Odin window. Instead remove the phone battery again, go into download mode again and then hit write again in the open Odin window. Inevitably, the second attempt will then succeed.
Try the very good procedure that is listed here <---- click on the link
Odin can be frustrating, but with a modicum of patience and attention to detail you will succeed. Good luck
.
Click to expand...
Click to collapse
I ended up going to the local AT&T Device Support Center (luckily it's about 2 miles from the ice rink at which my son practices) and they flashed it back to stock with no problems. She said I was one of 4 people that day who had issues with that particular update, and since my Knox Warranty showed 0x0, she thankfully ignored the "Custom" on device status. All is well and I have a clean backup in Kies if needed in the future and TowelRoot back on the device to kill some bloat. Thanks!

Can I get a flashable G900AUCU2ANG3? I am selling the phone and they want it stock and updated. I can't flash it back to stock. I didn't update it but it gives me the same Odin error as though I was trying to downgrade. Used to be able to downgrade it and do whatever I wanted when I was tinkering with getting SuperSU to stick after update. I've made no major changes. Did something come down from Samsung that locks Odin? I froze Knox and thought that might have something to do with it so I thawed it and factory reset after unrooting. No good.
Long story short I'd like an Odin flashable latest firmware to see if it will take. Sorry I don't have more info right now but the buyer has the phone right now.

Soft Bricked S5

Bought a S5 (SM-G900AZ) "unlocked" cricket phone intending to use it on AT&T, it was running 5.0 and I got root then started disabling some of the bloat via 'no bloat' app, all was well, then I restarted, after the splash it displayed the setting up android window, then went to setting up apps, then it got stuck in a loop where it rebooted repeatedly at this step, never actually starting. I let it retry for a while, dropped the battery and tried again to no avail. Next I put it into the menu so i could do a wipe and clear the cache which I did then restarted, same result. figured I had boned it up and would need to reflash the factory distro to reinstate some of the bloat I disabled. I downloaded the correct firmware of 5.0 from Samsung opened Odin and selected the AP check box, located the Samsung file, it checked the MD5 then I hit start, FAILED.
From ODIN
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Phone
ODIN MODE
Product Name: SM-G900AZ
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
AP Swrev: S1, T2, R1, A3, P1
Secure Download : Enable UDC Start
SW Rev Check Fail : [aboot]Fused3 >Binary 2
What does the Fused and Binary numbers mean?
Do I need to attack this from another angle?
Any ideas on how to get the factory software back on this thing?
Thank you for reading and any help you can provide.

bump

This is also my problem in my SM-G900I, i cant update to official marshmallow firmware because it always does the same as yours. Even in lollipop firmware still the same result, always failed. I already tried everything, factory reset, all odin version etc but still same result.
In odin 3.10.7 im stuck in this for almost 1 hour (see attached). I tried 5 times and still the same.
hope someone can help us.....:crying::crying::crying::crying:

The assasin said:
hope someone can help us.....:crying
Click to expand...
Click to collapse
He has a name, and called official Samsung service center.

SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Update kies, and usb divers [Tools : Reistall Device Driver]
With your phone booted in to Download Recovery [push Power + Home + Vol Down] then [Vol Up to confirm] then connect to the USB.
Now the USB cable should keep it powered up, you can remove the battery and read the Mod # and SN #
In Kies go to [Tools : Firmware Upgrade and Initialization]
Put in your Mod # [ok]
Put in your SN # [ok]
Click ok on all the confimation boxes.
It will download the correct software from Samsung then push it to the phone and restart, pay attention as it asks you to remove and replace the cable after restart, incidently if you removed the battery eariler to read the Mod # / SN # then when it resets it wont restart, if you happen to walk away.
Put in the battery and power it up, mine rebooted a couple times then booted normally starting back at the Welcome screen, I was able to re root and make some of the changes I was trying to make and now have a working phone.
I hope this helps others.

BrweckedS5 said:
SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Click to expand...
Click to collapse
The first software that every fresh S5 owner gets related with, this is KIES..
Every one assumes that you failed in all known ways and then you started this topic.

Samsung Galaxy S4 Bricked, Odin stuck at Initialization, Recovery Mode Inaccessible

Hello,
I keep on playing with lots of ROMs and Mods so I am quite familiar with the entire process of flashing via recovery or odin. However, something really sinister happened to my S4 and I can't find anything that can revive my dead S4. Here is what happened exactly.
1. My battery would only give around 4 hrs of backup so I went and bought a new Galaxy S4 battery.
2. I came home and tried to replace the battery but the phone wouldn't show signs of life. I thought it was because the new battery had no charge. I tried to charge the phone. It kept of showing the lightening bolt sign for very short period in frequent intervals. I let it charge for an hour thinking the new battery was in deep sleep but to no avail the battery didn't work. The battery wouldn't charge but the upper portion of my phone was heated.
3. So I removed the new battery (which I would go the next day to replace) and I placed my old battery which started the "Samsung Galaxy S4 GT-I9500" logo but after I ended up with a black screen.
4. I tried to go to recovery mode but it would just get stuck at the "Samsung Galaxy S4 GT-I9500" forever.
5. I went to download mode and connected it to Odin (which would assign ID:COM to my S4 meaning it recognizes it) and tried to flash TWRP but it would always get stuck at Initializing...
6. When I disconnected the phone it would say "Get PIT for mapping" and "There is no PIT partition"
7. I tried to flash Stock ROM (I9500XXUHPI1_I9500ODDHOJ1_I9500DDUHPE1_HOME.tar.md5) which gave the same result stuck at "Initializing..."
8. I tried 4 different USB cables, a desktop with Win 10, A desktop with Win 7, a laptop with Win 10, a laptop with Win XP, all the USB ports of each computers and still got the same result. I also tried 5 different Odin versions. Nothing!
9. I tried to flash PIT file with the stock ROM, same result.
10. I installed Kies, killed the processes, updated drivers, uninstalled kies and installed only the Samsung drivers and still wont work.
11. I tried to do the "Firmware upgrade and initialization" from Kies and put my model "GT-I9500" and my S/N and it said my model doesn't support initialising.
12. I have cleaned my USB port too. Oh, by the way, I had once replaced the charging flex and it would still give some problems regarding the "back" soft key but only once in a blue moon which I have ignored.
This is what happens in Odin every single time I try to flash anything at all.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
(Gets stuck here forever but when I plug my phone out it proceeds as following)
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Please help me. I don't know what to do because the download mode seems to never load anything into the phone. I am literally on the verge of tears.

I'm sure this is not what you want to hear, but you may need to let a professional look at it.
You've tried pretty much everything that might make the flash fail or get stuck, and yet it still doesn't work. So I'm pretty sure the problem is not you.

Are you using the original Samsung USB cable? Tried different USB cables and USB ports?
Based on my experience with Samsung phones (s2, s3, s4, Note 2, note 3), they are picky about USB cables when flashing in Odin.