If you have recently purchased the latest SAMSUNG Galaxy Pro handset then we will see on how you can update to the latest firmware of Android 2.2.2 version from the current version of either 2.2.1 or even 2.2 Froyo version. There are many add-ons which have been included in this update of Froyo 2.2.2 version which we will see in the due course of this article. Please note that any one from any part of the World can proceed and update their device of SAMSUNG Galaxy Pro handset but the only condition being that you should ensure that your phone is not a network locked handset which means that your handset should not be network locked which means that in other words it should be SIM FREE. The simplest way to find whether the device is network locked or not then you can just find by a simply trick that is if you see any operator’s name on the phone then it’s a Network locked phone and this update is not for you guys. The reason being this update will or will not work on this phone is because all the network locked phones are only updated with the Operator as it has some dedicated applications. This all new update of SAMSUNG Galaxy Pro is dubbed as Froyo JPKC4 which we will look on how you can update with the same.
So, let’s proceed and see on what are the things which you will have to look out for before updating your phone as well as while updating your phone. So it’s highly recommended to follow the instructions carefully before proceeding to the update as if you don’t follow the instructions which are mentioned below then there is a high probability that you may even brick your phone and your phone may turn into an expensive paperweight after which your device may or may not become repairable or irreparable.
There are several improvements which have been done. Please note that there are no changes if you compare with the version of. Please note that many users keep repeatedly address the issue of NO INTERNET CONNECTION working after the firmware update, for all those i would like to say that since the firmware upgrade process will be undergone all the APN Settings which are responsible for the Internet access will be wiped and you will have to reconfigure them all to get an Internet access and in the same way you will also have to configure all the MMS settings to be able to send the MMS from your phone after the firmware update.Also, updating this firmware in any manner will not void the warranty or spoil the phone as long as you are following every single instruction which is mentioned below. Please note that in any manner that is in part or in whole we can’t be held responsible for anything and this firmware is not recommended for all those whose phones are network locked.
Pre requisites for Firmware update:
Please note that before proceeding to the updation of the Galaxy Pro, ensure that your phone is having the model number as Samsung Galaxy Pro B7510 and not any other similar looking phones as if you install with this firmware then some of the functionalities won’t run and could even lead to serious damage to your phone.
Ensure that all data which is present in your phone is backed up in your computer which can be done by using the Astro File Manager application. Also, you can manage all contacts by syncing all of them with the Gmail.
Next up ensure that you have removed the SIM card as well as the external SD cards if any in the phone,
After this, ensure that you keep some things like USB cable which you have got with your Galaxy S GT I9000 and also the Galaxy S device,
Most importantly you need to ensure that your phone has atleast75-80% of battery power left, this is just an advisory which if followed then you will not experience any difficulties as while updation of the device the battery consumption is at a maximum,
Ensure that your computer / laptop which runs on a XP, Vista or Windows 7 OS the firewall and other antivirus programs are disabled and also you should have admin privileges to download and install the software including the drivers and also along with this you will be requiring the USB port on your computer which supports USB 2.0.
(Optional) Many of the Galaxy Pro users have reported the problem that they are unable to get into the download mode which is the top most necessity for updating your device, so for all those we came up with a tutorial here, just follow the given instructions and you can easily fix the download mode and also the recovery mode bug. This procedure is only for those whose devices unable to get into the download mode and the recovery mode.
Please note that flashing with the firmwares doesn’t mean that you are ROOTING Galaxy Pro. If you have flashed with Voodoo Lag fixes then too you can easily flash your device with this firmware.
Ensure that you have closed the KIES completely and also disable any firewalls, antivirus if any. Be rest assured as all the files which are mentioned in this article are safe and virus free.
Procedure to install Froyo 2.2 in SAMSUNG Galaxy Pro :
First of all you will have to download the Froyo JPKC4 2.2 Zip file from here and need to unzip the same to get the files and also the flash tool Odin too will be contained in this. Please note that in the process of extraction, if you are prompted to enter any password then enter the password as “samfirmware.com” without the inverted comas. Preferably, extract to the desktop so that you can easily find the file for flashing it to your phone. Please note that you should not rename the file in any manner or else the files won’t be recognized by the flashing tool which is Odin in this case.
Now, after finishing the download you will have to now ensure that you are turning your phone off so that the download mode which is nothing but the safe mode is activated in your phone. After turning Off the phone, you will have to first push the “Q” button to enter in to the download mode which will look like as shown in the below screen shot. If you have successfully entered into the download mode then you will see a green screen which is shown below. Also, additionally note that if the device boots in the normal mode with the home screen then you will have to again switch off the device and retry the process and if despite retrying you are unable to get into download mode then you will have to fix the download mode error for your phone. You can see the download mode screen on how it looks like.
Now, after this you will have to connect the phone to the computer where you have downloaded and extracted the zip file from the above link. Please note that while connecting the USB cable you will have to make sure that the Odin software is open as mentioned and shown above, as soon as you connect the phone to the Odin, the ID COM block will turn yellow after which you will have to enter the files by clicking on the corresponding options as shown below,
BOOT – APBOOT_B7510JPKC4_CL968357_REV00_user_low_true.tar.md5,
Phone – MODEM_B7510JXKC2_REV00.tar.md5,
PDA – CODE_B7510JPKC4_CL968357_REV00_user_low_true.tar.md5,
CSC – CSC_B7510OJPKC2_CL951730_REV00_user_low_true.tar.md5,
As soon as you feed in the files, you will have to double check the same and then you will have to proceed and click on the “Start” option to start the firmware update process. After clicking on the start, you will see that the firmware will be installed in your phone within a time of not more than 5 minutes.
Now, you can see that the flashing process is being in process and you will have to make sure that you don’t interrupt the flashing process as this may be fatal for your phone. So, after few minutes of time you will see the Odin screen as shown below,
Now, that’s it as soon as you see that the above screen is shown in the Odin, you will have to wait for the home screen to see in the phone and there you go, you have now successfully installed the latest firmware of 2.3.3 Gingerbread for your Galaxy Gio Android phone. Now, after this you will have reset the phone just to ensure that all the cache data is erased which can be done by following the below step.
For checking on which firmware you are currently on, you will have to go to the Settings > About Phone> Firmware Version where you will find the version of Android OS where it will show 2.3.4. As you can see above that we have shown some of the images of latest Gingerbread update of 2.3.3. So, let us know if you face any sorts of issues as we will see to it that all issues are resolved. Alternatively, you can also dial *#1234# to check the version number.
for more details on Samsung Galaxy Pro do visit Galaxy Pro Blog
Thanks for full guide.My phone stopped suddenly during update process now it won't go to "Downloading mode" by pressing Q+power key any more.Is there any solution to this?
Please help.
So its been a long time coming, and I've finally compiled the files and time to make the long promised thread on flashing or modifying demo units. Most information herein will also apply to the G925X, granted that you have the corresponding firmwares.
If you find this compilation of information and/or files particularly useful, please consider buying me a beverage with the donate button, thanks!
Please do not direct link to my files. Send people to this thread instead. This prevents confused users and helps everyone involved.
Table of contents
Background info on the G920X
What can and can't be flashed
Returning to stock
Disabling retail mode
Creating a working Gear VR device while on a Demo Unit rom
Flashing to other variant roms
Special features like the fingerprint scanner
Available firmware files
Background info on the G920X / G925X
The G920X and G925X are live demo unit versions of the Samsung Galaxy S6 and S6 edge distributed internationally. They are almost full featured devices minus modem components and anything directly related to it. Although the bootloader allows for flashing of G920F / G925F files, several guides below offer a way to accomplish a nearly complete experience on the stock rom, which does not attempt to use the non-existent cell phone components but suffers a couple of minor drawbacks.
To keep it simple, the following features work, with caveats as noted -
Fast Charging - Stock G920X / G925X kernel may turn off charging around 70%. Will experiment with directly flashing other kernels on top and update this.
Gear VR - Works once following instructions below. Some power savings are evident and the phone does not seem to get as hot as the G920T/F/I and G925T/F/I, which is an awesome bonus. On stock G920X / G925X, there is an additional disclaimer screen when first putting the device on. There may also be a timeout where the currently open app closes if the device is not worn for a period of time. Need to do more experiments. Please test and report your own findings. You can always flash a G920F / G925F rom and compare.
Fingerprint scanner - Works after flashing 5.1.1 bootloader and rom and running software update, then flashing to G920F / G925F. Should also be able to root the stock rom and replace the settings apk with one from the G920F / G925F to get it working (possibly fingerprint packages as well).
32GB memory - Unfortunately this one is a bit painful. Samsung has started signing their PIT partition map files blocking us from flashing one with a reasonable hidden partition size (stock is 4gb). Until this is cracked there is no way to reintegrate this space into user data. In the meantime, if you have root you can edit the default mounting options for the hidden partition (change to rw) and create a symlink or similar to it in your userdata partition as a partial workaround.
What can and can't be flashed
All G920X / G925X and G920F /G925F roms should work, but you must remove bootloader files (cm.bin, sboot.bin, param.bin, modem.bin) to use G920F / G925F roms correctly.
If your G920X / G925X is currently on 5.0.2, you may have issues flashing or using certain features like fingerprint on 5.1.1 roms due to the old bootloader. It's recommended to update to the newer one using the files below, running the one available system update, and then proceeding with custom recovery and G920F / G925F flashing.
Returning to stock
Simple enough, for G920X, download the files below and use odin 3.10.6 or newer to load up all three. If you were on 5.0.2 or don't know, go into the odin options tab and check off bootloader update before starting. There is currently one update available that will download and install after you finish setting up the rom.
S6 Edge, G925X, see post here and use the files linked to revert to stock and obtain a newer bootloader - http://forum.xda-developers.com/showpost.php?p=63762911&postcount=104
Disabling retail mode
There are two main apps and main passwords to deal with here, the admin password, 5444, and the master password, M729Q16K8546. After your system has been flashed and updated, enter the application called "RetailMode" and enter the admin password. Untick Play time scheduling (this setting may not stick) and then Service Enable. You must now enter the master password. Now exit the app and open "Samsung Retail Mode" and enter Customize Experience Contents, entering the admin password. Disable Retail contents protection (wait a bit for it and tap a few times to keep the device awake until it says that setup is finished), and, for safety, set the auto reset timer to the maximum timeout (3 hours?). Restart the app and enter Configuration Settings. Enter the admin password and disable the Factory Reset protection. Enter the master password once more and choose NOT to reset the device. Now tap "Delete hidden folders" and confirm. At this point you've finished with both retail mode apps.
You're now free to delete the folder in the main user storage called "Retail" or "RetailMedia". This is a big folder so you'll be happy to see it gone. If for any reason it wont delete, turn the retail contents protection from above back on, and after the reboot enable and disable service mode again. Now turn off retail protection (keeping the device awake) and delete the folder. If all else fails, delete if via your PC while the wizard is turning protection off.
Optionally, download Package Disabler Pro and disable the two retailmode applications used above. This will remove the notification tray icon as well as ensure that the services are not turned back on.
If at any point you factory reset the device, you will likely need to repeat this process.
Creating a working Gear VR device while on a Demo Unit rom
Currently recommend using a G920F / G925F rom instead if Gear VR is your primary use case.
You'll need to start by returning to a baseline stock setup with the files at the bottom of the post as directed above. Once you've booted into it and set up (samsung account sign in NOT necessary), check for system updates and let it update to the latest build. Disable retail mode as per above and delete its stray files. Download the Oculus Base package here - https://drive.google.com/file/d/0B4LLzOQW_EV4TzFRWmhqbEFNZkk/view?usp=sharing and extract all included APKs onto your phone. Install ALL of them, then open the Oculus app and sign in / sign up, then give the app a moment to recognize that you have all requisite APKs already installed. That's it! You're ready to slide the device into your Gear VR, accept the "extra" disclaimer page until a full disable method is found, and start the tutorial/download more apps. If you disable bloatware using package disabler, be aware that disabling some things will cause the Oculus app to fail to install its own apps.
Flashing to other variant roms
G920F roms and possibly others will flash and run just fine. The only preparation required is the removal of the modem, bootloader, PIT, and related partitions. This is mainly because Odin will fail, and not specifically due to incompatibility (though some pieces are in fact incompatible). G920FXXU3QOKN is provided below in the downloads with the extra files already removed and ready to flash, otherwise, continue on for instructions on modifying any other rom package. For any 5.1.1 rom such as those listed below, use the Return To Stock instructions first if you aren't sure that you're already on a 5.1.1 compatible bootloader.
To proceed, take an existing rom archive and remove the .md5 from the filename. Copy it to an available *unix machine and run the following commands -
tar --delete --file=[Filename here] hidden.img
tar --delete --file=[Filename here] cm.bin
tar --delete --file=[Filename here] sboot.bin
tar --delete --file=[Filename here] modem.bin
If a PIT file is included, delete it in the same way.
Now load the file up in odin and flash it over. Note that if you flash any non-stock kernel or recovery, it may work for up to one reboot, after which it will bootloop. Always be sure to test across several reboots before confirming that a specific rom or kernel works.
Special features like the fingerprint scanner
Confirmed working when flashing to G920FXXU3QOJQ, further tests to follow.
Available firmware files
G920XXXU1BOH2 - Install and use system update to get latest version, then disable retail mode as listed above
If your current/old rom was 5.0.2, download the bootloader (BL) first and flash it in odin as bootloader update (use the checkbox in options).
PIT file included in CSC.
AP - https://mega.nz/#!34EG2BCZ!m1WywuvOP3awZ2S9Sh5WIxmhzP-pOSs0wG7DYA-ehyI
BL - https://mega.nz/#!bxt3XBIK!-iH4gXYjQFVa3GDWFpv-W1Jg_Jxy0wR9kLigTGKX368
CSC - https://mega.nz/#!K91RgQjZ!wPtNc1RNTLTfcQRRa2OYNQuy40p3haMAC9R4ccggxKg
Special -
CSC without hidden.img - https://mega.nz/#!Cs9lASQa!4vKuuFabqRb3QeQA3PPZHq92IDg8iRr9fPmnbYqUtx0
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4LLzOQW_EV4ck5CeEF3MWpWUkk/view?usp=sharing (dead link, you'll have to make your own, sorry)
G920XZCU1BOI2 Files, only to be used if you specifically need them -
AP - https://mega.nz/#!Cx03WTTQ!-LyhT6baji6zdorVVMHE8S9cNJkFataORuWRNHqGFRs
BL - https://mega.nz/#!C8NShYya!dWxyz1VuX-4Jjws60f2M732FUlniKlA_dmkQk5HhDps
CSC - https://mega.nz/#!a1U1zZYQ!4qezYWoj16PylxU3_2kLFaafK_pJvSREI5r7bZ0zHOU
Reserved
seargent007 said:
Reserved
Click to expand...
Click to collapse
Great work
I normally just flash twrp and install one of the many roms from xda and if they loop, i just flash one of the many custom kernels out there.
Aldo if you want use VR you have to use original Kernel, very pixelated with custom kernel
keep up the info would love to be able to use full internal storage instead of 20gb
Great Start!
Thinking of picking up a demo unit - looking forward to reading more.
this is so amazing, thank you for your post
This is so amazing, thank you for your post.
Bought ldu via fraud trade.
But still pretty happy - it was cheap and i bought it as a gear vr device in development purposes.
What i did to make it work with release vr SM-R322:
1) Made a root via odin anddownload.chainfire.eu\733\CF-Root1\CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip?retrieve_file=1
2) Removed demo soft with this -droidviews.com\list-of-galaxy-s6-and-s6-edge-bloat-apps-how-to-remove-them-without-root\
3) Followed the instructions from section Creating a working Gear VR device while on a Demo Unit rom
I think root is not really necessary, cheers
Hi @Seargant007 i am interested in G920XZCU1BOI2 if you can help me
am intersted in G920XZCU1BOI2 can u pls help me
tareqak13 said:
Hi @Seargant007 i am interested in G920XZCU1BOI2 if you can help me
Click to expand...
Click to collapse
ixgeneral said:
am intersted in G920XZCU1BOI2 can u pls help me
Click to expand...
Click to collapse
Hey folks, what are you looking to do with that specific version?
Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.
de.monkeyz said:
Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.
Click to expand...
Click to collapse
Thanks, unforunately the easiest route is in fact to go to G920F roms, but it would be nice to get a fully functional stock rom (I hate the perpetually crossed out radio signal and such). I don't know how much longer I'll have access to a demo unit for, but if I can I'll make the Gear disclaimer screen a priority to hunt down.
de.monkeyz said:
Thanks for this, extremely helpful. I had a go with the stock G920X rom for use with a Gear VR (consumer edition), but the extra warning it shows was causing a few issues. Namely, that no matter what you do, after the disclaimer you *always* boot into Oculus Home. Meaning that you can't start an app from the Oculus store in regular phone mode, or an app from Sideload VR. It also meant I couldn't link my Twitch account to Oculus Video- perhaps I was doing something wrong but changing to G920F rom fixed my issue.
Click to expand...
Click to collapse
I have the same problem you had. Cannot test apps made with Unity because of the stupid warning. Thanks to SEARGENT (good fckin job ) I managed to get rid of retail mode, but when I flashed some g920f stock I bricked my s6. Now I reverted to the stock suggested by seargent.
I dont know why I bricked the phone, maybe I used a 5.0.2 variant.
Can you tell me what stock firmare worked for you , and how did you flash it ?
---------- Post added at 12:40 AM ---------- Previous post was at 12:32 AM ----------
seargent007 said:
Thanks, unforunately the easiest route is in fact to go to G920F roms, but it would be nice to get a fully functional stock rom (I hate the perpetually crossed out radio signal and such). I don't know how much longer I'll have access to a demo unit for, but if I can I'll make the Gear disclaimer screen a priority to hunt down.
Click to expand...
Click to collapse
Pfff, for me going to g920f seems imposible. What I am doing wrong ?
Maybe this : since I only use Windows I deleted the four bin files from one g920f stock image by decompressing the .tar.md5 file, deleting four files and compressing again to .tar (without md5). Odin accepted the .tar file, flashing was succesful, but it seems that it was a wrong version for me.
mirceanu said:
I have the same problem you had. Cannot test apps made with Unity because of the stupid warning. Thanks to SEARGENT (good fckin job ) I managed to get rid of retail mode, but when I flashed some g920f stock I bricked my s6. Now I reverted to the stock suggested by seargent.
I dont know why I bricked the phone, maybe I used a 5.0.2 variant.
Can you tell me what stock firmare worked for you , and how did you flash it ?
---------- Post added at 12:40 AM ---------- Previous post was at 12:32 AM ----------
Pfff, for me going to g920f seems imposible. What I am doing wrong ?
Maybe this : since I only use Windows I deleted the four bin files from one g920f stock image by decompressing the .tar.md5 file, deleting four files and compressing again to .tar (without md5). Odin accepted the .tar file, flashing was succesful, but it seems that it was a wrong version for me.
Click to expand...
Click to collapse
Did you follow steps for doing the bootloader update, and then follow up by having the rom update to the latest build? If you have, I can tell you that G920FXXU3QOJQ and G920FXXU3QOKN work perfectly fine for me. I'll upload the latter of the two with the modem/BL ripped out and PM you a link, so you can test it and let me know if you still have issues. Generally speaking you don't want to mess with tarring/untarring, but I don't know for sure that it's the cause of your issue.
seargent007 said:
Did you follow steps for doing the bootloader update, and then follow up by having the rom update to the latest build? If you have, I can tell you that G920FXXU3QOJQ and G920FXXU3QOKN work perfectly fine for me. I'll upload the latter of the two with the modem/BL ripped out and PM you a link, so you can test it and let me know if you still have issues. Generally speaking you don't want to mess with tarring/untarring, but I don't know for sure that it's the cause of your issue.
Click to expand...
Click to collapse
Seargent I sent you an PM with what I did.
Now I reflashed a G920FXXU3QOJQ version and it works well.
The next step I want to do is to root the unit to get rid of the bloatware that eats my memory and processot time. Any suggestion ?
The easiest way to turn off the bloat is by using package disabler pro, just be aware that disabling some of it will interfere with some system functions.
Any BL to use Marsh 6.0
datto666 said:
Any BL to use Marsh 6.0
Click to expand...
Click to collapse
Is this works room with sm-g920x already and how it is run
datto666 said:
Any BL to use Marsh 6.0
Click to expand...
Click to collapse
Your best (and probably only) bet is to flash back to stock and wait for an update to 6.0, then rip apart a 6.0 G920F package as detailed and flash it.
Hi , there is a ripped 6.0MM going around but cant boot with loli Bootloader , atm TWRP cant boot 6.0MM either.
So cant flash the LDU with Original BL and no TWRP that will boot 6.0MM
sit and wait i suppose
datto666 said:
Hi , there is a ripped 6.0MM going around but cant boot with loli Bootloader , atm TWRP cant boot 6.0MM either.
So cant flash the LDU with Original BL and no TWRP that will boot 6.0MM
sit and wait i suppose
Click to expand...
Click to collapse
That's my point, you need to sit on the stock rom and wait for an LDU update to be pushed that brings you to 6.0 before trying anything. If I can't get my hands on the odin files for 6.0, the procedure will still be the same even after the update is pushed; Revert to stock, update so your BL is updated, then go to another rom.
seargent007 said:
So its been a long time coming, and I've finally compiled the files and time to make the long promised thread on flashing or modifying demo units. Most information herein will also apply to the G925X, granted that you have the corresponding firmwares.
If you find this compilation of information and/or files particularly useful, please consider buying me a beverage with the donate button, thanks!
Please do not direct link to my files. Send people to this thread instead. This prevents confused users and helps everyone involved.
Table of contents
Background info on the G920X
What can and can't be flashed
Returning to stock
Disabling retail mode
Creating a working Gear VR device while on a Demo Unit rom
Flashing to other variant roms
Special features like the fingerprint scanner
Available firmware files
Background info on the G920X
The G920X is a live demo unit version of the Samsung Galaxy S6 distributed internationally. It is an almost full featured device minus modem components and anything directly related to it. Although the bootloader allows for flashing of G920F files, several guides below offer a way to accomplish a nearly complete experience on the stock rom, which does not attempt to use the non-existent cell phone components but suffers a couple of minor drawbacks.
To keep it simple, the following features work, with caveats as noted -
Fast Charging - Stock G920X kernel may turn off charging around 70%. Will experiment with directly flashing other kernels on top and update this.
Gear VR - Works once following instructions below. Some power savings are evident and the phone does not seem to get as hot as the G920T/F/I, which is an awesome bonus. On stock G920X, there is an additional disclaimer screen when first putting the device on. There may also be a timeout where the currently open app closes if the device is not worn for a period of time. Need to do more experiments. Please test and report your own findings. You can always flash a G920F rom and compare.
Fingerprint scanner - Works after flashing 5.1.1 bootloader and rom and running software update, then flashing to G920F. Should also be able to root the stock rom and replace the settings apk with one from the G920F to get it working (possibly fingerprint packages as well).
32GB memory - Unfortunately this one is a bit painful. Samsung has started signing their PIT partition map files blocking us from flashing one with a reasonable hidden partition size (stock is 4gb). Until this is cracked there is no way to reintegrate this space into user data. In the meantime, if you have root you can edit the default mounting options for the hidden partition (change to rw) and create a symlink or similar to it in your userdata partition as a partial workaround.
What can and can't be flashed
All G920X and G920F roms should work, but you must remove bootloader files (cm.bin, sboot.bin, param.bin, modem.bin) to use G920F roms correctly.
If your G920X is currently on 5.0.2, you may have issues flashing or using certain features like fingerprint on 5.1.1 roms due to the old bootloader. It's recommended to update to the newer one using the files below, running the one available system update, and then proceeding with custom recovery and G920F flashing.
Returning to stock
Simple enough, download the files below and use odin 3.10.6 or newer to load up all three. If you were on 5.0.2 or don't know, go into the odin options tab and check off bootloader update before starting. There is currently one update available that will download and install after you finish setting up the rom.
Disabling retail mode
There are two main apps and main passwords to deal with here, the admin password, 5444, and the master password, M729Q16K8546. After your system has been flashed and updated, enter the application called "RetailMode" and enter the admin password. Untick Play time scheduling (this setting may not stick) and then Service Enable. You must now enter the master password. Now exit the app and open "Samsung Retail Mode" and enter Customize Experience Contents, entering the admin password. Disable Retail contents protection (wait a bit for it and tap a few times to keep the device awake until it says that setup is finished), and, for safety, set the auto reset timer to the maximum timeout (3 hours?). Restart the app and enter Configuration Settings. Enter the admin password and disable the Factory Reset protection. Enter the master password once more and choose NOT to reset the device. Now tap "Delete hidden folders" and confirm. At this point you've finished with both retail mode apps.
You're now free to delete the folder in the main user storage called "Retail" or "RetailMedia". This is a big folder so you'll be happy to see it gone. If for any reason it wont delete, turn the retail contents protection from above back on, and after the reboot enable and disable service mode again. Now turn off retail protection (keeping the device awake) and delete the folder. If all else fails, delete if via your PC while the wizard is turning protection off.
Optionally, download Package Disabler Pro and disable the two retailmode applications used above. This will remove the notification tray icon as well as ensure that the services are not turned back on.
If at any point you factory reset the device, you will likely need to repeat this process.
Creating a working Gear VR device while on a Demo Unit rom
Currently recommend using a G920F rom instead if Gear VR is your primary use case
You'll need to start by returning to a baseline stock setup with the files at the bottom of the post as directed above. Once you've booted into it and set up (samsung account sign in NOT necessary), check for system updates and let it update to the latest build. Disable retail mode as per above and delete its stray files. Download the Oculus Base package here - https://drive.google.com/open?id=0B4LLzOQW_EV4WFZ6ZS1vUHBiT2c and extract all included APKs onto your phone. Install ALL of them, then open the Oculus app and sign in / sign up, then give the app a moment to recognize that you have all requisite APKs already installed. That's it! You're ready to slide the device into your Gear VR, accept the "extra" disclaimer page until a full disable method is found, and start the tutorial/download more apps. If you disable bloatware using package disabler, be aware that disabling some things will cause the Oculus app to fail to install its own apps.
Flashing to other variant roms
G920F roms and possibly others will flash and run just fine. The only preparation required is the removal of the modem, bootloader, PIT, and related partitions. This is mainly because Odin will fail, and not specifically due to incompatibility (though some pieces are in fact incompatible). G920FXXU3QOKN is provided below in the downloads with the extra files already removed and ready to flash, otherwise, continue on for instructions on modifying any other rom package. For any 5.1.1 rom such as those listed below, use the Return To Stock instructions first if you aren't sure that you're already on a 5.1.1 compatible bootloader.
To proceed, take an existing rom archive and remove the .md5 from the filename. Copy it to an available *unix machine and run the following commands -
tar --delete --file=[Filename here] hidden.img
tar --delete --file=[Filename here] cm.bin
tar --delete --file=[Filename here] sboot.bin
tar --delete --file=[Filename here] modem.bin
If a PIT file is included, delete it in the same way.
Now load the file up in odin and flash it over. Note that if you flash any non-stock kernel or recovery, it may work for up to one reboot, after which it will bootloop. Always be sure to test across several reboots before confirming that a specific rom or kernel works.
Special features like the fingerprint scanner
Confirmed working when flashing to G920FXXU3QOJQ, further tests to follow.
Available firmware files
G920XXXU1BOH2 - Install and use system update to get latest version, then disable retail mode as listed above
If your current/old rom was 5.0.2, download the bootloader (BL) first and flash it in odin as bootloader update (use the checkbox in options).
PIT file included in CSC.
AP - https://drive.google.com/open?id=0B4LLzOQW_EV4cE1XX290Mk1ycG8
BL - https://drive.google.com/open?id=0B4LLzOQW_EV4Z1dtVlJCSVZfVE0
CSC - https://drive.google.com/open?id=0B4LLzOQW_EV4VTNydlZxMEsyaWc
Special -
CSC without hidden.img - https://drive.google.com/open?id=0B4LLzOQW_EV4OENyS1p2dFd1WEU
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4LLzOQW_EV4ck5CeEF3MWpWUkk/view?usp=sharing
G920XZCU1BOI2 also available if someone has a specific need for it.
Click to expand...
Click to collapse
Special -
CSC without hidden.img - https://drive.google.com/open?id=0B4...ENyS1p2dFd1WEU
G920F Rom with modem/bl/hidden already removed and verified working - G920FXXU3QOKN - https://drive.google.com/file/d/0B4L...ew?usp=sharing
Click to expand...
Click to collapse
Are you saying that these surrender the 4Gb or so that the hidden.img is holding hostage?
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .