Constant Fail from ODIN. *Have Searched* - Galaxy S6 Q&A, Help & Troubleshooting

Hi,
Pretty much tried everything (I think) to reconcile this.
Tried to install Kingroot.
Bricked G920F that was on 5.1.1
Can get to Download Mode. But ODIN keeps failing at the last 'Write' bit on the script.
No idea where i am going wrong. Have searched but most threads offer solutions I have already tried.,
All advice welcome.
Thanks!
Tony

myotai said:
Hi,
Pretty much tried everything (I think) to reconcile this.
Tried to install Kingroot.
Bricked G920F that was on 5.1.1
Can get to Download Mode. But ODIN keeps failing at the last 'Write' bit on the script.
No idea where i am going wrong. Have searched but most threads offer solutions I have already tried.,
All advice welcome.
Thanks!
Tony
Click to expand...
Click to collapse
I have had this before. It is usually the "hidden" image part of the flashing process. Extract the rom zip and rename the "hiden.img" to "hidden.img.tar. Then flash this using odin.

You can also uncheck auto reboot and re-partition. Try it then

Just plug the phone to PC in download mode and rescue it via Smart Switch. It'll download the right firmware for your device and flash it automatically.
Here's how you can do it;

Related

samsung showcase HELP!!!

I apologize in advance, since I know people have asked questions similar to this already. But I am desperate for help, as I have been trying to fix my phone for 3 days now, and have not gotten anywhere!!! so here is my story/problem.
I was trying to do an update on my samsung showcase (cspire) using kies, and during the download it was interrupted somehow. The phone was bricked. (i think) so then I found something called one-click unbrick. after that i'm able to put the phone in download or recovery mode.
So i have been trying to get factory rom back on my phone. I downloaded odin3 v1.70 and v1.82 (i have tried both of these) and i have downloaded atlas 2.2 for pit and I have tried both EH09_modem_CS.TAR.MD5 and EI20.tar.md5\EI20.tar.md5. Everytime I do this odin freezes on factoryyfs.rfs.... I have tried all the tricks I can find, different usb port, diff cable, running as admin, i even download sandboxie ( someone suggested that)... I dont know if i am doing something wrong, or if it is odin... Also, i'm not rly sure about the software i'm using... I have very little experience with this kind of stuff, but i am really determined to fix this! please forgive my ignorance! TIA!!
Try flashing a custom rom and boot.img first then Odin back to stock
AshtonTS said:
Try flashing a custom rom and boot.img first then Odin back to stock
Click to expand...
Click to collapse
I've been trying to find one, you don't happen to have a link to where I can find one do you?? Also can i do this using odin, the same way I have been trying to get the stock on there?? Thanks for you help!!

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

SOFT BRICK Galaxy S6 (SM-G920I)

this is the second time i've soft bricked my phone in the past 6 days and if this is fixable i will probably consider researching for weeks at a time before trying anything new..
anyway, the first time i soft bricked my phone last week, my s6 was rooted (via chainfire, G920IDVU1AOC6) but i decided to unroot so i could update software. after unrooting with SuperSU, i attempted to update by using smart switch and then something went wrong with that process (my firmware was at G920IDVU1AOC4) which i then fixed by flashing G920IDVU1BOE3 (latest stock firmware) WITHOUT the hidden.img
backstory out of the way, i wanted to flash TWRP so i could install xposed installer. i used the same chainfire firmware that worked the week prior (above) and so now my phone is soft bricked
things i've tried:
- flashing recovery of AOC4 - i can get back into recovery mode with the older firmware
- flashing AOC4 stock firmware with AND without the hidden.img
- flashing the BOE3 stock firmware with AND without the hidden.img
i'm still able to get into download mode and stock recovery and i've already tried wiping cache and factory reset but nothing works.
i continue to get FAILED on odin
if anyone is able to bring my phone back from purgatory for the second time it would be greatly appreciated.
thanks in advanced, mojo.
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
thank you so much for your reply and reassurance! i'll try this out right now and update on the results
UPDATE: i tried flashing stock and then the my-recovery.img.tar and i could get into recovery but i was stuck in boot loop.
is there something i'm doing that's incorrect?
Saafir said:
Did you remove the cable, boot download mode, then reconnect and let the driver install screen complete on your PC? Sorry if its a bit redundant but I had made this mistake before.
Click to expand...
Click to collapse
yes i have reconnected each time but thanks anyway!
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
I FIXED IT.
i'm not exactly sure of the steps i took, as i had to keep waiting for my Unified Android Toolkit to create the tars but essentially what i did was i flashed;
- stock BOE3 WITHOUT hidden.img
- TWRP recovery (was able to boot into twrp and when i looked through some settings (reboot) it said i had no OS installed for some reason
- from this info i tried flashing the AOC4 older firmware WITHOUT hidden.img then it worked.
do you think it is worth attempting the smart switch thing mentioned in that link you posted?
i wouldn't want to run into this problem again..
my lord.. so SOMEHOW i managed to get myself into this for THE THIRD TIME..
once i got it fixed, just a few hours ago, everything was fine and i was then able to flash CF root again.
but once i tried to install TWRP (it worked before i fixed the second time) odin FAILED again and i'm back to square one.
i'm unsure how to properly fix it and the steps i took before aren't working now and i can't even flash any recoveries (whether its AOC4, BOE3 or TWRP)
can anyone suggest anything else please?? i'm in panic mode again lol
this is definitely the last time i try to do any type of configuration with this device.
Do you have recovery now? Maybe burn some custom rom? ..
JusTeN_ said:
Do you have recovery now? Maybe burn some custom rom? ..
Click to expand...
Click to collapse
now i can't flash the twrp .. it won't work. this suck so much!
UPDATE (final update, hopefully ): fixed it AGAIN.
after going through this hellish nightmare for the 3rd time and reading countless threads, i've discovered that the FAILs on odin may be occurring due to the corruption of the firmware file.
so if anyone goes through my problem, CREATE A COPY of the desired firmware before flashing with odin!
thanks justen for your patience and attempts to help me!

Bricked S8+..... i think cant access recovery

hey everyone, im new here, just got a Samsung s8+ last week. had it rooted and all working well until today, had problems so i went to reflash twrp and when was unticking auto reboot in odin i accidentally ticked "nand erase"..... and i didnt notice until it was too late.
Now i cant get into recovery mode, i can get to the download mode but it wont flash the twrp at all it keeps failing. all i get is a black screen with samsung logo when i try to start it up. i am downloading factory firmware as i write this and going to see if that'll flash. any help will be appreciated.
thanks in advance, hope this is the right place to post it.
Hey
If you can get to download mode,you just install the original firmware from smartswitch,I think you have that option to recover from that program,and install the original firmware.
Or just do it in Odin and find the firmware on SamM.
Lots of work for you,but thats the only thing I can come up with.
Then you have to root it again and everything with it.
PapaD78 said:
Hey
If you can get to download mode,you just install the original firmware from smartswitch,I think you have that option to recover from that program,and install the original firmware.
Or just do it in Odin and find the firmware on SamM.
Lots of work for you,but thats the only thing I can come up with.
Then you have to root it again and everything with it.
Click to expand...
Click to collapse
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
How is it failing? Are you getting an error? Is Odin detecting your device?
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
No worry
You just have to install Microsoft visual c++ 2008 x86,after you have done that,no more errors in smartswitch.
Try that,and let us know
Long time since I used Odin now,but try the first thing first
anonuser111 said:
Thanks for your help, i downloaded the following https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022 they all seem to fail when i try to flash them, do i have to do something different to what you would do flashing twrp? any options need to be selected? any particular order? Also the samsung switch software wont install on wither my ma or pc (win 10) " THIS APPLICATION HAS FAILED TO START BECAUSE ITS SIDE-BY-SIDE CONFIG IS INCORRECT"[/]
thanks again sorry for my newbness lol
Click to expand...
Click to collapse
Morning Mate,
Smart Switch (and KIES on Win 10) requires some old stuff to work. Install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) from https://www.microsoft.com/en-us/download/details.aspx?id=5582 My advice however would be to try and flash your carriers stock firmware with ODIN or if you want an easier way you can use KIES by doing the following -
- Install C++ 2008 SP1 from link above to get it to work on Windows 10
- Install KIES www.samsung.com/au/support/usefulsoftware/KIES/ - I'm in Australia so that's my closest but you can still get it from there no worries.
- Also select install 'unified driver' during install if you have not already installed Samsung USB drivers to your PC
- Fire up KIES and from the top menu select 'Tools' and from the drop down menu select 'Firmware Upgrade and Initialisation'
- Enter in your model number - for me it's SM-G955F (make sure model is all in CAPS or it will not work). Now it will present you with a S/N dialog box. This is the tricky part if your phone is bricked. Chances are you have not written down your serial number. You can get your serial number from the back of your phone towards the bottom in really small print, or you can get it from the box it came in from purchase if you happened to have kept that.
- Enter in the serial number and follow the instructions, it's easy as. This will install your stock firmware and you can start again. Provided there is no damage to the phone this method will always get you out of the proverbial as a last resort and it's faster than downloading firmware from updato.com or other places.
The fastest way is by using the SamFirm tool to download but it takes some knowledge and I have lost the link to where I got it (the link at XDA is dead now and refers you to updato.com). The method with KIES above will always work, is fairly fast and pretty easy for the newbies or experienced alike.
Hope this helps, let me know if you need any more assistance :good:
Thanks heaps mate, im also in australia too. have installed all the software and is updating and installing as i write this, all seems to be going well so far, thank you so much your a life saver i was starting to worry as wtf i could do with this brick haha i will keep you posted and let you know if i have nay problems. Thanks to everyone else for their help and contribution this forum is awesome. What would you recommend in regards to rooting the phone again use the twrp recovery and magisk-v14.0 root?
thanks again
I was just about to write a post about how it wouldnt work.... twice in a row it kept failing when it went to install and initialize... 3rd time lucky it ****ing worked! i have a stock phone now all working sweet. Thanks so much to everyone you guys are literally lifesavers!
LEGENDS! Happiest man alive right now.

S8 bootloop, ODIN fails at write, finally asking for help

So the past couple days I've been learning what I can about rooting. Finally decided to give it a shot and well I can't seem to get ODIN to work correctly. It seems to always end with abl.elf and then failing at write. I've tried Comsy and a few versions of ODIN including the latest version.
I'm currently downloading the latest firmware for my phone which is what I was updated to.
I have the Galaxy s8+ SM-G955U originally through VZW. I remember the ending of my firmware was CRE9 so I found this version off of Samsclub: G955USQU4CRE9_G955UOYN4CRE9. I downloaded some stock files for my device because I wanted to reset my bootloader version so I could root and use PARTCYBORG's rom. That's when it seemed to start looping.
I have access to download and recovery if you need that information. I also have downloaded the latest samsung drivers for Odin. I'm pretty sure if I could get it to write I could fix this issue but I've gone through a hundred threads on this forum and I'm pretty much a bit overwhelmed now. Please help
EDIT: I think I've nearly gotten it, but I'm stuck now. Odin 3.12 and Comsy 3.12 seemed to get me close. I've ran into missing Home Binary and Fail! Model Mismatch. Trying a 3.13 version of ODIN and then calling it.
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
JeffDC said:
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
Click to expand...
Click to collapse
hi I installed the image twrp 3.2.2.0 but by mistake on boot. how can I restore the boot? thank you

Categories

Resources