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!
Related
Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Edit: Screen is not faint and the device is working.
So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
biggiesmalls657 said:
Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Click to expand...
Click to collapse
Gatsrom said:
So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
Click to expand...
Click to collapse
Thats why ^^^^^^^ i love this great community because people help each other and positive feedback rather than negativity. I have modified dozens of device over the years and this device is my first big fail as of now but I will let it die. What gets me is Verizon and ATT know that locking their device makes people mad and yet they continue to do whats best for business. I someday would love to reach dev status. How would I flash the recovery without download mode?
Debrick IMG
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story
just boots with RECOVERY BOOTING....then hangs...
--- wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working.
Click to expand...
Click to collapse
the first one sounds so, that the recovery Image was/is the wrong one. This matched also the 2nd one : Stock, but Wifi is not working. If you flash e.g. on P905 the H3 Imagage and after that the C3 kernel, Wifi doesn't work in this status also anymore. I'll believe, you've flashed a wrong image.
To change anything / or the repair the Tab, you must have the possibility to have an access to the Tablet.
What does you've try?
Fastboot / Recovery-Menu? [This one failed -if I've understood you right]
Download-Menu?
Up to which point does your Tab start's up ? Doers you've any access?
biggiesmalls657 said:
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story
Click to expand...
Click to collapse
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x
Gatsrom said:
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x
Click to expand...
Click to collapse
Now the software wont flash and there seems to be a hardware issue (my screen flickers) and it didnt last night.
Update: This device is fixed except for wifi wont initialize but this can help other users. Please lock this thread and hope it helps other people in unbricking! I love XDA and its community!
Update: This device is fixed except for wifi wont initialize but this can help other users
Click to expand...
Click to collapse
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?
Mad07 said:
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?
Click to expand...
Click to collapse
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.
biggiesmalls657 said:
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.
Click to expand...
Click to collapse
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
Wifi and bluetooth and system status is custom and updating bricks and puts me back to letting it die.
Wifi and bluetooth and system status is custom and updating bricks
Click to expand...
Click to collapse
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
updating bricks
Click to expand...
Click to collapse
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset
Mad07 said:
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset
Click to expand...
Click to collapse
I had NB1 installed and it was working then i used Repair Assistant and it has recovery booting and the boot logo with Custom android. They wont cover it for insurance, i might as well just damage and pay the deductible. I have tried everything and it results in a brick.
From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash
Mad07 said:
From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash
Click to expand...
Click to collapse
Yes the latest build is what I flashed. I wonder if the kernel changed but right now NB1 makes it usable with no WiFi or bluetooth.
Which Rom does you mean exactly with NB1 ?
the only one, which I've found - which contains NB1 at the end is:
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 617169
Build date: Thu, 06 Feb 2014 12:19:18 +0000
Product Code: VZW
PDA: P905VVRUANB1
CSC: P905VVZWANB1
MODEM: P905VVRUANB1
Click to expand...
Click to collapse
Why you don't try to flash the K1 Rom? [See above].
If I think about my Galaxy S3 LTE : I have the old Bootloader ( without Knox ) on the device -> if I flash the new System / Kernel without the new Bootloader, I'll have also a problem with a nonworking Wifi ...
Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
The software is flashed and notice the system sleeps and screen wont turn back on until i three finger salute. Boot Logo has no unlocked symbol but About phone displays Custom. Also Wifi/Bluetooth issue which I could not find. If i can fix the wifi and bluetooth i wont send into verizon. They should cover it, Odin mode displays 0x0.
Edit: Odin mode still displays SYSTEM STATUS: Custom even though I flashed the NB1 build. Wifi/Bluetooth still do not work. I have wiped data/ cache and rebooted the device. Towelroot didnt work previously but I will try with this build.
ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.
Mad07 said:
ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.
Click to expand...
Click to collapse
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.
biggiesmalls657 said:
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.
Click to expand...
Click to collapse
If Knox still triggered? Ill believe so. K1 is now the current FW?
Try after install TWRP , wipe normal and go into the adv. wipe settings to format / System and / Data / Cache etc..
Reflash K1 again.
How does it looks like Jam of Wifi / BT ? does you received a FC? only Interruption ?
Hello,
I bought a cheap used live demo unit S7 that I want to use just for the GearVR.
It works great so far but the retail services are annoying, I've found articles that mention how to remove the software on S6 units...
I was wondering if the same instructions apply to the S7? Model is "SM-G930x"
I've also read a couple of posts about someone successfully flashing the stock rom using odin, but when going to sammmobile to download the firmware I don't know which country to choose. I bought it in the US but I don't know if there are different firmwares for Snapdragon versions or Exynos versions.
Any help would be appreciated.
Thanks!
In case someone stumbles upon my thread, I have successfully flashed a stock rom into my live demo S7.
I just used Odin and had to delete the same files that needed to be deleted for the S6 demo units using cygwin... cm.bin, sboot.bin and modem.bin. The difference here though is that with the S7 firmware, those files are spread between files, since the firmware zip contains 5 md5 files instead of 1... one is inside the CP file and the other two inside the BL file.
I deleted them all and then flashed with Odin by selecting the main AP file and the 2 modified BL/CP files.
Hope it helps someone in case they are looking to flash an S7 LDU, I'm guessing the same rules apply to the S7 edge though I have not tried that myself.
Everything works perfectly except cellphone calls/internet obviously, and the fingerprint sensor...which appears to commonly not work on live demo units.
Cheers
andrewe1 said:
In case someone stumbles upon my thread, I have successfully flashed a stock rom into my live demo S7.
I just used Odin and had to delete the same files that needed to be deleted for the S6 demo units using cygwin... cm.bin, sboot.bin and modem.bin. The difference here though is that with the S7 firmware, those files are spread between files, since the firmware zip contains 5 md5 files instead of 1... one is inside the CP file and the other two inside the BL file.
I deleted them all and then flashed with Odin by selecting the main AP file and the 2 modified BL/CP files.
Hope it helps someone in case they are looking to flash an S7 LDU, I'm guessing the same rules apply to the S7 edge though I have not tried that myself.
Everything works perfectly except cellphone calls/internet obviously, and the fingerprint sensor...which appears to commonly not work on live demo units.
Cheers
Click to expand...
Click to collapse
Any idea if this same method applies to Verizon demo phones that are actually consumer models running retail software?
I don't know...probably? If the model is the same I don't see why not. Don't take my word for it though... This was my first experience flashing an LDU model.
andrewe1 said:
I don't know...probably? If the model is the same I don't see why not. Don't take my word for it though... This was my first experience flashing an LDU model.
Click to expand...
Click to collapse
Well, since you managed to do it with an X variant, I have pretty high hopes that it will work with an actual consumer model(SM-G935V).
How did you manage to power off the device and go into Download mode?
KillTheSprint said:
Well, since you managed to do it with an X variant, I have pretty high hopes that it will work with an actual consumer model(SM-G935V).
How did you manage to power off the device and go into Download mode?
Click to expand...
Click to collapse
Follow the same instructions here up to the part where you delete the files with cygwin... in that step do what I did:
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Same passwords and everything.
Hope that helps
andrewe1 said:
Follow the same instructions here up to the part where you delete the files with cygwin... in that step do what I did:
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Same passwords and everything.
Hope that helps
Click to expand...
Click to collapse
Thanks!
I am not sure deleting files from the firmware is needed since you needed to delete them since you were flashing a different model firmware on to the demo model. In my case it is just a verizon stock firmware to a regular consumer phone so hopefully after removing the Retail software, Odin successfully flashes the stock firmware.
Hi, Is it possible to give a step by step process taken and the files used to flash with.
thanks in advance.
try to flash stock rom to your s7
---------- Post added at 04:12 AM ---------- Previous post was at 04:11 AM ----------
or try to reset the phone from recovery
Please help guys, I have a Samsung galaxy s7 demo version SM-G930X and stuck in boot loop error. I am trying to install SM-G930F stock rom on this by following this method but don't know how to delete those files from the firmware .tar file. Please can anyone provide a stepwise instruction
flutenpsyte said:
Please help guys, I have a Samsung galaxy s7 demo version SM-G930X and stuck in boot loop error. I am trying to install SM-G930F stock rom on this by following this method but don't know how to delete those files from the firmware .tar file. Please can anyone provide a stepwise instruction
Click to expand...
Click to collapse
here you go: basicly just the same but remember to flash s7 roms/firmware not s6.
Edit: /u/servili007 posted this thread on XDA developers forum which is probably a better guide. I'm not an expert so defer to that if it makes sense. /edit
In case you saw this thread a couple of weeks ago and thought you can get a GearVR capable Samsung S6 for cheap by buying a Live Demo Unit (LDU) here's some warnings:
It's a store display unit meaning it's likely used and abused.
There's no phone capabilities as the cellular antenna and SIM slot are removed.
The screen probably has burn in of some sort and has been on a lot.
It's not covered by warranty so you're getting it as is, and likely no return to the Ebay seller
The stock ROM automatically loads "Retail Mode" that's not simple to remove and it resets the phone
GearVR software likely will not load on it without effort.
If you understand the above, read what might be required before making the plunge.
First, watch this and write down the information he says to get: https://www.youtube.com/watch?v=n8LMyRqBViM
Basically you need to disable "Retail Mode" by installing a ROM that's not retail. Again, this probably won't work and will BRICK your phone, but you've been warned. This works for S6 and not the Note 4 which needs different passwords.
Go to the app drawer and open an app called Samsung Retail (not the Retail Mode program).
Go to Configuration Settings and enter the password 5444 to unlock it.
Then uncheck “Disable the factory reset” and enter the following password M729Q16K8546.
Decline the "Factory Reset" and instead turn your Samsung Galaxy S6 off
Boot into Recovery mode by holding down Volume Up, Power and Home button all at the same time.
Go to Wipe data & factory reset and press OK.
Now comes the fun part: Flash a stock firmware with ODIN. These steps I've got from here, here and here.
Go to sammobile and download the fimware you think it is the right one. This firmware which is a 5.0.2 version from New Zealand worked for more than one person
Extract the firmware file which is a 1.5gb tar.md5 file.
You will now have something like this G920IDVU1AOC6_G920INZC1AOC6_G920IDVU1AOC6_HOME.tar.md5
Rename it to something shorter like G920IDVU1AOC6.tar and be sure to delete the .md5 at the end.
Download the pseudo-Linux emulator Cygwin from it's home site here and install it
Move the tar file (G920IDVU1AOC6.tar) to C:\cygwin\home\''username''
Open cygwin and delete all the ''.bin'' files by typing the following commands (use up arrow to reload last command and edit for next command). Takes a few moments per command.
tar --delete --file=G920IDVU1AOC6.tar modem.bin
tar --delete --file=G920IDVU1AOC6.tar cm.bin
tar --delete --file=G920IDVU1AOC6.tar sboot.bin
Close cygwin. You can check if cygwin really deleted the bin files by opening the .tar file with winRAR.
Make sure the Samsung drivers are installed on your computer. Something you should verify ahead of time (before any of this) by seeing if you can access it from "My Computer" when it's connected.
Download the latest Odin3 v3.10.6 from here and unzip it (the link is in the signature block of the comment). Odin is a program for service stores to reload stock roms into units in maintenance.
Open Odin
Click on AP button and choose modified .tar file from step 7.
Connect your Samsung phone to the pc. Turn it on using Down Volume (not Up), Power and Home buttons. When you get the warning screen about loading up roms can be dangerous, press Up volume to accept.
On Odin screen, you should see the phone connect. Click "Start" and hope it works .... your s6 should boot a few times, and then start up like new, if not, try another fimware from another country from sammobile.
Again, the firmware that seems to work is a 5.0.1 and only if you remove the .bin files. The above worked for myself and I was finally able to load up GearVR. However, as it was a LDU there is burn in easy to make out. In addition it was an S6 with older firmware meaning it's missing out on some improvements.
Please note I don't make a habit of rooting smartphones or messing around installing images into hardware. As such, I probably spent way to much time searching around for the above, downloading a few roms and trying to get it to work before finding the correct path. Hopefully the above saves you some headache if you take the unadvised route of using an LDU for your GearVR.
I found this somewhere on this website:
Free simple factory reset - how to
Okay this is how you do it, super easy
Download: https://apkpure.com/free-simple-fact....android?hl=en
1. Connect phone to PC
2. Place Simple Factory Reset.apk in the phone's storage
3. Install Simple Factory Reset.apk
4. Open Simple Factory Reset
5. Click reset
5. Wait untill you see a message that says something like "not allowed to shut down"
6. Once you see that restart the phone (hold: volume down, volume up, power and home button)
7. As soon as phone goes black, boot into recovery (hold power, volume up, and home button)
8. Let phone reset
Done, phone will restart and retail mode is no more.
This works on all samsung, ive tested it myself on s4, s5, s6, and s7 as well
Donnavarro said:
here you go: basicly just the same but remember to flash s7 roms/firmware not s6.
Edit: /u/servili007 posted this thread on XDA developers forum which is probably a better guide. I'm not an expert so defer to that if it makes sense. /edit
In case you saw this thread a couple of weeks ago and thought you can get a GearVR capable Samsung S6 for cheap by buying a Live Demo Unit (LDU) here's some warnings:
It's a store display unit meaning it's likely used and abused.
There's no phone capabilities as the cellular antenna and SIM slot are removed.
The screen probably has burn in of some sort and has been on a lot.
It's not covered by warranty so you're getting it as is, and likely no return to the Ebay seller
The stock ROM automatically loads "Retail Mode" that's not simple to remove and it resets the phone
GearVR software likely will not load on it without effort.
If you understand the above, read what might be required before making the plunge.
First, watch this and write down the information he says to get: https://www.youtube.com/watch?v=n8LMyRqBViM
Basically you need to disable "Retail Mode" by installing a ROM that's not retail. Again, this probably won't work and will BRICK your phone, but you've been warned. This works for S6 and not the Note 4 which needs different passwords.
Go to the app drawer and open an app called Samsung Retail (not the Retail Mode program).
Go to Configuration Settings and enter the password 5444 to unlock it.
Then uncheck “Disable the factory reset” and enter the following password M729Q16K8546.
Decline the "Factory Reset" and instead turn your Samsung Galaxy S6 off
Boot into Recovery mode by holding down Volume Up, Power and Home button all at the same time.
Go to Wipe data & factory reset and press OK.
Now comes the fun part: Flash a stock firmware with ODIN. These steps I've got from here, here and here.
Go to sammobile and download the fimware you think it is the right one. This firmware which is a 5.0.2 version from New Zealand worked for more than one person
Extract the firmware file which is a 1.5gb tar.md5 file.
You will now have something like this G920IDVU1AOC6_G920INZC1AOC6_G920IDVU1AOC6_HOME.tar.md5
Rename it to something shorter like G920IDVU1AOC6.tar and be sure to delete the .md5 at the end.
Download the pseudo-Linux emulator Cygwin from it's home site here and install it
Move the tar file (G920IDVU1AOC6.tar) to C:\cygwin\home\''username''
Open cygwin and delete all the ''.bin'' files by typing the following commands (use up arrow to reload last command and edit for next command). Takes a few moments per command.
tar --delete --file=G920IDVU1AOC6.tar modem.bin
tar --delete --file=G920IDVU1AOC6.tar cm.bin
tar --delete --file=G920IDVU1AOC6.tar sboot.bin
Close cygwin. You can check if cygwin really deleted the bin files by opening the .tar file with winRAR.
Make sure the Samsung drivers are installed on your computer. Something you should verify ahead of time (before any of this) by seeing if you can access it from "My Computer" when it's connected.
Download the latest Odin3 v3.10.6 from here and unzip it (the link is in the signature block of the comment). Odin is a program for service stores to reload stock roms into units in maintenance.
Open Odin
Click on AP button and choose modified .tar file from step 7.
Connect your Samsung phone to the pc. Turn it on using Down Volume (not Up), Power and Home buttons. When you get the warning screen about loading up roms can be dangerous, press Up volume to accept.
On Odin screen, you should see the phone connect. Click "Start" and hope it works .... your s6 should boot a few times, and then start up like new, if not, try another fimware from another country from sammobile.
Again, the firmware that seems to work is a 5.0.1 and only if you remove the .bin files. The above worked for myself and I was finally able to load up GearVR. However, as it was a LDU there is burn in easy to make out. In addition it was an S6 with older firmware meaning it's missing out on some improvements.
Please note I don't make a habit of rooting smartphones or messing around installing images into hardware. As such, I probably spent way to much time searching around for the above, downloading a few roms and trying to get it to work before finding the correct path. Hopefully the above saves you some headache if you take the unadvised route of using an LDU for your GearVR.
Click to expand...
Click to collapse
Thanks for the Info, I got my s7 LDU working, I just flashed a normal G930F stock room via Odin and it was stuck in bootloop, then flashed a twrp and later went to recovery mode where it showed "dm varity check failed, need to check drk first". I learned that it happens when you are not rooted, so I flashed cf auto root via Odin and after that it booted correctly. The retail softwares all gone. But there's only a problem that it hangs for 2-3seconds every now and then unfortunately.
https://www.s7fanclub.com/2016/04/flash-stock-rom-galaxy-s7-galaxy-s7-edge.html
https://www.s7fanclub.com/2016/03/download-flash-twrp-recovery-root-galaxy-s7-sm-g930f.html
https://www.s7fanclub.com/2016/02/how-to-root-samsung-galaxy-s7.html
I finally removed the Retail Mode from my Verizon Demo Phone.
https://www.youtube.com/watch?v=MXrHmD-mee8
KillTheSprint said:
I finally removed the Retail Mode from my Verizon Demo Phone.
https://www.youtube.com/watch?v=MXrHmD-mee8
Click to expand...
Click to collapse
Why don't you post the method you used.. the video, is not only useless it doesn't work anymore....
All I did was flash it with the stock rom. The Verizon demos seem to have a different bootloader/recovery compared to regular demos. What model do you have?
vo_danh said:
Why don't you post the method you used.. the video, is not only useless it doesn't work anymore....
Click to expand...
Click to collapse
Not surprising considering the post you just replied to is 9 months old....
*Detection* said:
Not surprising considering the post you just replied to is 9 months old....
Click to expand...
Click to collapse
Just wanted to confirm, you got full retail S7 functionality, calls, text, fingerprint reader everything?
KillTheSprint said:
Thanks!
I am not sure deleting files from the firmware is needed since you needed to delete them since you were flashing a different model firmware on to the demo model. In my case it is just a verizon stock firmware to a regular consumer phone so hopefully after removing the Retail software, Odin successfully flashes the stock firmware.
Click to expand...
Click to collapse
bump
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
flutenpsyte said:
Thanks for the Info, I got my s7 LDU working, I just flashed a normal G930F stock room via Odin and it was stuck in bootloop, then flashed a twrp and later went to recovery mode where it showed "dm varity check failed, need to check drk first". I learned that it happens when you are not rooted, so I flashed cf auto root via Odin and after that it booted correctly. The retail softwares all gone. But there's only a problem that it hangs for 2-3seconds every now and then unfortunately.
https://www.s7fanclub.com/2016/04/flash-stock-rom-galaxy-s7-galaxy-s7-edge.html
https://www.s7fanclub.com/2016/03/download-flash-twrp-recovery-root-galaxy-s7-sm-g930f.html
https://www.s7fanclub.com/2016/02/how-to-root-samsung-galaxy-s7.html
Click to expand...
Click to collapse
bump
m.jordan89 said:
Just wanted to confirm, you got full retail S7 functionality, calls, text, fingerprint reader everything?
Click to expand...
Click to collapse
I don't have a demo unit, and no, you won't get all that because there is no modem or fingerprint reader in demo units, so you can't call or text or use fingerprint security
Hi guys,
Not started a thread on XDA for years but I really am stumped.
I have claimed my girlfriends s6 (SM-G920F) after she upgraded and intended to root it and maybe try a few Oreo ROMs etc. After investigation I saw that (I think this is right) I don't need to OEM unlock this version of the device and rooting via Odin is the best way to do it. BTW if I do need to OEM unlock then that might be the solution to my issue, so if some one could clarify that'd be great.
So a week ago I downloaded Odin and also my old favourite CF-AutoRoot after putting in the device details. The package was generated, I unzipped and put it in a folder in my desktop
After putting the device in download mode I run Odin as administrator and plug it in. The device is recognised and I get the blue box to show this.
I then click the AP box and select the image file and click start, everything runs as expected to this point and I get PASS displayed in the info bar. On the phone the progress bar looks like it has not completed and I can see a small portion still to run. On the first try I left phone like this waiting for it reboot for over an hour. I was expecting 5he device to reboot and get the android with the red exclamation point. At this point I restarted manually and saw during the boot process an error message saying Recovery not SE Enforcing in red.
I have read a few posts saying this can be caused by the wrong image being used, so I downloaded the Auto root package again and made sure that it was all correct, but the same thing occurred.
I have been looking and reading for the last week to find a solution, but I'm still in the same position. Can anyone help or point me in the right direction?
If you need any more info let me know.
Thanks in advance
Jon
im in exacltly the same boat pal. was running nanorom on my rooted s6, but had no vr capability and just got some galaxy gear goggles. tried to reflash arter97 kernal and lost my whole setup. ive been in and out of hard brick for last 24hrs and am back now to where you are, i can access download and recoveries via three button combo, but any packages i flash with odin just fail out right.
ive been here before though and usually get out once i find the right stock rom and csc's for my version. iof i find anything ill come back and share it with you pal.
Cheers mate, it's really frustrating. I'll keep looking too and post back if I have any success.
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
copernicus666 said:
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
Click to expand...
Click to collapse
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
what a f**k about!!!!
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
shiko2007 said:
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
Click to expand...
Click to collapse
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
copernicus666 said:
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
Click to expand...
Click to collapse
if your not root yet just download latest your carrier/country firmware
from sammobile
and flash it by odin
but you are probably trip knox so you must root
so the steps you should do :
1-download your carrier/country firmware from sammobile
2-flash it by odin
3-flash cf-auto root to pass bootloop
or
download twrp recovery of g920f and flash it by odin to replace stock recovery then after flash it ,wipe delvik cash then flash su binary
DagsyMc said:
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
Click to expand...
Click to collapse
Legendary post! Cheers mate you just made my morning. I knew the XDA guys would pull through.
I'm on my way to work, but I'll give it a crack later.
Cheers bud - Kudos
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
wilsen23 said:
My bad eyes failed me.
I dLoad'd and used the cf-autoroot sm-g900f
when I should have used
sm-g901f.
The first one seemed to root as it changed 0x0 to 0x1, but would not reboot after that.
I pulled batt & tried the correct one later, but looks hard-bricked to me. Goes thru the steps on Odin, but says Failed and of course no reboot. The blue progress bar shows abt 2% and stays there until disconnect.
Question: anything I can try? Not too concerned for hardware...had a bit o' data I would like back.
Most forum root problems I could find start with unknown issues. I know what I did.
Click to expand...
Click to collapse
Try flashing the stock firmware via Odin. You have to be certain that you flash the exact same firmware build number that you already had on the device before you tried to modify it or at least a firmware that has the same binary version as the firmware that was already on the device. The binary version can be identified by looking at the 5th character from the end of the firmware build number. As long as the firmware that you flash is not an upgraded or a downgraded binary from what you had, your data should still be after the flash is finished. If what you flash is an upgrade or a downgrade from what you had, it will wipe your data. If your firmware comes with two different CSC files, use the HOME CSC to preserve your data, using the other CSC will wipe your data.
Sent from my SM-S767VL using Tapatalk
My bad eyes failed me.
I dLoad'd and used the cf-autoroot sm-g900f
when I should have used
sm-g901f.
The first one seemed to root as it changed 0x0 to 0x1, but would not reboot after that.
I pulled batt & tried the correct one later, but looks hard-bricked to me. Goes thru the steps on Odin, but says Failed and of course no reboot. The blue progress bar shows abt 2% and stays there until disconnect.
Question: anything I can try? Not too concerned for hardware...had a bit o' data I would like back.
Most forum root problems I could find start with unknown issues. I know what I did.
Epilogue
So to finish this off:
I had written stuff down but not the exact build. There were several and I was willing to gamble (nothing to lose).
Originally I was using a Win7 box with and old Odin....and as I said in orig post....the Root did take as there were changes noted on the download screen, but no reboot bcz wrong file. At any rate....
To prep for the gamble I dLoad'd newest Odin to a Win10 box. I also dLoad'd Kies3 to ensure I had drivers as the phn had never been connected to this box. After it was all set up I had trouble finding the firmware I had decided on. Just for poops and giggles I decided to try flashing the CORRECT file again. I had tried that a couple times on the Win7 box right after I discovered my error.
I didn't expect much and wasn't even looking at the phone....and it buzzed. That was gooood buzz bcz it took.
So I got it back, rooted, with all data.
I guess the take away is try with freshest drivers, softwares etc b4 giving up. That is standard advice, but clearly it made all the difference in my case.