Database Develop

Is the build version of.....

A Bell Canada Galaxy S I900UGJH2?
Looking to revert back to 2.1 from a leaked Bell 2.2 build, since the phone ended up in a boot loop, managed to get it to the Galaxy S screen after flashing the above build with the 512 pit, but thats about it, its just a black screen ATM, recovery mode doesnt work with the 3 button combo but download mode does, am I missing something here? Do I need to add phone and CSC files too?

Yes. Any firmware starting with i9000UG is a Canadian firmware.
Search the general forums for someone who has linked to a JH2 firmware that also includes an SBL file. Depending on which 2.2 firmware you flashed, you might need this.
If none of this works, flash JL2 and call it in for service/replacement.

gtg2 said:
Yes. Any firmware starting with i9000UG is a Canadian firmware.
Search the general forums for someone who has linked to a JH2 firmware that also includes an SBL file. Depending on which 2.2 firmware you flashed, you might need this.
If none of this works, flash JL2 and call it in for service/replacement.
Click to expand...
Click to collapse
Thanks a lot I appreciate the reply, Ill take a look around for the JH2
If this doesnt work and I flash the JL2 do I only need to flash that PDA and the 512 PIT? I assume I would flash the JL2 pretending that I upgraded to 2.2 when it was official in Dec and now its messed up to have it covered under warranty?

Here is how you fix this:
- First off, download odin3 v1.7
- then download i9000UGJL2 and i9000UGJH2 (the JL2 is the recent stock rom, JH2 is 2.1 that your phone shipped with, they are both .tar files so make sure you see that)
- download the latest speedmod kernel from the development section
http://forum.xda-developers.com/showthread.php?t=822756
get the "speedmod-kernel-k12p-500hz.zip"
- boot odin
- put your phone into download mode then plug it into your computer
- odin should see it (you will see under ID:com)
- click the pda button and locate the speedmod.zip file
- click start, it wont take long and your phone will reboot (you should have recovery mode now but we're still not done)
- put your phone into download mode again
- close and reopen odin so it's back to default
- plug your phone in and make sure odin detects it
- leave everything default but check off "phone bootloader update"
- click the PDA button and find the i9000UGJL2.tar file
- click start (this time it will take longer and flash the entire ROM)
- now when you go into recovery mode it should ***** about dbdata missing
- put your phone back into download mode
- close and start odin again (leave everything default this time)
- plug in your phone and make sure odin detects it
- click the PDA button
- locate the i9000UGJH2.tar file and then click start
- this will flash the stock rom your phone shipped with, once it's done it should boot fine
- then you can plug kies in and flash JL2 on top OR flash a custom rom
- good luck, let me know I can post the stock ROM's if you cant' find them but they are on this site somewhere
PS your phone isnt' dead, so dont waste your time getting it replaced, it can be brought back to life so dont worry. I was in the same boat as you once and if this works dont forget the thanks button!

spectre85 said:
Here is how you fix this:
- First off, download odin3 v1.7
- then download i9000UGJL2 and i9000UGJH2 (the JL2 is the recent stock rom, JH2 is 2.1 that your phone shipped with, they are both .tar files so make sure you see that)
- download the latest speedmod kernel from the development section
http://forum.xda-developers.com/showthread.php?t=822756
get the "speedmod-kernel-k12p-500hz.zip"
- boot odin
- put your phone into download mode then plug it into your computer
- odin should see it (you will see under ID:com)
- click the pda button and locate the speedmod.zip file
- click start, it wont take long and your phone will reboot (you should have recovery mode now but we're still not done)
- put your phone into download mode again
- close and reopen odin so it's back to default
- plug your phone in and make sure odin detects it
- leave everything default but check off "phone bootloader update"
- click the PDA button and find the i9000UGJL2.tar file
- click start (this time it will take longer and flash the entire ROM)
- now when you go into recovery mode it should ***** about dbdata missing
- put your phone back into download mode
- close and start odin again (leave everything default this time)
- plug in your phone and make sure odin detects it
- click the PDA button
- locate the i9000UGJH2.tar file and then click start
- this will flash the stock rom your phone shipped with, once it's done it should boot fine
- then you can plug kies in and flash JL2 on top OR flash a custom rom
- good luck, let me know I can post the stock ROM's if you cant' find them but they are on this site somewhere
PS your phone isnt' dead, so dont waste your time getting it replaced, it can be brought back to life so dont worry. I was in the same boat as you once and if this works dont forget the thanks button!
Click to expand...
Click to collapse
Ok well I reflashed back to JH2 already, Im pretty sure I was on JL2 when it went into a force close, then was just constantly boot looping, so now Im on JH2 and it boots but only to a black screen, after flashing it through Odin the phone reboots itself into recovery mode, I tried doing the update.zip that was showing in the card but it gives me the E:Error business, so I just selected the reboot, which takes me to the black screen after the S logo is done
My only concern is if I apply the speedkernel pda and that doesnt fix it then if they were to actually check the phone and they find the modified kernel they will know I was messing about with it, one other issue I was concerned about was not being able to get into download mode, since I cant get into recovery with 3 button, the speedmod kernel doesnt change any of the secondary bootload options does it?
*edit* I misread what you posted so it does change the bootload by allowing the 3 button to work

You can always flash back, if it takes a flash through odin then it will flash back. If you follow those steps you should be fine, msg back
Sent from my GT-I9000 using XDA App

spectre85 said:
You can always flash back, if it takes a flash through odin then it will flash back. If you follow those steps you should be fine, msg back
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks Ill give it a try
Ill post back how it goes

The challenge is that the symptoms being reported are also associated with unrecoverable problems. It would be great if you could enter recovery and indicate what if any error msg you're getting below the menu.
If the above directions from spectre85 don't work (great post BTW), don't kill yourself. Call it in for a replacement.

gtg2 said:
The challenge is that the symptoms being reported are also associated with unrecoverable problems. It would be great if you could enter recovery and indicate what if any error msg you're getting below the menu.
If the above directions from spectre85 don't work (great post BTW), don't kill yourself. Call it in for a replacement.
Click to expand...
Click to collapse
Ya I agree, once you get into recovery mode you can tell us the error you are getting, if it's complaining about missing dbdata or some kind of missing data your still ok. If it's the dreaded can't mount SDcard then your sunk

Bahh I think its soft bricked I tried spectre's advice and it was boot looping again, plus even with the new bootload it still wouldnt go into recovery, I just put on JL2 and am gonna bring it to Bell..... good thing there was issues with the version so I can get this under warranty
Thanks for your help guys I appreciate it
Yall got double and triple thanked

Odin successful, but still stuck in boot loop

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.

[Q] i9000 halts after Semaphore CWM installation

So I have this old Samsung i9000 lying around and I wanted to give it a new life with an update (ran Android 2.2, so it was pretty useless).
I started by looking up all installation instructions I could find (took me a whole day to make sure I had it right) and the procedure was:
Update to CM9 first, then update to newest CM.
Pretty simple I thought. But as usual I ran into some troubles I can't get myself out of. That's why I'm asking you guys to help out.
What I did: set up all the drivers and downloaded the Heimdall suite and Semaphore 2.7.4 CWM. Then ran the "heimdall flash --kernel zImage --no-reboot" command. It uploaded the zImage to the phone. Pulled the battery, booted with Vol Up & Home & Power. At this point I'm stuck on the GALAXY S GT-I9000 SAMSUNG boot thingie. When I press Vol Up & Vol Down & Power it seems as if it bootloops. The boot thingie flashes.
I can't get into the system, I can't get into recovery, I can however set it up to download stuff (the yellow under construction Android sign), so I'm guessing there is a possibility to upload something else that works in stead...

Lex_Michdeandroid said:
I can't get myself out of. That's why I'm asking you guys to help out. .
Click to expand...
Click to collapse
Just to let you know what you did wrong.
when you have a 2.2 froyo ROM, you cannot flash a gingerbread kernel on it and hope to get it booting.
The solution is , just follow this guide and flash the gingerbread ROM as mentioned after that you can chose what custom ROM you want on it .
Check this out! You , YES! you are an " Android ". Not your phone but U.​

Lex_Michdeandroid said:
So I have this old Samsung i9000 lying around and I wanted to give it a new life with an update (ran Android 2.2, so it was pretty useless).
I started by looking up all installation instructions I could find (took me a whole day to make sure I had it right) and the procedure was:
Update to CM9 first, then update to newest CM.
Pretty simple I thought. But as usual I ran into some troubles I can't get myself out of. That's why I'm asking you guys to help out.
What I did: set up all the drivers and downloaded the Heimdall suite and Semaphore 2.7.4 CWM. Then ran the "heimdall flash --kernel zImage --no-reboot" command. It uploaded the zImage to the phone. Pulled the battery, booted with Vol Up & Home & Power. At this point I'm stuck on the GALAXY S GT-I9000 SAMSUNG boot thingie. When I press Vol Up & Vol Down & Power it seems as if it bootloops. The boot thingie flashes.
I can't get into the system, I can't get into recovery, I can however set it up to download stuff (the yellow under construction Android sign), so I'm guessing there is a possibility to upload something else that works in stead...
Click to expand...
Click to collapse
First of all flash XXJVU official and its root. You will surely get out of the problem.
Read my post in the below link. I tried the process easy as much as I could.
forum.xda-developers.com/showthread.php?p=47034690#post47034690

Of course... I'm an idiot... I thought I would have the newest update from OTA, but didn't check what was the latest official OTA...
Anyway, back to the lab, will update as soon as possible.
Edit: filerio is really ****ty... I'm going to try to find other downloads...
Edit2: got files from Rohitdahiya's post, now waiting for downloads to complete
Something else, the yellow thing isn't coming up in Odin, so I guess that will be my next problem. I can't put the phone in 'debug mode' because the main system doesn't start. Also something that occurred to me was that when charging the big green battery doesn't come on screen anymore. It just shows a static circle of bars...
Heimdall could connect to the phone no problem... Downloaded the Heimdall rescue kit, but I'm not sure how to use it...
Edit3: And indeed the Odin software doesn't recognize the damn thing... Trying to find an install for this KIES.exe to make sure I have the right drivers installed...
Edit4: Awesome. KIES starts "Installing device drivers. This may take several minutes." and never stops... Now my device isn't detected anymore... Just great.
Edit5: I reinstalled drivers with Zadig. Found out Heimdall rescue was just a .bat file... I already said I am an idiot right? Anyway, now trying the rescue kit again...
Edit6: Using the Heimdall rescue was all there was to it... I'm retarded! Had this rescue kit sitting there for a week and it didn't occur to me to JUST USE THE GAWDDAM BATCHFILE INSIDE THE GAWDDAM FOLDER...
Anyway! After running the "Restore.bat" file and choosing the 1. option (Flash and repartition) it went on doing all kinds of good stuff and now I'm running 2.3.6... Now for the next step, getting it to run the latest CM (or a variant).
Edit7: Okay, good things come to those who wait. Started all over after getting the 2.3.6 on the device. Followed CM instructions:
-USB Drivers through Zadig
-Put the phone in download mode (Vol Down + HOME + Power), plug in USB
-Extracted the zImage from the .tar into the folder that holds heimdall.exe
-Run "heimdall flash --kernel zImage --no-reboot"
-Make sure he's done, take battery out, reboot into recovery (Vol Up + HOME + Power)
Find out it's working fine! THANK YOU!
Now I'm going to see if I can get the latest CM running. Again, thanks!

How I un-soft bricked my Samsung SGH-T679 and restored recovery mode

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???).

[Solved] Stuck in Download Mode?

Hello, been a while since I unlocked and installed custom ROMs. Recently I bought a cheap Note 9 and since it is already out of warranty, might as well get a custom ROM to get rid of Bixby.
I used Odin to flash TWRP as per the instructions and now my phone refuses to get out of it. It reboots in to Download mode no matter what button combination I use. Vol down + Power key gets me back in to download mode, if i press all the buttons, same thing. No matter what combo of buttons I use, it just keeps rebooting in to Download mode.
I cannot even turn the phone off... lolwut
The first time it booted in to TWRP, i flashed my ROM and I wanted to reboot to start it but it just keeps coming back to Download mode.
Any ideas?
===========
Ok i somehow fixed it.
When I tried to flash the stock firmware, it gave me Device 4 Binary 3. Googled it and apparently I flashed a BL that's a higher version.
So I fixed it with this genius post from the S6 Edge+ forums by Samuwelle.
---
RE: sw rev check fail device 4 binary 3 error
For all of you who get a similar error while downgrading:
1. download your firmware
2. download 7-Zip
3. download Odin
4. download tar tool
5. READ the guide to the tar tool
6. create the tar.md5 for boot.img, system.img and modem.bin ONE at a time and always cut the created files into a second folder. (I dont know if you need the .back files but just to be shure put them in, too
7. put your phone into download mode
8. start Odin (make shure phone is connected)
9. navigate to the boot.tar.md5 for "BL", the system.tar.md5 for "AP" and modem.tar.md5 for "CP"
10. press "Start" => DONE
This works for me and might not work for you.
I do not take responsibility for any damage YOU did to your phone.
Feel free to ask questions.
Hope this saves someone's day.
Sam
---
I downloaded the stock beta android 10 ROM, did the above, flashed it with Odin, did it 4 times because the progress bar did not move at all. Finally, the last attempt I just let it run while I played some games, after about 20mins, it still hasn't moved, gave up, pulled out the cable and immediately got an "Error updating, please use Smart Switch Emergency Recovery". SS did not work, did not detect.
Tried the above method again, no dice. I could not get out of the error mode now, so I just opened Reiboot Android and clicked the little button to exit download mode, and for some reason it started booting! LOLOL
I guess it flashed successfully, just that the progress bar for Odin didn't move. Either way, I ain't touching **** now. On Android 10, One UI 2.0, gonna use this til the official thing comes out.