Related
Here was my situation, and how I got out of it:
I was running the Perception build 7 ROM. It was great, no issues except that I needed to get some kernel modules for it, and was unable to get the info I needed to re-create the kernel build environment. I decided to return to stock. There were lots of threads, all going in different directions with inconsistent advice. The wiki I was looking at has what appeared to be a ClockworkMod (CWM) backup.
I had already tried to restore my own CWM backup, but (after disabling lagfix) would restore, but then seemed to loop trying to start the lock screen. Same thing with the version on the wiki. I didn't want to restore to the ATT version and I didn't have windows to run Odin...
So this should work from Windows, Linux and Mac.
get param.lfs from http://forum.xda-developers.com/showpost.php?p=9663090&postcount=58
get FIRMWARE from http://forum.xda-developers.com/showpost.php?p=9109370&postcount=697
Get Odin.rar from http://forum.xda-developers.com/showpost.php?p=8802897&postcount=1
Get Heimdall from http://www.glassechidna.com.au/products/heimdall/
Install Heimdall and any drivers it requires.
Extract the .pit file from Odin.rar. I have heard other people say don't use the pit file…I did…
Unzip the firmware
start Heimdall
FactoryFS
- factory.rfs
Kernel
- zImage
Param.lfs
- param.lfs - though I didn't use this
Primary Bootloader
- I left this blank
Secondary Bootloader
- I left this blank
Cache
- cache.rfs
Modem
- modem.bin
FactoryFS
- factory.rfs
Click Start
Phone will do it's thing. I did receive an error at the very end but all went well. I'd welcome some additional info on the Primary/Secondary Bootloader.
Curious if this restored the bootloader from at&t back to the rogers one?
Excellent! Another successful restore of Rogers stock with Heimdall. Thank you for the write up, gin032.
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
I had the same troubles is well.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
gin032 said:
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
Click to expand...
Click to collapse
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
sshvetsov said:
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
soooo why is the "start" button grayed out???
soooo why is the "start" button grayed out???
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
SteveCheeseman said:
soooo why is the "start" button grayed out???
Click to expand...
Click to collapse
10ee said:
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
Click to expand...
Click to collapse
sshvetsov said:
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Benjamin Dobell said:
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Click to expand...
Click to collapse
In my case, I did re-partition....but in the interest of fullness, where can one find such a secondary bootloader?
Bricked my rogers i896 while trying to mash up different kernels for a rom, odin didnt work so i tried heimdall with the procedures thanks to OP.
The only difference was I did not use the pit file. Everything worked flawlessly and I still managed to maintain my data on root sd although i lost root access. The ATT splash screen also was removed (thank goodness) and model number changed back to i896 in the "About". It is now back to pretty much stock, though I did lose the APN settings (can easily reenter it). Last step now is just to re-root and restore via Titanium Backup.
Thanks for the helpful information everyone!
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
loonieryan said:
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
Click to expand...
Click to collapse
This please!
I've tried this, but use zadig.exe my phone shows up as Gadget Serial. So I installed anyways, it says successful, but nothing happens in the frontend that shows the phone and it doesn't allow me to start anything.
ootz0rz said:
Curious if this restored the bootloader from at&t back to the rogers one?
Click to expand...
Click to collapse
+1 this is important!
Tried doing this and my phone is now a brick. It's stuck at the following image:
Phone...Yellow exclamation...PC
Edit: Just got download mode back but still not working for me
Edit: Got Odin3 to work finally. Flashing JL1. Hoping it works.
ok, I have a real challenge.
I made the derp of giving my phone temp root using Z4root, then I ran OneClickLagFix on the phone. The phone rebooted & now just goes to a black screen after the rogers logo. it is on but does not respond to anything (capacitive butons light up when pressed).
I tried the steps listed here to revert to factory but it didn't help. Any ideas?
Well here is something that I hope is the start of some hardcore hacking.
This is an ODIN that I created of stock-rooted ED1 for the DROID Charge. In the course of making this, I bricked my charge (first attempt failed in ODIN) and then created a working ODIN that un-bricked it. I then upgraded to ED2 (I confirmed that I lost root as well) so I could test if this will downgrade back to ED1 and it worked and I have root again!
Instructions for ODIN (for those who are unfamiliar with it):
1. Open ODIN.
2. Put the phone into download mode. Do this by powering off your phone, pulling out the battery, and then holding volume down while connecting it to your pc. A giant yellow triangle should be on the phone's screen and it should say 'Downloading...' ODIN should say 'Added!!' and one of the boxes will be yellow and say '0:[COM#]'
3. Click the button labeled 'PDA' and locate the file you are wanting to flash. For emphasis: YOU MUST USE THE PDA BUTTON!
4. Click start. Do not disconnect the phone while it is flashing, it can cause some serious damage.
5. Wait.
6. When finished, unplug the phone, put the battery back in and power up the phone.
Every time I've flashed this, the phone booted straight into recovery. Just select reboot (press home) and it boots up normally. It should probably be recommended to wipe data and cache afterwards, but I didn't and all of my data stayed in tact.
Multiple people have reported that this works. Use at your own risk. I am not responsible for anything that happens to your phone if this doesn't work.
Thanks to imnuts for the HOW-TO thread on creating ODIN builds.
Download here.
Download ODIN here.
to my redbull habit if you feel the need.
I feel dumb for asking, but what are you using to flash this to the phone? I've never used anything other than simple one click root programs, so if you could give a little more detail I'd be happy to try it out.
Download Odin here: http://goo.gl/52aY1
Download Drivers here: http://goo.gl/Tbcca
Download stockrootedED1-20110517.tar.md5 http://goo.gl/kD3Ld
1. Open Odin3 v1.30
2. Remove battery,Hold Vol down. Connect USB to computer and phone then press power. It should take you to a yellow android.
3. Click PDA Button
4. choose stockrootedED1-20110517.tar.md5
5. Click on the Start button
6. Don't Touch and allow the phone to reboot
7. If its taking a while to start DONT PANIC, its perfectly normal
Thanks for the guide, but it doesn't do anything for me, seems like Odin doesn't even know my phone is there. When I plug it in I get the Verizon media manager link to pop up though.
I edited my first post with a link to ODIN and instructions. I guess I'm a little slow with the typing because you beat me to it medjam, but you left out the step of putting the phone into download mode.
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
Once rooted go into your build.prop file and every thing that says ED1 change it to ED2...that should quit the nagging to update. Then restart your phone
Credit goes to Jt3 for that info as he posted it in the Charge forum at android central.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
AWESOME!!! So glad to help!
Very nice!
I know that this will kick start the development of this device now that everybody can haz root.
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
streetlightman said:
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
Click to expand...
Click to collapse
Should work for everyone. My Charge that I just ran it on was never rooted before.
das7771 said:
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Click to expand...
Click to collapse
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
jt1134 said:
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
OH OK...Well let me make change my statemet to be more adult like. If i brick my phone I will just go buy another full price so I don't seem like an asshole. I hope this pleases you Sir....
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
teddykgb715 said:
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
Click to expand...
Click to collapse
Did you install the drivers that came with the phone?
wynalazca said:
Did you install the drivers that came with the phone?
Click to expand...
Click to collapse
I thought so, I can connect to USB storage, etc. I'll check it out.
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
teddykgb715 said:
I thought so, I can connect to USB storage, etc. I'll check it out.
Click to expand...
Click to collapse
I think the issue is that my damn work laptop is locked down pretty tight so it won't let all the drivers install. Unlike many here, I'm actually not an IT professional so I can't circumvent it. I'll just have to try it at home tonight.
das7771 said:
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
Click to expand...
Click to collapse
You're welcome! I'm very glad to help get this development stuff going. Also, there should be a donate button in the OP.
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
de4dw0lf said:
There is a phone on the left, a warning triangle in the middle, and a computer on the right side.
Click to expand...
Click to collapse
Does it look like the attached pic? Or similar?
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
de4dw0lf said:
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
Click to expand...
Click to collapse
First off, you are in an alternate download mode. Just flash Odin as normal with a stock ROM and all will be good again.
Second off, what ROM did you flash that has an overclocked processor? We don't have a kernel that supports overclocking yet, at least for gb.
As for the SIM card, I've had that problem before. It's from not wiping /data /system /cache before flashing. Once you Odin back to stock, it should work. If not, you will have to contact your service provider to get a new one.
de4dw0lf said:
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
Click to expand...
Click to collapse
That is still download mode. Use Heimdall One Click.
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g?
Click to expand...
Click to collapse
Use Heimdall One Click. The one with bootloaders. It will work. Read the OP to a T.
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
Click to expand...
Click to collapse
Click on the Lightning Zap link in my signature... Then click on the link called Removing the Gremlins in the OP
Read the whole post. The link will give you KG4 and Odin and the necessary drivers...
If you already have odin setup use this http://forum.xda-developers.com/showthread.php?t=1353176 It's the official update to Gingerbread.
alright
Alright. i will try the things you guys sent me, and i will tell you later if it worked.
Thanks a lot!!! i hope it works^^
I'm going through the exact same problem right now! But this happened to me using Heimdall. My phone is still recognized by Heimdall but when I try to reflash it I get this in the command prompt:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DD F\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\mod em.bin]
and this in the Heimdall window:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
i am too stupid
Ok, i am probably just way too stupid, but i can't find the download for heimdall one-click.
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
de4dw0lf said:
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
Click to expand...
Click to collapse
Did you download java?
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
DarsOnMars said:
I'm going through the exact same problem right now! But this happened to me using Heimdall.
Click to expand...
Click to collapse
You may have a bad download. You might try redownloading the file.
java is installed, i might have fixed that problem though. i think my download wasn't quite finished, because when i updated java, it wanted me to close firefox..
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
de4dw0lf said:
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
Click to expand...
Click to collapse
Here is my recommendation...
First used the attached .zip (assuming you are on a 64 bit machine) and uninstall all samsung and android drivers.
Then start over with Heimdall One Click. It will tell you whether you have the drivers you need or not, and if you do not, it will put up directions, send you to zadig and tell you what you need to do.
And you are in download mode.
Heimdall uses different drivers then ODIN.
Go here then and download 32 bit USBDeView.
I recommend restarting your machine after uninstalling drivers.
im on 32 bit
de4dw0lf said:
im on 32 bit
Click to expand...
Click to collapse
By the way... I recommended downloading the bootloader one click in case whatever you previously flashed was not for our device and changed your bootloaders.
"java -jar T959V-UVKJ6-One-Click.jar" --> is not the bootloader download.
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar = bootloader download.
hmm.. so it tells me to select Samsung USB Composite device, but it's not there.. :/
i am downloading the one "Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders" right now.
And after i am done im gonna restart my computer.
Not sure if this is the proper section for this but thought I would post this here as I'm sure it would highly assist people in development and other tasks. This is the button combinations you need to enter each mode.
ODIN/Download Mode
Make sure your device is completely off
Key Combos: Volume Down + Home
While holding both of them simultaneously press the Power button until you see a disclaimer on the screen
Then let go of all the buttons and press Volume Up to accept the disclaimer
Once the green robot is visible on the screen this indicates that handset is in now ODIN/Download mode
Recovery Mode
Make sure your device is completely off
Key Combos: Volume Up + Home
While holding both of them simultaneously press the Power button
As soon as the phone vibrates, let go of the Power button but keep holding Volume Up + Home
When you see the "Samsung Galaxy S III" logo (not just the word "Samsung"), right after that, the next screen you should see is your recovery
Don't let go of Volume Up + Home until you see your recovery
Updated OP to correct that Samsung devices do not have a "Fastboot" mode. ODIN mode replaces this and the ODIN software is basically a set of fastboot commands which is the only way to communicate to the device on a low level. Just a little FYI for everyone.
Heimdall should also work ,and it's cross-platform, unlike Odin. But somebody with a phone should test it to make sure it does.
http://forum.xda-developers.com/showthread.php?t=755265
Thanks for this handy information.
Since I am not at all familiar with Odin and how it works, could you ad a description of the steps to take in order to use Odin to flash an image file to the Galaxy S III? I watched a video on rooting, but the author never really showed much of the Odin screen on his PC and didn't say anything at all about how to use it. So far I keep reading to "use the PDA button", and I have the files downloaded and ready to go, but I don't want to make any mistakes.
Zoandroid said:
Thanks for this handy information.
Since I am not at all familiar with Odin and how it works, could you ad a description of the steps to take in order to use Odin to flash an image file to the Galaxy S III? I watched a video on rooting, but the author never really showed much of the Odin screen on his PC and didn't say anything at all about how to use it. So far I keep reading to "use the PDA button", and I have the files downloaded and ready to go, but I don't want to make any mistakes.
Click to expand...
Click to collapse
Check out the video linked in this thread: http://forum.xda-developers.com/showthread.php?t=1759980&highlight=heimdall
Happy rooting
Thanks. I guess it's really pretty simple after all.
I've seen some posts where folks had Odin still chewing on the process after 45 minutes. What do you recommend one do in that instance?
Zoandroid said:
Thanks. I guess it's really pretty simple after all.
I've seen some posts where folks had Odin still chewing on the process after 45 minutes. What do you recommend one do in that instance?
Click to expand...
Click to collapse
In 99% of cases such as that it is likely the fault of a bad USB cable or the computer itself. First try another cable, if still the same try to get access to something like a laptop and try there, usually USB ports work fine on laptops.
satadru said:
Heimdall should also work ,and it's cross-platform, unlike Odin. But somebody with a phone should test it to make sure it does.
http://forum.xda-developers.com/showthread.php?t=755265
Click to expand...
Click to collapse
You would think so but I haven't seen anyone have any luck with Heimdall on Verizon. If someone out there has gotten it to work, would appreciate some sort of guide.
open1your1eyes0 said:
In 99% of cases such as that it is likely the fault of a bad USB cable or the computer itself. First try another cable, if still the same try to get access to something like a laptop and try there, usually USB ports work fine on laptops.
Click to expand...
Click to collapse
Thanks. Luckily, I did not have this issue, and your thread here allowed me to root easily on the first try (I did use the OEM USB cable, having read that sometimes prevented problems for others). So thanks a lot for this thread. I am one of a presumed many who came here as this thread was spawned from a divergence on a previous root thread. Glad I did.
I did have an issue with Rom Manager while trying to flash CWM Recovery. It hung on the first attempt and I had to reboot the phone, but then it worked the second time. The only remaining anomaly I have here is that the nandroid I made is dated 1970. I'd like to know if others are having the same issue, and await some announcement for a fix. Does CWM Recovery actually have a support site? If so I'll post there about it.
Zoandroid said:
Thanks. Luckily, I did not have this issue, and your thread here allowed me to root easily on the first try (I did use the OEM USB cable, having read that sometimes prevented problems for others). So thanks a lot for this thread. I am one of a presumed many who came here as this thread was spawned from a divergence on a previous root thread. Glad I did.
I did have an issue with Rom Manager while trying to flash CWM Recovery. It hung on the first attempt and I had to reboot the phone, but then it worked the second time. The only remaining anomaly I have here is that the nandroid I made is dated 1970. I'd like to know if others are having the same issue, and await some announcement for a fix. Does CWM Recovery actually have a support site? If so I'll post there about it.
Click to expand...
Click to collapse
Happy to help.
And the date bug is a known problem with both CWM and TWRP recovery so far so don't worry too much for now and it won't affect it's use, just an annoyance. No ETA on a fix just yet but check in ROM Manager for an updated version possibly.
open1your1eyes0 said:
Happy to help.
And the date bug is a known problem with both CWM and TWRP recovery so far so don't worry too much for now and it won't affect it's use, just an annoyance. No ETA on a fix just yet but check in ROM Manager for an updated version possibly.
Click to expand...
Click to collapse
What I would actually like to see is CWM offering to let us name the nandroid when creating it, as well as where to put it. From what I have read this date issue is long standing, yet I have never encountered it before using rooted Android devices for the past 2 years until just now. I wonder if it is just this phone model causing the issue?
Does the battery need to be pulled for Odin to be accessed?
How about updating the OP to mention that you must be powered off before pressing the key combinations to enter ODIN mode. Would have saved me a lot of time.
rigman said:
How about updating the OP to mention that you must be powered off before pressing the key combinations to enter ODIN mode. Would have saved me a lot of time.
Click to expand...
Click to collapse
Section 6 of my guide stickied at the top if page:
Step 3: Power device off, then hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "download mode"
delete
Added more details to OP to avoid confusion
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Zoandroid said:
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Click to expand...
Click to collapse
Appreciate the bump but please stay on topic of OP. If not related, please post in corresponding appropriate thread.
Zoandroid said:
What I would actually like to see is CWM offering to let us name the nandroid when creating it, as well as where to put it. From what I have read this date issue is long standing, yet I have never encountered it before using rooted Android devices for the past 2 years until just now. I wonder if it is just this phone model causing the issue?
Click to expand...
Click to collapse
The paid version of ROM Manager allows just that, to name and choose the storage location of your Nandroid backups.
Zoandroid said:
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Click to expand...
Click to collapse
I was curious as to why backups I'd named were failing seemingly at random. Thanks for the heads up. I wonder if this applies to renaming a backup and is therefore correctable by doing so with no spaces in the new name?
Sent from my SCH-I535 using xda premium
open1your1eyes0 said:
Appreciate the bump but please stay on topic of OP. If not related, please post in corresponding appropriate thread.
Click to expand...
Click to collapse
I was replying to a statement made in post #10 by the OP in his own thread. My apologies if it was deemed inappropriate.
Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).