Related
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.
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.
I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!
Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...
irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.
shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.
hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?
Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)
I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.
I also forgot to mention you can't get ahold of the system.img because it's not released to the public.
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.
Hello everyone actually I have a G360T1 with the latest system update (G360T1UVU1AGP2) and I want to customize my phone, root it and/or install a custom ROM but it's my first time messing around with a Samsung phone and I need some help because I don't want to do something wrong with my phone
BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!
syran123 said:
BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!
Click to expand...
Click to collapse
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?
Auraburst said:
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?
Click to expand...
Click to collapse
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly
syran123 said:
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly
Click to expand...
Click to collapse
Well, now I understand a little more, just a few questions, which custom recovery should I use? I've read about TWRP is available for this phone, also, what should i avoid to install or do with the stock ROM and don't brick my phone? As I said, it's my first time messing around with a Samsung phone and it's my main and only phone atm
As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.
I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.
syran123 said:
As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.
Click to expand...
Click to collapse
syran123 said:
I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.
Click to expand...
Click to collapse
I did it without problems, thanks a lot! :victory:
Something i've noticed after i rooted my phone: Sometimes the system freezes randomly, but is only a issue that happens a few hours after i've rooted, now works as usual
Check out this thread. It has everything you need for this device
http://forum.xda-developers.com/gal...des-faq-one-stop-shop-metropcs-t3266173/page1
I can confirm almost all of these working perfectly as I have this device and it is my daily driver
Hope this helps
Hello,
I tried to root this model using Odin, and now the only thing I can do is get in to the Downloading mode. If I escape that I have 4 options; Normal Boot, Factory Reset, Safe Mode and Turn Off. only the Turn Off has success, I can not boot, can't hard reset etc. The phone shows something to the effect of an update and tiny little lines of code that run, then it reboots and does this over and over and over and . . .
The first choice only gets me to a Samsung Galaxy S8 power by Android Splash screen, it stays there perpetually stuck or also reboots in it.
Factory Reset runs the lines I mentioned and this goes on cycling and never completes. (Erasing - failed to .....)
Safe Mode looks about the same but says something about installing updates and cycles.
I'm at a loss to find a FW to get this fixed, (tried to find the latest) I've read so many posts and tried so many differing FW, and all I get are "Failed! auth" "sw rev check fail [abl]fused 2 binary 1" and type error codes.
Can anyone with a little compassion and patience please give me some clear straight forward advice before I have to take this back to BB and spend $$ on swapping it? Please be specific, supply a url to a FW, m a y b e something I haven't done or found in the past 24 hours and 189 tabs I've opened?
Thanks in advance!
Don't think you can use Odin to root on snapdragon models
Let's revisit that once I get this recovered. I has no phone
On the HTC I had I was able to put many ROMs on it, never used Odin.
Anyone?
If you can get into download mode you can flash a stock or rooted ROM. Look for threads on flashing stock ROM. There are a few.
No offense but I just spent a day poking around here before asking for some very specific help. I don't know how to be more clear, I've tried things on these threads over and over.
I can't get in to recovery mode, I can't use ADB commands . . . I'm at wits end.
Telling someone to just go search through endless threads for key words isn't much help, and I've done that for about 24 hours now.
you are trying to flash a firmware with a v1 bootloader, your phone has a v2 bootloader..
try flashing this: G950U1UES2AQL1
https://updato.com/firmware-archive-select-model?record=7990E6F5EC0F11E7A5F9FA163EE8F90B
Thx, downloading now.
I tried using > SM-G950U1_1_20170817082313_6u8ae5j9jh_fac
It contains:
BL_G950U1UEU1AQH3_CL11979009_QB14538295_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_G950U1UEU1AQH3_CL11979009_QB14538295_REV00_user_low_ship_MULTI_CERT_meta.tar.md5
CP_G950U1UEU1AQH3_CP7166652_CL11979009_QB14538295_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OYM_G950U1OYM1AQH3_CL11979009_QB14538295_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OYM_G950U1OYM1AQH3_CL11979009_QB14538295_REV00_user_low_ship_MULTI_CERT.tar.md5
Like the other ones, I get a "Fail! auth" message.
QH3 is bootloader v1. Like i tokd you QL1 has a bootloader v2, and try to flash using a usb2 some people had reported trouble using a usb3 port
Righto - DL still needs another 2 hours, not breaking any speed records. Indeed I am using a USB port. Until the phone was officially buggered, both Odin and Adb worked fine on this port - cable.
Is there a place where people can see or ascertain the nomenclature for how the FW is labelled? You have some instructions on that?
Cheers
Needs Help said:
Righto - DL still needs another 2 hours, not breaking any speed records. Indeed I am using a USB port. Until the phone was officially buggered, both Odin and Adb worked fine on this port - cable.
Is there a place where people can see or ascertain the nomenclature for how the FW is labelled? You have some instructions on that?
Cheers
Click to expand...
Click to collapse
It's a little bit old but I hope it helps
https://www.androidpit.com/how-to-make-sense-of-your-samsung-firmware-number
https://forum.xda-developers.com/showthread.php?t=1356325
I had to go get a burger and get liquored up a bit When I came home the QL1 had completed and I added to Odin and ran it completely - successfully!
I'm back in the saddle again. Now to restore apps and test etc.
And thx for the links btw. I'll start a new thread on wanting to use Wi-Fi calling and get a rooted device if possible.
Cheers
Glad you got it working again, if you want to root..
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
That is the best option ti do it..
I was able to do this using the Previous Version set. It works, but the boot is some horrendous lines of code with lots of rd and the word fail in it. This build gives me the otion for Advanced Calling > Activate Wi-Fi Calling etc.
G950USQU2BQK5
Bootloader Version 2
AP_PartCyborgRom-G950USQU2BQK5_Part1.zip
BL_PartCyborgRom-G950USQU2BQK5_Part2.zip: