Hi everyone, I hope that you can help me. My phone was rooted for quite a long time but since it was rooted it wouldn't allow me to access my banking app or PayPal or other apps that I needed to, so around a week ago I decided to unroot it with a simple unroot button in the SuperSU.
However this did not end well and when my phone was rebooting it got stuck in the boot loop and it would not load again, I tried wiping the cache which didn't help. I then wiped the phone completely and that did not help with anything.
So then I read about it and I decided to try using Odin to flash the phone with the stock firmware, and whichever firmware I used the Odin would fail and give me a "Nand write start fail". I tried for hours and day and could not get this to work.
So then I decided I would try contacting Samsung and see if they could fix it for me, they took the phone but today I got an email saying that the can't repair it because the KNOX was tripped and the warranty is voided.
So right now I don't really know what to do, do I buy a new phone?
You can do JTAG maybe
darkliesbehind said:
Hi everyone, I hope that you can help me. My phone was rooted for quite a long time but since it was rooted it wouldn't allow me to access my banking app or PayPal or other apps that I needed to, so around a week ago I decided to unroot it with a simple unroot button in the SuperSU.
However this did not end well and when my phone was rebooting it got stuck in the boot loop and it would not load again, I tried wiping the cache which didn't help. I then wiped the phone completely and that did not help with anything.
So then I read about it and I decided to try using Odin to flash the phone with the stock firmware, and whichever firmware I used the Odin would fail and give me a "Nand write start fail". I tried for hours and day and could not get this to work.
So then I decided I would try contacting Samsung and see if they could fix it for me, they took the phone but today I got an email saying that the can't repair it because the KNOX was tripped and the warranty is voided.
So right now I don't really know what to do, do I buy a new phone?
Click to expand...
Click to collapse
Tried flashing bootloader and stock recovery? Smart Switch emergency initialization?
And a bit more details would help, like model, CSC, Android version, can you enter recovery, is it stock or custom, is there any DRK error in recovery, which firmware you tried to flash, which kernel you used for rooting, whatever you think it could be useful.
brenner650 said:
Tried flashing bootloader and stock recovery? Smart Switch emergency initialization?
And a bit more details would help, like model, CSC, Android version, can you enter recovery, is it stock or custom, is there any DRK error in recovery, which firmware you tried to flash, which kernel you used for rooting, whatever you think it could be useful.
Click to expand...
Click to collapse
I will provide more details when I receive the phone back from samsung. But from what I can remember. I am able to go into recovery mode, it was running stock ROM, I tried to flash both Vodafone firmware which is what I bought the phone with and I also tried UK base firmware. its the SM - G920F model. It was running the newest android, I don't remember what version it was but the update wasn't too long ago .
with Smart Switch emergency initialization, you can make that your phone works, it's long but it works. i do it.
look at (it's in french but you can do it)
https://www.youtube.com/watch?v=mi7O0OvnS2E
Okay, so I've tried using the Smart Switch initialization and this did not work, it says that my device was not supported for initialization.
darkliesbehind said:
Okay, so I've tried using the Smart Switch initialization and this did not work, it says that my device was not supported for initialization.
Click to expand...
Click to collapse
what model are you using?...download the latest MM rom with the PIT file ....flash the PIT file with odin to repartition the phone and flash the stock rom....it should work
Related
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
inolil said:
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
Click to expand...
Click to collapse
Have you tried to Odin back to stock?
http://forum.xda-developers.com/verizon-galaxy-s6/development/5-15-stock-odin-tar-t3109676
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
brholt6 said:
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
Click to expand...
Click to collapse
Awesome thank you
I need help!
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Bubblegum Mage said:
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Click to expand...
Click to collapse
Keep in mind XDA is a community for developers by developers. People are also willing to help, but you got to put forth your own effort. You will get ignored if you think people on this site are going to act as free tech support. Your question is posted just a few posts down from a link to the process on using odin to return to stock. You need to just follow those instructions. If you don't understand a step then Google it. I'm saying this because I noticed you joined XDA to ask this question. Or at least it's your first post. You will make a lot of enemies here if you don't take the time to read and research things before posting.
HELP
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Bee Funny said:
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Click to expand...
Click to collapse
If you have an edge you should use their forum. It's different than the GS6.
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Oooah said:
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Click to expand...
Click to collapse
Same exact crap just happened to me. I was running CleanRom Lite....thought I could use TWRP...some times I do stupid things...should have just stuck with FlashFire.
I've tried odin back to stock, it keeps failing. it says nand write fail and it stops. I've tried many different times. I've run Odin 3.10.6 and 3.10.7 I have the latest drivers, it recognizes the device but it will not load anything via odin. I've tried on two different computers as well.
...
Gizmoe said:
...
Click to expand...
Click to collapse
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
keith7120 said:
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
Click to expand...
Click to collapse
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
---------- Post added at 06:50 PM ---------- Previous post was at 06:44 PM ----------
Fe Mike said:
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
Click to expand...
Click to collapse
Sorry I saw you tried other odin versions 3. 10.x, I meant going lower. 3.09 is recommended for jb/kk but that worked for me.
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!
Flashed the Moar rom and all was working fine until I turned off the OEM Unlocked and then rebooted the next day.
Now I all I can get is the download mode. Tried flashing the rom, TWRP, Stock tar rom with Odin. And get nothing but failed. Called Sammy customer support and all they would say is they don't support custom roms. I am downloading Kies 3 to see that will work. So whatever you do, don't turn off the OEM Unlock or you are screwed.
Unless someone can help it looks like I will have pay full price for a new phone.
See post #3
Already answered. Flash back to the stock firmware with odin and you can oemunlock again.
Resolved Custom Binary(Boot) Blocked FRP Lock
After much research and finding nothing for the Note5. I did find a post related to the T-Mobile SG6 that several were able to fix this problem by flashing the Srock tar... My problem was I found a link to the previous OGD tar. Flashing this failed because I was on 016, not OGD. Once I downloaded and flashed using Odin 3.06... I lost root and TWRP recovery. Then I flashed TWRP using Odin and then using recovery I was able to restore a previous saved rooted rom. So my phone is back to normal.
WARNING! do not turn off OEM Unlock or USB Debugging or might run into the same problem. I did not know this options are tied to the custom recovery. I would like to kick the Samsung tech... in the a$$ for not just telling me this rather than saying there was nothing they could/would do. Even if I paid for the repair!
If this had not worked I was looking at 839.00 dollars for a new phone. This was the most serious brick I have ever run into...
Many thanks to Moar for an Awesome rom.
Easy for u , I have the same problem like u . After rooted and installed the super su , I restarted my note 5 . After that screen had been blocked by FRP lock , however I tried I can go to recovery mode so I used with Odin to install the new firmware but FRP lock still blocked the installation. So I'm thinking how to do , at last time I tried with Samsung Kies . Just simple go to Tools ... firmware upgrade and installation and will ask and fill for yr Phone type and S/N ( can find yr phone back ) and go to recovery mode yr phone and automatically download the firmware will install the new firmware.
winnainghein said:
Easy for u , I have the same problem like u . After rooted and installed the super su , I restarted my note 5 . After that screen had been blocked by FRP lock , however I tried I can go to recovery mode so I used with Odin to install the new firmware but FRP lock still blocked the installation. So I'm thinking how to do , at last time I tried with Samsung Kies . Just simple go to Tools ... firmware upgrade and installation and will ask and fill for yr Phone type and S/N ( can find yr phone back ) and go to recovery mode yr phone and automatically download the firmware will install the new firmware.
Click to expand...
Click to collapse
It's not installing new firmware that will work. But using Odin to install a stock ROM tar of the same version your phone was on at the time of the FRP. I hope u already found this out and back to working again. If a different method worked for u then please tell us it here so others may be able to resolve their FRP lock.
Thanks
Edit: What combo of buttons are using to get into the download mode. I used vol. down, home and power. Sometimes it wouldn't work, the phone would try a normal boot. Just try again.
Sent from my SM-N920P using Tapatalk
I've looked through the forums to identify a similar problem to mine in hopes I can resolve this issue but I've not found one. So here's my problem.
I have a UK Galaxy S7 running on the 6.0 firmware that came with the phone when it first released (Yes I know it's very old and should have updated along the way but I had plans to root and install customs at some point which obviously didn't happen). The phone is unrooted and the stock rom is the XEU version with Multi-CSC (according to recovery)
The phone was running fine until a few days ago when all of a sudden it shut off and wouldn't power on via the power button. So I pressed and held Home + Volume Down + Power. The green screen appeared and selected Volume Down to restart the device (as you do in odd situations like this).
PHONE IS NOW STUCK IN BOOTLOOP!!!
I have tried various means (not including flashing) to get the phone to boot to the home screen with no success. I have not performed a factory reset from recovery because I have various data, including pictures, music and other software on the internal storage which I wish to keep and not lose. The phone is still under warranty so I can take it to a Samsung repair outlet to get them to fix it for me but due to data privacy or whatever, they have to format it clean to then install the most recent firmware.
I've been scouring the forums for help on flashing OTA updates which retain data on phone whilst possibly allowing my phone to boot into the home screen so I can access my data. Is such a thing possible?
Any help would be greatly appreciated.
You can flash the latest firmware without losing data (as long as the hardware is not faulty) by downloading it from either sammobile, updato.com or using the samfirm tool here on XDA (Fastest option)
Then extract the firmware and add all 4 parts to ODIN 3.12.7 (Do not use ODIN 3.13.1 unless you want to flash BTU Oreo 8.0)
AP << (Takes quite a long time to add, be patient as ODIN will look frozen)
BL
CP
HOME_CSC
If you use CSC instead of HOME_CSC it will wipe the device after the flash, HOME_CSC will not wipe it
Put the phone into download mode (Home & Power & Volume Down)
Connect to PC USB and hit start on ODIN
Wait for the flash to complete (It can take quite a while) and the phone should hopefully boot back into Android
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Cassie` said:
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Click to expand...
Click to collapse
Almost, you must flash all 4 files at the same time, load them all into ODIN before hitting start, doesn't matter which order you load them in as long as they are all loaded before flashing
And you are correct with the rest, HOME_CSC will not wipe anything, and yes it will act as an upgrade although it is a full ROM you are flashing, to you the user, it will appear exactly the same as an upgrade as long as you use HOME_CSC
No other steps needed
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Cassie` said:
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Click to expand...
Click to collapse
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
*Detection* said:
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
Click to expand...
Click to collapse
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Cassie` said:
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Click to expand...
Click to collapse
Yea unfortunately all alternatives other than samfirm tool are slow, and samfirm only downloads the latest ROM
Judging by the bootloader version and the ROM version you have chosen, if this also fails, then I would assume a hardware failure
The only other thing I could suggest if this doesn't work, is to pick an older version of ODIN to flash the older firmware, ODIN 3.11.1 was used for MM 6.0.1 ROMs if I'm remembering correctly
https://forum.xda-developers.com/showthread.php?t=2711451
or
https://odindownloader.com/download/odin3-v3-11-1
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Cassie` said:
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Click to expand...
Click to collapse
Your ODIN screenshot looks like it managed to flash the bootloader before it failed, so it's possible you are going to need to use a version 2 ROM from now on, I have the same phone, XEU G930F and it is running Bootloader version 2 (Running the BTU Oreo 8.0 stock ROM)
But if the 7.0 Nougat ROM failed again it's looking more like a hardware issue, seems to be failing when it should be starting to flash SYSTEM (AP)
You can try flashing the 7.0 ROM section AP on it's own with ODIN 3.12.7, see if that fails immediately, if it does that's likely where the problem lies, it's not unheard of for these S7's to fail like this out of the blue, I see it maybe a couple of times a month on XDA
Only solution is to get the mainboard replaced
But yea, give 6.0.1 a shot anyway, worth a try saying as everything else has failed up to now
(Looking for mirrors for that 6.0.1 ROM, I've got it on my main machine but it is offline right now with no graphics card so I can't access any files, stuck with a laptop, I always download and save every new firmware release for this reason)
There is Samsung SmartSwitch software for Windows for the emergency firmware recovery, but it WILL wipe your phone back to factory and delete all your data (Last resort if nothing else works, although if ODIN doesn't work, I'd say hardware failure)
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Cassie` said:
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Click to expand...
Click to collapse
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
*Detection* said:
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
Click to expand...
Click to collapse
The charging issue occurred immediately when the phone shut off by itself and wouldn't power on conventionally. The phone is still under warranty so if the Samsung SmartSwitch software is unable to recover the phone then I will take it to the repair center and have them fix/replace it. If it's a case of undoing the glue and whatnot then I'd rather they give me a replacement.
I did change the USB cable to a different one, and I've attempted to flash the 2 different ODINS with the 2 different ROMS on a laptop as opposed to the desktop I was using. Still fails at the recovery.img part of ODIN.
I'm going to try Samsung SmartSwitch now and see if this will give it some life. If THAT doesn't work then it's 100% hardware issue and my data was lost to begin with.
Considering both versions of ODIN didn't work with either ROM, I don't think I'll be looking for the BTU version of OREO to attempt to install with. If there's a direct download that's quick I might but I think I'll attempt to Emergency Recover through the Samsung tool.
I want to thank you plenty for your help and knowledge on this. It certainly has been helpful and given me better understanding of the problem I'm facing and potential solutions. I have a feeling that the SmartSwitch recovery won't work either and still be posting back here hahaha.
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Cassie` said:
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Click to expand...
Click to collapse
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
*Detection* said:
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
Click to expand...
Click to collapse
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Cassie` said:
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Click to expand...
Click to collapse
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
*Detection* said:
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
Click to expand...
Click to collapse
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Cassie` said:
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Click to expand...
Click to collapse
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
*Detection* said:
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
Click to expand...
Click to collapse
I've had no luck flashing it with Oreo. It's definitely going to the repair centre. Such a shame.
I'm very grateful for your time and help with this. I will report back this weekend with the results of what the repair centre will do regarding the device. Don't like to leave a thread without an end result.
Many thanks again!
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W