Related
First, I am not an expert. I cannot code, I do not produce ROMS in a kitchen. I can use google and I am determined and have learned bits. I offer what worked for me in the hope of helping others.
So, here’s the thing. Like others I went for the release version of KitKat for n8000 and by missing out the modem bit flashed it via Odin. Now the proper KitKat for n8010 comes out but it won’t update via odin, KIES is not happy either. I blame no one but me for this.
I figure it is the sboot that is the problem so I look for a way to flash without it. When I say “I figure” I mean I have put two and two together from many hours of google reading. I may be wrong but in the end I managed it.
Long story a little shorter I find Heimdall and I extracted the components from the n8010 kitkat update (I used winrar on the BTU version) and flashed them leaving out the sboot.img and tz.img bits as either would lead to failed flash. I now have a working n8010 with KitKat which under device, under settings, gives the n8010 build number and is recognised as an n8010 by kies.
It still says n8000 under download mode (due to locked sboot) but if I may get future updates via kies, as it recognises it as an n8010 and says it is up to date for now, then that works well enough for me.
Detailed instructions:
1. Download and unzip your update file of choice and extract the tar.md5 file to separate files. I used winrar but suspect 7-zip would work equally.
2. Download Heimdall (just Google it!).
3. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe.
4. Run zadig.exe from the Drivers folder of the Heimdall Suite.
5. If you get an error as follows:
The program can't start because MSVCP100.dll is missing from your computer.
This means that you haven't installed the Microsoft Visual C++ 2010 runtimes. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Use the x86 even if you are running 64 bit Windows.
6. Put you tab into Download mode (while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC.
7. Once you’ve started Zadig.exe and connected to PC choose Options » List All Devices from the menu.
8. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies).
9. Click Replace Driver (having selected "Install Driver" from the drop down list built into the button).
10. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on.
11. You will need to re-install the Samsung drivers later if you want to run kies.
12. Run Heimdall-Frontend.exe.
13. Hit the utilities tab then detect button.
14. If it doesn’t say detected in the output box it will not work. Try to repeat the above steps. Use a different usb port or a different pc.
15. Now you need to create a pit file. Hit save as and give it a name. Then hit download and it will create a pit file for you.
16. Go to Flash tab and hit browse and find the pit file you created earlier.
17. Then hit the add button. You will notice a drop down menu has appeared next to partition name. Then if you look below under Partition ID in brackets it says what sort of file it needs. So for example MD5HDR in the drop down requires md5.img. Use browse to find the relevant file from the files you extracted in step 1 and select then hit add again. Then repeat this until you have selected all the extracted files EXCEPT sboot.img and tz.img.
18. Hit start.
19. Bask in your new updated n8010 without needing kies or odin.
If you want to repeat this on another tab you can create a heimdall install package using the partitions and pit file you’ve created using the create package tab.
Now comes the question...
I've found places that offer an app for testing whether the sboot is locked (not sure how useful that is?) but several also offer a method for replacing a locked sboot. Such as this batch file:
@ECHO Restore OLD BOOTLOADER N7100!
@pause
@ECHO --- STARTING ----
@ECHO --- WAITING FOR DEVICE
@files1\adb wait-for-device
@ECHO --- Restore BOOTLOADER ---
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
@pause
There are others for different Samsung devices but all have the same block/mmcblk0p1 as the block to replace the sboot. And I also found a common block for the tz.img; mmcblk0p2. My question is whether this would work for the n8010, could we edit this batch slightly, grab the relevant files from a n8010 kitkat update and then have a n8010 sboot again?
Just hoping someone is either expert enough to know or brave enough to try?
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
That may also work.
What do you think of my suggested method to replace the sboot?
jika23 said:
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
Click to expand...
Click to collapse
azureus139 said:
That may also work.
What do you think of my suggested method to replace the sboot?
Click to expand...
Click to collapse
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
I am downloading the gtn7100 kitkat and will extract to check whether they are the same size. That should get us one step closer. I am still not brave enough to use adb to replace the sboot until someone more expert can comment on whether it is likley to be same address on the n8010.
YOSEFE said:
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
Click to expand...
Click to collapse
In a tar file isn't something like the updater script like in a flashable zip. Cause if there is we should know with that where the sboot is flashed.
that batch file won't do it
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
azureus139 said:
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
Click to expand...
Click to collapse
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Sadly that will not help. I have discovered it is because the leaked n8000 kitkat rom has a knox bootloader which cannot, as far as I can discover, be replaced. Thank you for the suggestion.
ivica81 said:
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Click to expand...
Click to collapse
secure boot key is what your looking for
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Well I was already out of warranty so that isn't an issue and I have it working with the proper kitkat for my device so tbh I don't know what difference it really makes. It shows n8000 in download mode and I will have to do something tricky via heimdall for any future updates, is that the only difference? Does it mean no access to custom roms as so far I've been happy to use stock and remove all bloat so that won't be too bad for me personally although it would be a real pain for some.
erica_renee said:
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Click to expand...
Click to collapse
As i said i never flashed that on my device. I am thinking all the issues/ benefits quarks of having the n 8000 boot loader on a non n 8000 device.. There may be NO Disadvantage unless Samsung Chooses to change how they sign there roms and so on.I just think Samsung Should Give us a way to avoid this .
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
I did no wipes and just flashed over the top. All apps and data as before but no phone icon.
JamesEsh said:
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
Click to expand...
Click to collapse
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
raducux said:
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
Click to expand...
Click to collapse
Nothing from me. Everything I found says no way to unlock or replace the kitkat sboot. The n7100 apparently has a way but none for the 8xxx that I have found. Don't know what a jtag is?
fail to finish
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
If you can't get heimdall to detect your tablet then it isn't going to flash to it either so a pit file wouldn't help you. It looks like a driver problem. I'd try uninstalling any samsung drivers and / or kies then reinstalling the heimdall ones.
keevo2481 said:
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This driver is too tired
Thought that could be the issue as it changes every time I reinstall the usb driver. Currently too tired. Going to do a fresh windows or Linux install on my spare computer so it's fresh to go and hopefully doesn't have driver issues. Will confirm how it goes either way. Computer needed an upgrade from 7->8.1 anyway.
wifi problem
hy guys i just did that the guide said everything is working very well i m on 4.4.2 stock samsung. But the WIFI is not working. :crying: can you help me how to fix?
Hi,
Pretty much tried everything (I think) to reconcile this.
Tried to install Kingroot.
Bricked G920F that was on 5.1.1
Can get to Download Mode. But ODIN keeps failing at the last 'Write' bit on the script.
No idea where i am going wrong. Have searched but most threads offer solutions I have already tried.,
All advice welcome.
Thanks!
Tony
myotai said:
Hi,
Pretty much tried everything (I think) to reconcile this.
Tried to install Kingroot.
Bricked G920F that was on 5.1.1
Can get to Download Mode. But ODIN keeps failing at the last 'Write' bit on the script.
No idea where i am going wrong. Have searched but most threads offer solutions I have already tried.,
All advice welcome.
Thanks!
Tony
Click to expand...
Click to collapse
I have had this before. It is usually the "hidden" image part of the flashing process. Extract the rom zip and rename the "hiden.img" to "hidden.img.tar. Then flash this using odin.
You can also uncheck auto reboot and re-partition. Try it then
Just plug the phone to PC in download mode and rescue it via Smart Switch. It'll download the right firmware for your device and flash it automatically.
Here's how you can do it;
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
Hello all,
So, my name is Aaron Hewitt. I am 15 and blind, and am looking for the stock rom for my Samsung galaxy s7 as stated above. The slight problem I am having here is that, from what I have noticed the only place I can obtain the complete factory image is from sammobile.com, However, being blind, I cannot signup to the site, as they have an inaccessible captcha--solving the puzzle. This makes obtaining the correct rom rather difficult, as although I have been able to obtain stock ROMS, they are not the full factory image, that is, PDA, CSC, and phone files. (these are the options I have in odin). I wish to restore the phone to stock and was wondering if anyone could shed some light on where else I can obtain the stock rom, or perhaps send it over.
Any help would be greatly apprishiated.
Thank you,
Aaron Hewitt.
How did you create your account on XDA? and typing this thread? Reading responses?
updato.com
fair question. I have a peace of software on my computer called a screen reader. It reads text as it appears on the screen, and i learned to type at 5 years old. As for creating an account ans posting, their was an audio captcha i could use. Sammobile unfortunately does not have this. and unfortunately updato.com as referenced has the image, however it does not work. the message i get when flashing that via odin os OSM all threds completed. Sucseeded 0 faled 0.
Thanks,
Aaron Hewitt.
Are you putting your phone in Download Mode? (Volume Down & Home & power)
Using ODIN 3.12.3 or newer?
Extracting the download from updato and adding all 4 sections into the appropriate ODIN sections?
Still confused as to how you are managing to do all this with a screen reader, as you need to click small buttons to use ODIN
I am doing all these things, apart from i'm not sure where to put the "bl" file, as i do not have a "bl" button in odin. As for navigating in odin, i am using the tab and shift+tab key combinations to navigate betweene the buttons, and enter/spacebar to activate.
ahewitt13 said:
I am doing all these things, apart from i'm not sure where to put the "bl" file, as i do not have a "bl" button in odin. As for navigating in odin, i am using the tab and shift+tab key combinations to navigate betweene the buttons, and enter/spacebar to activate.
Click to expand...
Click to collapse
BL button is the top one of the 4, in order it goes like this:
1: BL
2: AP
3: CP
4: CSC
This is a link to the latest version of ODIN 3.12.10 so we can be sure you are using a new enough version, all versions from 3.12.3 up have a BL button at the top
http://forum.xda-developers.com/attachment.php?attachmentid=4330999&d=1510555908
It will download as a zip file
First of all thank you for taking the time to read this. I've been struggling with this for a while and I hope we can resolve it somehow.
So here's what's been going on:
My Samsung S7 was an absolute mess for a few weeks, battery life was absolutely miserable (died 10 seconds after unplugging it from charger) but I just assumed it needed a battery replacement.
I've never attempted to root, flash or mess with my device in anyway, not after this issue has already occurred. One day I pull out my phone to check something and it's dead again, okay. nothing out of the usual.
I tried to turn it on and it would get stuck on the Samsung logo. I tried plugging it in and just leaving it and it would stay stuck on the Samsung logo forever. Please note at this point I have not tampered with my devices hardware or software yet.
I tried downloading odin and downloading stock ROMs from somewhere but that didn't work.
My phone is NOT rooted, USB debugging is NOT enabled.
The phone contains a lot of my stuff and I would prefer not to lose them. I was wondering if there was a way for me to retrieve my stuff before factory resetting it or throwing the thing away. The phone itself means nothing to me. I just want what's on it.
Any kind of help is appreciated, I really wanna get to the bottom of this. Thanks in advance to everyone.
How far into the Odin flash did you get? Because a stock flash still wipes data if you use all firmware files.
If you can get into recovery try the wipe cache partition option, this won't wipe any user data but might fight the boot issue.
If you can still get into download mode try flashing the BL and CP firmware files for your model/region/carrier/version and nothing else via Odin. Again flashing just these won't wipe, but may fix issues.
I'd recommend reading his guide before using Odin https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
When downloading firmware I'd recommend using a firmware resource like updato, sammobile or here on xda
Without USB debug and root you're limited in the tricks you can do to get the phone in a state to transfer files.
Beanvee7 said:
How far into the Odin flash did you get? Because a stock flash still wipes data if you use all firmware files.
If you can get into recovery try the wipe cache partition option, this won't wipe any user data but might fight the boot issue.
If you can still get into download mode try flashing the BL and CP firmware files for your model/region/carrier/version and nothing else via Odin. Again flashing just these won't wipe, but may fix issues.
I'd recommend reading his guide before using Odin
When downloading firmware I'd recommend using a firmware resource like updato, sammobile or here on xda
Without USB debug and root you're limited in the tricks you can do to get the phone in a state to transfer files.
Click to expand...
Click to collapse
I'm not entirely sure how far I got. I followed a tutorial that said to flash the BL files but I'm not entirely sure if it worked or not considering my phone wasn't rooted/didn't have USB debugging and didn't restart or fix the issue. I got the files from updato. I've tried wiping the cache partition but that didn't seem to fix it. I haven't tried flashing any CP on there as I didn't know what that was but I will try to do that today.
Should I flash new BL files and try again, and what are CP files/where do I obtain them? Thank you so much for your help.
If you get the firmware from updato, or sammobile it should come with 5 files: AP, CP, BL, CSC and Home CSC all in one zip.
I would say try flashing CP and BL from the zip, and for Odin flashing you don't need USB debugging or root etc. You just need to be in download mode.
So try putting the CP and BL files into Odin and flashing, the newer version the better, but anything thats the same as your android version i.e. if you're on Nougat than any Nougat BL should work
Beanvee7 said:
If you get the firmware from updato, or sammobile it should come with 5 files: AP, CP, BL, CSC and Home CSC all in one zip.
I would say try flashing CP and BL from the zip, and for Odin flashing you don't need USB debugging or root etc. You just need to be in download mode.
So try putting the CP and BL files into Odin and flashing, the newer version the better, but anything thats the same as your android version i.e. if you're on Nougat than any Nougat BL should work
Click to expand...
Click to collapse
So I got the firmware, the most recent I could find that matched my region/carrier etc. I ran it through Odin and it seemed to have worked. Odin said it passed and the phone restarted.
Then it showed that it was applying system updates or something. But then it stopped. It showed the android guy laying down and the words "No command" I tried figuring out how to resolve this but I couldn't find anything that could be done without having USB debugging already enabled. I can't think of anything else to try and I'm running out of options. If you have any more ideas I'd really appreciate it. It seems like such a waste to give up now when the phone is only soft-bricked and not completely useless.
Only extra steps I can think of will save the phone but lose the data