Related
NOTICE 10/18/2010:
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
I can vouch for this. It worked exactly as described.
Thanks!
Just to make sure after I do this I can flash any rom through odin without problem?
bobby915 said:
Just to make sure after I do this I can flash any rom through odin without problem?
Click to expand...
Click to collapse
I have flashed JFD, JI6, JI6 unofficial, JI6 OTA after flashing this and have had
no problem's
in general these files are written to parts of the phone that are usually never
written again after manufacturing and are responsible for getting the hardware
ready to load the kernel and then loading the kernel and booting the phone and
should not have any issues loading any ROM you care to flash.
Right now I can access download mode intermittently (maybe 1/10 times) by holding vol-up-down + power with usb plugged in. I cannot access recovery mode at all. Will this flash ruin my ability to access download mode? I feel like download mode is more important than recovery in case of a brick, but I would like the ability to go to recovery without adb or rom manager.
I've tried this 5 times, ODIN says failed everytime,EDIT Apparently 3rd times the 3rd time is the charm cause the 9th time it worked, Second Edit, The 9th time it started but its been 10 minutes so I assume it froze, Dammit.
Persanity said:
I've tried this 5 times, ODIN says failed everytime, Apparently 3rd times the 3rd time is the charm cause the 9th time it worked
Click to expand...
Click to collapse
So your recovery works now? Can you also get into download mode?
I'll add my Vibrant to the list of previously hardware locked phones, fixed by this.
I'd like to send out a HUGE thanks. Recovery and Download mode work every single time now. I can start playing around with roms safely.
Thank you so much
STEP BY STEP GUIDE
**UPDATE**10/14/10
STOCK RECOVERY VERSION OF HWLOCK FIX
untermensch has created a UPDATE.ZIP version of the fix
1) Download UPDATE.ZIP from OP or here http://www.megaupload.com/?d=2R2XOZ0X
2) Place UPDATE.ZIP in root of /sdcard not /sd
(If you have a previous UPDATE.ZIP file in root of /sdcard move it to another folder untill you have unlocked)
3) Use ADB to get into recovery
(use step posted below if you dont know how to use ADB)
(use command "adb reboot recovery")
4) Use vol down to navigate to reinstall packages press power to select
ODIN VERSION OF HWLOCK FIX
**NEW**
untermensch test file
(download from OP)
Everything you need minus drivers(or download individually in steps below)
http://www.megaupload.com/?d=66SSG9VR
step 1) go here and get the drivers and install them
http://forum.xda-developers.com/showthread.php?t=728929
step 2) download this zip file
http://forum.xda-developers.com/attachment.php?attachmentid=415810&d=1286579010
(load tar file from this zip in PDA section of odin after step 4)
step 3) go here download and follow guide to setup adb
http://forum.xda-developers.com/showthread.php?t=502010
(use "adb reboot download" to get to download mode)
step 4) go here get odin v 1.3
http://forum.xda-developers.com/showthread.php?t=790026
(run odin load tar in PDA make sure com4 or similar pops up click start)
FOR THOSE WHO NEED ADB HELP
REBOOT TO DOWNLOAD MODE WITH ADB
*must have drivers installed*
1) download androidSDK from here http://developer.android.com/sdk/index.html
2) extract the folder to root of your harddrive and rename it something short like ADB
3) on phone go to settings , applications , development and click USB debugging
then plug your phone into the computer
4) open windows command prompt and type this (hit enter after each line)
cd c:\
cd ADB\ (or whatever you renamed the folder in step 2)
cd tools\
adb reboot download
5) flash tar with odin
Sent from my SGH-T959 using XDA App
No, It did not work, The 9th time it actually started instead of saying failed immediately, But after 20 minutes nothing had changed and then odin cr5ashed and now my phone is soft-bricked/bricked whatever it is. All I know is im ****ing pissed. Can somebody point me in the direction of a complete restore thread? EDIT: Yeah I finally got it, Thank god I have never had a problem getting into download mode, When I say got it I mean restoring my phone to work not getting recovery to work, If I flash J14 first then J16 am I gonna lose the ability to go into recovery mode if the J14 update does actualy let my phone go into recovery?
untermensch said:
The leaked JI4 firmware contained the files needed to get the our phones unlocked
attached is an odin flashable tar with sbl.bin, boot.bin when flashed your phone wont ignore
the vol up + vol down + power buttons and you will be able to access recovery.
if you haven't used odin before follow AgentFour20's instructions http://forum.xda-developers.com/showpost.php?p=8541107&postcount=35
note:
1. the port wont be com4 for everyone as long as odin shows a com port you should be fine.
2. you might not need adb this method worked on my locked phone http://www.youtube.com/watch?v=rqxearzXrVY
you can flash this over any ROM or firmware and will probably never have to flash it again because boot.bin, sbl.bin are rarely included in firmware.
as usual use caution when flashing your phone, I am not sure if you can get back into download mode if this flash fails, So flash at your own risk!
for more info check out the I9000 thread:
http://forum.xda-developers.com/showthread.php?t=785201
and the original thread:
http://forum.xda-developers.com/showthread.php?t=802763&page=3
Good Luck!
md5 for tar file = d18f9d23d3060260a4e7edc1b6321941
Click to expand...
Click to collapse
Gonna put in my vote for one recommendation for you people who have a dickens of a time getting into download mode and are afraid of Odin3 leaving you stranded.
Try using Odin3 v1.30 instead of Odin3 v1.00 (it's linked in the Bible thread). My failure rate on flashing with v1.30 so far is zero. My failure rate when I was flashing with v1.00 was more to the tune of 50% of the time. I'm not hardware locked, so this is less scary for me than it is for you.
Just a safety tip...Best of luck!
sounds like solution is simple, but why did this occur on some vibrants in the first place?
SamsungVibrant said:
sounds like solution is simple, but why did this occur on some vibrants in the first place?
Click to expand...
Click to collapse
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Awesome....used odin 1.3 and this took a few seconds and worked flawlessly
if you follow the instructions in the posts above, don't see how you can go wrong
I can now access download mode and recovery...and I can sleep a lot easier knowing that if something happens I can fix it now
Yes! Masterotaku thank you so much for posting about odin3 v1.3, 1st time it work for J14 over J16, I can now boot into download and recovery mode. Sweet.
masterotaku said:
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Click to expand...
Click to collapse
hmmm interesting, seems like samsung isn't consistent with their screen tints also. They need to get quality control under quality control
Wanted to add that this worked for me as well. Thanks for the info.
Worked on first try, Odin 1.3. Thank you so much for this fix! I knew holding out on replacing my vibrant would pay off =)
Now I got into recovery by both vol + power then release power, but how do you guys get into download mode? I used to be able to get there occasionally by doing that same key combo, but with usb attached.
EDIT: Wow that was easy.
RECOVERY MODE: Hold both volume buttons and power, once vibrant logo shows up, release power.
DOWNLOAD MODE: Hold both volume buttons (no power) and plug in USB. Instant!
EDIT: Honestly I can't thank you enough. This is so amazing!
Thanks so much, this really works, my 1st time ever using odin 1.3
and finally figure out what adb is. Before even pulling the battery would
not get me into download,and the only way to get into recovery was using
clockworkmod. This really works!!! thanks you thanks you.
Everything is not as good as it seems. I managed to flash the fix all right and now I have download mode. But my friend had done the same steps as myself but odin FAILED to flash the fix. It just said:
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
And his phone is totally bricked now.
It is really dangerous to use ODIN on hardware locked phones... Too high chance of failure to flash. ((
Hello,
I verified that I am able to enter download mode by plugging in the USB cable while pressing both volume buttons with the device turned off. I also verified that I can enter recovery mode by pressing both volume buttons and the power button. So I am pretty sure that I know how to enter the modes.
I then ran the Odin version from http://forum.xda-developers.com/showthread.php?t=731989 (by mistake, I didn't know it differed from the one in http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html). I assume that simply overrode everything with the stock ROM instead because I did not get the chance to select the SpeedMod kernel.
However, after that the hotkey method was no longer working. I was only able to enter download and recovery mode using adb. I used this to flash SpeedMod using the correct Odin version from the SpeedMod page.
Then I proceeded by going into recovery mode and extracting captivate-efsbackup.zip. I went into download mode (again with adb, keys still didn't work) and flashed cm7-captivate-initial-kernel.tar.
Now, however, I'm in real trouble. I can enter neither recovery nor download mode. No matter if I use hotkeys or adb, the system reboots, but then just shows the "Galaxy S\n cyanogen^(mod)" image.
Anyone able to help? Why aren't the hotkeys working anymore after running Odin?
I have no explanationas to why buy do have a suggestion. Try the AIO tool box. If the phone boots, just enable usb debugging and follow instructions. You should probably use the 3 button fix option.
I recently had done a clean up of my cappy because after tons of flashes it had become a mess. After flashing back to stock I lost dl mode and recovery. Whipped out the AIO...ver.2.5 , booted phone, put in debug.. Reformated with 3 button and boom!, back in business. Be sure your net framework is current 4 version, install the C++ lib as siggested.
Took a likely pain in the ass and turned it into an inconvenience. Just follow the instructions...
Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
First of all, what model of Captivate do you have (the model number is underneath your battery, on the phone itself. It will be a number between 1006-1014).
And I hope you do realise that CM7 is a particularly difficult (than standard) ROM to flash, and if you don't know what you're doing (or miss a step), you can perma-brick your phone easily.
If you can't get into Download Mode by any means, then the only last suggestion I can give you is to try a USB Jig (search around in the Captivate Forum here, you'll see what I mean).
Thanks for the suggestions. Here is how I recovered:
Download SpeedMod Kernel
Create a nandroid backup on a working phone, copy that over to the broken one
Copy zImage from SpeedMod kernel to SD on broken phone with adb
Enter shell mode on phone
Look into misc/recovery.fstab to figure out the name of the sdcard block device
Mount sdcard with `mount [blockdev] /sdcard`
Flash zImage with `flash_image boot /sdcard/zImage`
Flash nandroid backups with `flash_image {system,cache,datadata} /sdcard/{system,cache,datadata}.img` (but not data)
Leave the phone without battery for at least 1 and at most 6 hours (my phone appeared completely dead after this operation, not even adb shell access, so I went to bed frustrated)
Now you can boot into download mode again using "adb reboot download" (which didn't work when running the CM7 kernel)
Use One Click Odin to revert to stock firmware
Install 3ButtonFix to get combos working again
Note that the original problem that caused all the trouble was that flashing the stock ROM with Odin One-Click disables the 3 Button combos. You have to use the 3ButtonFix to get it working again.
Nikratio please help me i was updating samsung galaxy 5 2.1 eclair to 2.2 froyo but when i was using odin then it stops working and i unplug the device the after that phone is not getting switched on and even not getting is recovery mode ... m very sad and even dnt have the backup of any phone and none of my frnd have android phones so that i have backup please help me bro m afraid of my mom too coz i just bought it few time back please hem me bro
TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM
Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.
Just out of curiosity, what is your build number?
I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.
May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App
I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?
Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App
I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?
You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.
FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)
ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......
Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.
By soft bricked, in my situation, I mean that the only mode I could successfully enter on my SGH-T679 was ODIN download. Recovery and normal boot both locked up no matter how long the phone was allowed to run. Or it reported that firmware failed and to use Kies but Kies failed to recognize the phone.
How I bricked it
I was given one of those fitness wrist bands for Xmas, but it's from a startup company and their app only works in 4.3 or higher. So I got adventurous and tried CM 10.2. I got CM to run but couldn't get Google services to work. I finally gave up and started to revert to stock. When I had my first problem at 2am, I should have gone to bed and finished after a good night's sleep because I soft bricked it. At first, I was running flashes from my internal SD card and could only get it to flip between stock recovery and CWM recovery, it wouldn't take full stock flash. Finally, one CWM recovery flash failed and my recovery mode got stuck so it only showed the hat and gear icon and at the bottom of the screen it said "CWM 6.etc..." and never went further. But I could still get to ODIN download mode.
And that's when I got really stupid. I messed with things I didn't understand in ODIN. Did you know that if you try to run ODIN Multidownloader 4.43 using the "Debug Only" and "MD5 Ram Check" options that you can fully soft brick a T679? If allowed to run for a while (10-20 minutes is sufficient), then after forcing the phone to restart, it will result in the screen about firmware failed please use Kies for recovery (but then Kies can't see the phone because the recovery is bricked).
Long story short, after hours of trying this and that, I finally found a webpage that said you can download the CWM recovery via ODIN. That would have worked if I hadn't gotten the wrong version (resulting in lots of screen flickering), but it proved to me that I might be able to fix the recovery using ODIN.
Here's the walk thru of how I restored my stock recovery and ultimately got back to stock ROM:
Software required:
A zip software that can handle TAR files (I used PeaZip)
Go to this wiki http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G and scroll down to "Flash to stock via ODIN", you need the software discussed and read thru the "STEPS" section just below that
You can first try using ODIN as described in the wiki. But if that doesn't work, you can try what I did...
Restoring stock recovery
If you haven't already, unzip the uvlg3.odin.zip file that you got via the wiki link above
From the .tar file that was in the zip, extract recovery.img and then put it inside a new TAR file (call it something easy like recovery.tar) (depending on your zip program, use "add", do not use "convert", you need the .img file inside the .tar file)
Refer to the wiki link above for more help on ODIN but basic steps are:
- Run ODIN as admin (not sure if it matters if you disable auto-protect on your antivirus software but I followed that recommendation)
- Using "OPS" button, select the Ancora.ops file that you extracted from the zip file
- You may have to recheck the "One Package" box to be able to then select your recovery.tar using "One Package" button
- Press "Start" and cross your fingers
You hopefully have now restored the stock recovery to your phone.
Further steps
I went a step further. I extracted the entire .tar file (not just the recovery image) and put each item into its own new .tar file. I used ODIN to individually load each item. I did first try to load the full file but I now think mine was failing to load system (which is pretty critical, especially if you followed directions that included "format /system"). (Note, the preload file might not work, didn't for me ; I found several posts about it and the general answer was to ignore it.) One trick to this is to watch and push the Vol Down and Home buttons when ODIN reboots the phone so you go back into download mode. Oh, and change the reset time to 30 seconds (I tried 1 but ODIN changed it to 30) so you don't wait as long on "reset". I'm not sure if it would have made my first normal boot go faster if I'd gone to recovery mode between ODIN downloads. I do know it took my phone several minutes on the first normal boot. I'm sure those of you who have bricked phones can appreciate the feeling of waiting for the stupid startup jingle and the relief when it actually plays.
Oh, and save yourself some bother by rebooting 2 or 3 times before you try to do much w/ your phone once you get back to stock ROM (or some other ROM). I was a little freaked because my wifi didn't work but after some googling, I learned Android can require a couple reboots before all services (especially wifi) load properly (which makes me wonder if I should try CM 10.2 again with more reboots... am I a glutton for punishment enough to try???).
Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!
mcjenda said:
Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!
Click to expand...
Click to collapse
Did you try odin 3.10 by any chance? That could be the problem. Use odin 3.07 or 3.09, boot manually into download mode with complete shutdown & using vol down + power key and odin the stock ROM, reboot and do the same with TWRP (hold down the vol up key after flashing recovery when it is rebooting)
JASONRR said:
Did you try odin 3.10 by any chance? That could be the problem. Use odin 3.07 or 3.09, boot manually into download mode with complete shutdown & using vol down + power key and odin the stock ROM, reboot and do the same with TWRP (hold down the vol up key after flashing recovery when it is rebooting)
Click to expand...
Click to collapse
Hi there, Jason.
Yes, I did exactly as you say - got to the download mode, plugged in, ran Odin (tried 3.10, 3.09 and 3 v1.85) started flashing the latest Stock ROM and the I only got as far as the "system.img.ext4", when the download failed. Sometimes that happened even earlier, saying that there was no PIT etc.
When trying to flash the CWM recovery, it goes through OK, but then when trying to get into it, the screen just goes black, as described in my previous thread - "CWM or TWRP Recovery Black Screen".
I am stuck.
But I still hope that I am not a proud brick owner
John
mcjenda said:
Hi there, Jason.
Yes, I did exactly as you say - got to the download mode, plugged in, ran Odin (tried 3.10, 3.09 and 3 v1.85) started flashing the latest Stock ROM and the I only got as far as the "system.img.ext4", when the download failed. Sometimes that happened even earlier, saying that there was no PIT etc.
When trying to flash the CWM recovery, it goes through OK, but then when trying to get into it, the screen just goes black, as described in my previous thread - "CWM or TWRP Recovery Black Screen".
I am stuck.
But I still hope that I am not a proud brick owner
John
Click to expand...
Click to collapse
Are you using the original USB cable if not then try with another cable. Also what is the device name shown when you boot into download mode
mcjenda said:
Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!
Click to expand...
Click to collapse
Hi. Try this:
Remove the battery and USB cable from your phone, and wait at least 3 seconds.
Place the battery only back in your phone.
Fingers on volume down and home, then another on power. (cold boot directly into download mode - this is important!)
Press up to enter download mode.
Insert USB cable into phone and lie it down somewhere it won't move or be touched during the flash.
Download a good current copy of Odin from:
https://idlekernel.com/flash-tools/Odin_3.10.7.zip
Extract the archive and run Odin.exe
Download this emergency recover tar for your device (newest firmware revision available as of right now):
https://idlekernel.com/flash-tools/recover/BL_I9295XXUDPA4_RECOVER.tar.md5 (also has official TWRP 3.0.0-2)
Insert "BL_I9295XXUDPA4_RECOVER.tar.md5" in the [BL] slot.
In the Options tab put an [✔] in the "Phone Bootloader Update" checkbox.
If you don't have anything you need on your internal storage, put an [✔] in the "Nand Erase All" checkbox.
Click [Start].
Once the progress bar is near finished, place your fingers on volume up and home to enter directly into official TWRP 3.0.0-2.
If you used the "Nand Erase All" feature earlier, you will need to go into Wipe -> [Format Data] -> type "yes" for your data partition to be usable again.
Hopefully this will get you past your black screen issues.
PS. Remember to flash stock boot.img with your system.img.ext4, as you cannot boot a ROM without a matching boot image.