Related
Ive been reading different posts and i keep hearin people say ODIN back to stock... can somone please explain this in newie terms? and can i do this after root to get my phone exactly how it was when i bought it??
if so i've deleted some stock apps and was wondering if those will be back....
Sent from my SPH-D700 using XDA App
Yes.
http://forum.xda-developers.com/showthread.php?t=963652
It literally runs itself after you get your phone into download mode (turn it on while holding 1 on the keyboard) and it does return you phone to the way it was out of the box.
there is a thread in development by Whosdaman to get ODIN . It will flash your phone back to stock exactly how you got it...everything will start from scratch. You will have to download the DI18 files in the thread and drivers etc. It will bring back everything from out of the box Epic...
Edit: i was too late ^^^
hmmm, ok... someone posted a link with steps that seem way wayyyyy more complexed then turing the phone on and holding "1".... an i do it either way? or is one more proper than the other...
Sent from my SPH-D700 using XDA App
Nixo - thanks... u actually kinda answered my last post =D
Sent from my SPH-D700 using XDA App
I can surely tell you, you need to search and read up, as there are plenty of posts on this topic. This also tells me I really need to keep working on my "Welcome to Hacking Samsung Phones - What you need to know" Thread.
Basically ODIN is what users can utilize to return their epics to stock. ODIN is a program that you run on your computer that communicates with your phone and returns everything back to a stock factory version of android.
In order to use it on your phone you need to put your phone into "Download Mode". Instead of the traditional "three finger salute" that you would use to boot into recovery, you slide open your phone and press the number "1" key and then while holding it down, press the power button. The screen will boot up with yellow text and a yield sign that declares it is in "Download Mode" You then run ODIN on your desktop. Once ODIN opens up you plug the usb cable into your phone. Assuming you have the correct drivers installed, you will see a COM response on the ODIN application. From that point you can load .tar files into ODIN, click "start", and ODIN wipes your phone and returns it to stock fresh out of the package. Because our phones have this option it makes it very difficult to brick the EPIC.
Hope this helps.
nellison1470 said:
Ive been reading different posts and i keep hearin people say ODIN back to stock... can somone please explain this in newie terms? and can i do this after root to get my phone exactly how it was when i bought it.
Click to expand...
Click to collapse
The only reason to odin to stock (DI18) is if you plan on getting an OTA or use the update.zip method. If your going to utilize odin, then save yourself the hassle and just odin directly to EB13 from wherever you happen to be. ODIN is a factory production tool to flash a bunch of phones all at one time, but it works just as well on one phone.
watermoore - THANKS!!!!! i have better understanding now of what the heck the hype about Odin is. you explained it perfect and used terms i would undersand since im a newbie...
i really appreciate everyone's help
Sent from my SPH-D700 using XDA App
nellison, alternatively you can just use the Windows installer version provided by Samsung, which is basically a prepackaged Odin & EB13 update all in one. I haven't used it, but it seems to be very noob-proof from what I've read: http://downloadcenter.samsung.com/c...22061912233/Epic4G_FroyoUpgrade_EB13_Tool.exe CAUTION!!! Be advised, this will wipe your phone (but leave the contents of your SD card intact), so you'll have a clean, factory-fresh installation of EB13 / Froyo.
If you're looking to do an "upgrade" and keep all your settings, apps, etc., then look for a guide on applying the update.zip, which I conveniently have here: http://forum.xda-developers.com/showpost.php?p=11546546&postcount=15
Good luck!
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. Sorry but the links to some of the files are gone I don't have them anymore so I suggest you look through the comments someone will have someplace to get what you need. Your recovery methods may have changed but this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
This is a great source of information. The formatting could be a little better though. Perhaps break up those great giant paragraphs a bit. It would be easier to follow along. Especially for noobs in a panic state after "bricking" their phone.
Great work though. This should be stickied.
I will Update thread to an easier format over the next few days. Thanks for the tip, i looked good to me but now i see what you are talking about. It took hours today to gather all the info, pull up each program ans walk through it. I guess I was in mental overload.
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You were that guy.
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Oops, but at least i was consistant on the typo...LOL. I will fix it this weekend.
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Figured out this morning I wasnt using my factory usb cable switched cables odin'd stock eb01 worked perfectly now I feel retarded.
Sent from my SCH-I500 using XDA App
Excellent write up. Thanks a bunch.
What are some other differences in Odin 1.7 vs 1.3? I have used 1.3 many times and never had any issues. Any improvements?
Thanks so much Dale! headed to work now, but will try this tonight
Rayn1328 said:
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
More reasons as to why you should never fear bricking your phone and testing new kernels and ROMs. Thank you for the thorough tutorial.
cbalt said:
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
Click to expand...
Click to collapse
I prefer what i think is a much simpler method. Just go to this link and follow Post 2. I don't believe I have ever had it so easy to root a phone:
http://forum.xda-developers.com/showthread.php?t=948722
nice write up, thanks for posting. I hope I never have to use it
netwalker0099 said:
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Click to expand...
Click to collapse
Got that once cause i didn't install the drivers in zadig. I installed it, didn't reboot PC, worked fine. If you had the CSC unchecked then you didnt install a cache or database, so no your phone wont work like that. Unless you ran into something new, follow this guide step by step, and it should work. I would also make sure you get the files from here, they are tested and known to be good. There are some incomplete, and bad files out there, these work.
Heimdall is officially the greatest piece of software ever created and DaleV is my hero!!! FINALLY have my phone up and running again! Was serious contemplating dropping around $300 for a new phone on Craigslist.
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Oxirane said:
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Click to expand...
Click to collapse
after it failed did you unplug then replug and go back into download mode? also I updated the OP with a superuser.zip file it works better than the one in the market for showing you have root access, I have no idea why.
Also you might try a different usb port, sometimes that does the trick.
I've unplugged and replugged and rebooted it a dozen times... it first goes to 2e recovery, then I reinstall packages and it reboots to the simplified download mode with just basic little icons. Doesn't get recognized by the computer though. :/
Wont boot into anything but 2e, and from there into oldschool download mode.
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
want a droid said:
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
Click to expand...
Click to collapse
Odin the proper clockwork,reboot straight to it, wipe data and then flash CM7 from the SD card.
Please give me step by step instructions with links. I'm an HTC Thunderbolt guy myself so I am having a hard time finding all the right links and stuff. I really appreciate your help!
First sticky in this forum has all the links and steps.
Sent from my SCH-I500 using Tapatalk
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
want a droid said:
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
Click to expand...
Click to collapse
Really? did you look at the sticky?
Code:
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. All of the files, I cant guarantee links to other OP's, will still be available, I wont take them down. Your recovery methods have not changed, nor have the PIT files, so this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1026746
odin...
atlas_v2.2.pit
CI500_VZW_ED05_FROYO_REL.tar.md5
check repartition
then follow the CM wiki
I don't understand why I'm getting this: http://imgur.com/WkDsK
Sorry for rotated picture.
I'm in the process of flashing the verizon firmware but it's taking forever to download. I thought I could just odin the CWM?
You better do some research before u brick ur ****...there are guides all over the place on how to get back to stock/flash roms. And last but not least all questions should be posted in the q&a section...that's what its there for...seriously use it!
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
When I try to connect it to my mac it says it can't read what I'm trying to connect. When I connected it to windows laptop it says its a CD drive that is write protected.
I can't move any files in or out. Also when I try to flash a rom zip in recovery it doesn't work.
I'm in the process of trying to restore her MIUI backup. Here's to hoping that works.
EDIT: Supposedly the restore worked, but here is part of the error that showed when trying to flash a zip (top text): http://imgur.com/X1RQL
Oh and I'm stuck on the Samsung screen now...what do I do?
want a droid said:
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
Click to expand...
Click to collapse
fail.
if you did CM Wiki, you have CWM 4.X, not 2 or 3
you need to flash back to stock like i said
I did flash back to stock. Anyways in the broken clockwork recovery I decided to try and install MIUI again and when I clicked it it took me to an orange recovery.
Then I flashed her backup and it loaded up fine. Hopefully everything is back to the way it was. I'm not sure what ever went wrong in the first place.Thanks for your help.
Dude...sounds like you just made it hard. Its actually quite simple.
Pull battery, put in download mode.
Odin the Verizon firmware with atlas.pit and repartition checked.
let it boot, then shut it back down and go back into download mode and Odin the fixed recovery for CM7. Then flash MIUI and profit.
It shouldn't take but about 15 minutes out so for the whole process
Swyped via Tapatalk
Well I wish you had been here last night. I was told to do the heimdall thing and then after all that the phone wouldn't be recognized in odin.
It was a frustrating 3 hour long process (granted ~1h was waiting for the 441MB file to download).
so I found this thread searching through the fascinate forums and i gotta say, it saved my ass. I used heimdall 1.3.1 and it wasn't working right for the flash. IDK why but when I tried 1.1.1 it worked first try to flash back to stock after brick. I used the eh03_full_odin.zip file in heimdall and it quick and easy to get back to stock =] this forum rox!!
This guide is provided for information only. I will not be held responsible if you cause any damage, software or hardware, to your phone by following the guide. You are choosing to follow this guide, and as such, you choose to accept any responsibility for any mishap that may occur.
WARNING: Do not follow this guide if you think (or even suspect) that your USB port may be faulty in any way (ie, slow charging, loose connection among other faults). If your USB port is faulty, it must be fixed before flashing, or you are in danger of hard-bricking your phone. If the connection to the computer fails even for a moment, at best the flash will fail, and at worst the phone will need a new motherboard. Either send it to a service centre, or here is a good place to start if you want to DIY.
WARNING #2: If at all possible, make sure you have a backup of your efs folder (using Hellcat's app, "kTool" from playstore). Efs is the folder which contains your imei. No imei =no signal. Flashing a ROM may corrupt the efs folder, in which case the backup will be invaluable. If you do not have a working backup of your efs folder, I am not responsible if you choose to follow this guide and your efs becomes corrupt.
Symptoms
This guide is for people who find themselves in the situation where:
The phone currently will not boot.
The phone can only enter download mode (If it can’t do that, see the section below.)
If, for whatever reason, an Odin flash fails.
It assumes you know the basics of Odin flashing. If not, see here.
No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Send their phone to a service centre. That costs money (& you’re without a phone for a week or so).
Read on and hopefully you will be able to recover your phone without spending anything.
What to do
Keep flashing via Odin. You don't really have a choice. As for the files to flash: It’s worth trying to flash a range of stock ROM’s and custom kernels. I recommend downloading a stock firmware from Samfirmware for your device; either ICS 4.0.3 or JB 4.1.2. Stay away from 4.0.4 (research emmc brickbug if you’re interested.) See here for the stock ROM’s. Alternatively you can also download firmwares from xda. Make sure you’re using the correct firmware for your device variant and region (i9100, i9100g, i9100p etc).
As for custom kernels: If you manage to flash a custom kernel onto your phone, that gives you recovery (usually CWM for i9100), from which you can either restore a nandroid backup, or flash a custom ROM. ONLY for i9100: See here for Siyah kernel. If you were previously on ICS, flash ‘siyahkernel s2-v5.01’ from that link. If you were previously on JB stock, flash the ‘S2-v6.0beta5’. You want the .tar extension in both cases. If you were on a 4.2.2 or 4.3/4.3.1 ROM, see here. You want the file called "Kernel_Dorimanx-V9.43-[12-16]-[24-10]-TAR-FOR-ODIN.tar". None of the other files downloadable from that mirror are Odin-flashable. All files linked are for international I9100. Even still:
Your best bet is to continue to attempt to flash Stock ROMs for your model variant and region.
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: (Android File Host link) or here: Mega link. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Now that you have chosen a file to flash, continue on.
If Odin won't recognise the phone ...if it does, continue to 'Preliminary Steps'
Firstly, keep trying. Many users will find that Odin will recognise the phone in download mode eventually, but this will take perseverance. Note that if you do get Odin to recognise your phone in download mode, attempt to flash a stock ROM then. Don't unplug it thinking 'you'll try again later'.
Things to try if the phone isn't recognised by Odin:
Open Odin without the phone plugged in. Enter Download mode without the phone plugged in. Now, plug the phone in and wait a few seconds.
Didn't work? Try again in a different USB port. Still didn't work? Try all the USB ports, and then a different computer. If that doesn't work:
Uninstall the USB drivers using Revo Uninstaller. This program can remove the registry edits from the drivers, giving you a completely clean install of the drivers. Reinstall the USB drivers: Latest version here, or a "tried 'n true version here". Both are worth trying. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file to the Samsung USB drivers.
If you're still not having any luck, then follow these steps: (Credits to 4-2ndtwin)
1. Turn off both the computer and phone. Fully shut down.
2. Disconnect phone from computer: the USB cable from both the computer and phone.
3. Boot up the computer. Log in and let it settle.
4. Start up Odin and let it settle.
5. Put phone in download mode.
6. Connect phone to a USB port.
If that doesn't work, keep repeating those steps, with different USB ports on your PC/laptop. Change the USB cable you're using, multiple times (preferably use the cable that came with the phone). If all that doesn't work, start again at 'If Odin won't recognise the phone' on a different computer. Keep persevering
Now assuming you can get your phone into download mode, and is recognised by Odin:
Preliminary steps
Odin failing a flash usually isn’t a failure of the software itself. It’s usually to do with the way the flash is set up. Before we get on to the troubleshooting steps: you must always- i.e. every flash:
Run Odin as an administrator in Windows (only for Windows 7. This doesn’t apply for Windows XP). Yes, Odin is Windows only. If you use Linux/a Mac, you’ll need to use someone else’s Windows computer.
Ensure Kies is installed on your computer but you must kill all Kies running services in the Windows task manager. Most people have 4 running continuously. I personally only have 2, so don’t stress if you can’t find 4 to kill.
Make sure you're not using a USB hub of any description.
Remove your phone case, if you're using one. I've seen cases which make it not possible for the cable to correctly sit in the USB port.
If you haven’t done those steps on your previous Odin flash, it’s worth flashing again making sure you do those three things. Still didn’t work?
Troubleshooting steps
Things to do:
Change the USB cable you’re using. Preferably, use the original cable that came with the phone. If you’re already using the original cable, change to another, genuine, S2 cable. Try at least 3 different cables.
Remove your phone case, if you're using one. I've seen cases which make it not possible for the cable to correctly sit in the USB port.
Try different USB ports on your computer. You have to be using a mainboard (powered) port. Try as many of those as you have on your computer.
Use different versions of Odin: Attached at the bottom of this post is a zip file containing versions 1.3, 1.83, 1.85, 3.04 3.06, and 3.07. Try them all, but particularly 1.3, 1.85, 3.04 and 3.07. Make sure to extract the Odin files before using them.
Reinstall the Samsung USB drivers. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file.
Turn off all antivirus/antimalware/antispyware/firewalls. I advise downloading all files you need before doing this step so you’re not without antivirus whilst downloading files. I’m not responsible if you do manage to get a computer virus during this time.
Check the rom/kernel you download, making sure it’s not a corrupted file. The best way to do this is to check the MD5 sum using md5summer. If you don’t have the MD5 sum, then you can use WinRar, 7Zip, or IZarc to test the file. If any tests (MD5 or the 7Zip test) fail, then you need to re-download the file. Test the new file before using it.
Run Windows update on the computer you’re using.
What now?
Ok, so if you’ve got to the bottom of the list, but you’re still having failed flashes:
Use a different computer. Now, run through the list again. Yes, the whole list. Try everything all over again on the new computer. Didn’t work? Try again on one more computer. Keep persevering, the feeling you’ll get when your S2 is back to life will be worth it
Last Resort
What if… Ok, so you genuinely can’t get anything to work. This really is a last resort. It’ll be either up to you to choose whether:
You research the flashing of .pit files. If you are going down that route and have an I9100, two good places to start are here and here.Note that your phone will be stuffed if it fails. Full stop. Motherboard replacement. Ask yourself “if Odin won’t flash a ROM without failing, why will it flash a .pit successfully?” Only click that link if you have tried the steps over and over and over again as stated.
You take your phone to a service centre.
Many thanks to keithross39 for proofreading & editing this guide, and re-hosting the 3-part firmware.
Also many thanks for It_ler for providing and hosting the 3-part firmware, after it was lost during the shutdown of hosting site hotfile.com.
Credits:
MistahBungle, on whose posts these troubleshooting steps are based.
keithross39, for his guide on replacing the USB port.
Intratech, for his guides on the basics of Odin flashing & stock ROM collection.
4-2ndtwin, for his troubleshooting steps if Odin won't recognise the phone.
SamHaLeKe, for the updated Samsung USB drivers.
ApriliaM3, for the USB driver hosting.
daerragh, for the Windows 8 drivers.
king_below_my_lord, for his guide on I9100 .pit file flashing.
metalgearhathaway, for his thread containing .pit files
Nice hopper, let's make this a sticky
Sent from the little guy
This is going to be VERY useful.....
I agree, it needs to be stickyed....
I can see myself referring a lot of folks to this thread.....
Excellent work mate......
Edit.....mods, get the glue out please.....lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
keithross39 said:
I agree, it needs to be stickyed....
Edit.....mods, get the glue out please.....lol
Click to expand...
Click to collapse
I've PM'd a mod, so hopefully it can be stickyed
I thought thanks/credit is supposed to be given to the originators of the info.
Maybe a mod could look into that as I dont see any of that here.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
theunderling said:
I thought thanks/credit is supposed to be given to the originators of the info.
Maybe a mod could look into that as I dont see any of that here.
Click to expand...
Click to collapse
All of the information in this guide is freely available on the internet, a lot of it XDA. If you are referring to the steps MistahBungle wrote, he has specifically stated there is no need to credit him for those steps as the info is freely available on the internet. If it makes you feel better, I can credit him anyway. I used over 20 XDA threads as well as info from outside XDA to write this guide. Would you like me to credit every single one of them?
Edit: Have credited MistahBungle in OP. I hope that puts your mind at rest.
It wasnt only mistahbungle I was thinking of,eg the 1st link is from Intratech.
I am not the one making up guides so I dont need to know what the correct protocol is regarging credits,this is up to a mod to decide.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
OP edited, new section with troubleshooting steps if Odin won't recognise the phone. Also, many many credits are added, for all linked files/guides.
Good job Hopper, everyday I find that many people here are doing a great job of answering people in trouble, the best are Gastonw(watch out this guy answers anything) , Mistahbungle, Keith, The Underling, you, I hope these guy's will be around for some more time(before the device becomes obsolete) I find myself quite unnecessary, as all the above mentioned guys are tackling all possible problems with great success. I am happy to be a part of such a great forum.
Sent from my GT-I9100 using xda app-developers app
But custom, I don't do custom.
Sent from the little guy
OP updated with a warning not to flash anything if USB port is faulty in any way. Thanks to Keithross39 for the suggestion to add this.
Sponsor it with a "don't flash without backing up EFS" banner
Sent from the little guy
gastonw said:
Sponsor it with a "don't flash without backing up EFS" banner
Sent from the little guy
Click to expand...
Click to collapse
I'm not sure many people following this are in a position to back up efs? I've started at the point that they can only enter download mode.
You'd be surprised....
Sent from...this is not even my S2
gastonw said:
You'd be surprised....
Sent from...this is not even my S2
Click to expand...
Click to collapse
OP updated. Thanks for the suggestion
Whow whow, that was a joke.
The whole banner thing...damn, the meme thread &%#@*+ me up.
Edit: nevermind, fitted nicely
Sent from the little guy
This is rapidly turning into one helluva guide......
Pretty soon, everyone's going to be able to find out everything about their phone.....right here.... lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
The DeLorean is coming too.
Sent from the little guy
keithross39 said:
This is rapidly turning into one helluva guide......
Pretty soon, everyone's going to be able to find out everything about their phone.....right here.... lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Just hoping it can still be stickyed...
Sent from my GT-P7510 using Tapatalk 4 Beta
It will.
Sent from...this is not even my S2
Model# SM-N900T
Android Version# 4.4.2
Baseband# N900TUVUENK3
Kernel# 3.4.0-2587359
Build# K0T49H.N900TUVUENK3
Security Software# MDF v1.0 Release 3
I'm kinda new to this whole XDA developers website (don’t let when I joined fool you) I’ve always heard that the XDA community are very helpful and I am in need of some serious help. I've had my Samsung Galaxy Note 3 for quite some time now, but now it has started to crash and slow down I was wondering if rooting it might fix this problem.
If so then how and where do I even begin? Do I even need to root it?
Also if and when I root I want to get rid of all of the bloat ware apps how do I do this?
Please someone teach me I’m willing to learn, so be detailed and dumb it down as much as possible.
I want to say thank ahead of time to anyone that responds! :highfive:
First off, rooting is nothing to be scared off. As long as you have a little bit of knowledge and some common sense it's pretty straight forward.
To root you just need a couple of things, and this will trip knox too if I remember rightly, but if your phone is out of warranty then it doesn't really matter to much.
Firstly you will want odin - this will put the files onto the phone using a PC and USB cable.
Secondly you'll need the .tar file that contains the "root" files. I used CF-Auto-Root by Chain fire.
Head to http://autoroot.chainfire.eu and find the right file for your phone model.
This also contains Odin too.
So unzip the CF-Auto-Root zip file on your PC, and you'll find odin.exe and the CF-Auto-Root.tar.md5 files along with a couple of dll files and an ini file.
Open the odin.exe and you'll have a screen pop up which may look pretty daunting but fear not, it's not bad, it's actually really easy and you'll love it.
Now turn off your phone and once it's completely powered off, hold volume down button, the home button together and then hold the power button. The phone will boot into download mode... You'll see a screen saying to press volume up to continue or cancel by pressing volume down. You'll need to continue so hit volume UP.
Now plug the phone into the PC and wait a few minutes while the drivers are installed. You will notice on the odin program that at the top, a bar has lit up saying "comxxx" (where xxx is will be a number. This is the com port your phone is connected to)
Now comes the bit you need to get right....
Click the PDA or AP button (depending on version of odin) on the right side of odin and then select the CF-Auto-Root.tar.md5 file. It will load it into odin ready to flash across to the phone.... Make sure auto reboot and f reset time are the only boxes checked on the left side.
Now comes the really difficult bit, you need to pay attention here...
Click the "START" button.
Thats pretty much it. The phone will reboot and once it's rebooted, go into your apps and see if supersu is there. If it is just open it up and update the binaries if it asks you to.
Congratulations, your phone is now rooted.
I recommend using a custom recovery like philz or TWRP and make nandroid backups before you do anything else, so if something goes wrong you can always go back and restore.
You can also flash custom roms which may help your phone go fast again. I recommend audax roms or echoe roms.
OMG!! Thank you!!! so simple!!!!! Just a few more questions before I start.
1. What is a "custom recovery" and how do I use it?
2. What are "Custom Roms" for and how do I flash them?
3. What is supersu for? (I've been reading that everywhere)[/B]
4. Do you recommend buying titanium backup?
EstradaKing said:
OMG!! Thank you!!! so simple!!!!! Just a few more questions before I start.
1. What is a "custom recovery" and how do I use it?
2. What are "Custom Roms" for and how do I flash them?
3. What is supersu for? (I've been reading that everywhere)[/B]
4. Do you recommend buying titanium backup?
Click to expand...
Click to collapse
1. Custom Recovery is a recovery where you can a lot of stuffs which are not supported in stock recovery. Like flashing a zip package to be able to install it, be it a ROM or a small mod or whatever. Then you can take Nandroid backups too from it, along with so many other options.
2. Custom ROMs, same. ROMs which have a lot of customisation ability unlike stock ROMs, some custom ROMs come with some more pre bundled.
3. SuperSU is an app which is a must for rooted devices. It gives administrative level permission to apps, without it you won't be able to run some apps which needs root access. It can be found on Play Store, but better way to install it from a custom recovery after downloading the latest zip package of SuperSU.
4. Yes, very much, that is one of those apps which is a must have for Android.
Also one thing about XDA, when you are thanking someone, just use the Thanks button. I could not care less about it but believe me a lot of people prefer that.