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?
Hello guys
Well the problem is the next one hope u can give me some solutions, because I've tried everything I'm at the border of install a new ROM
Well I have a tablet which was messed up from the usage of hack apps with root usage like the freedom, kingroot, etc... and it stops connecting to the PlayStore
First: It was showing the label "No connection retry" over and over again without the capacity to connect to the PlayStore by any means, Youtube app was affected too
-After a factory reset by the Android software and from the bootloader (holding the keys) restart the Tablet and Youtube was working now, but Playstore remains with the same label
Second: Now we figured out that some rooted app was the one who causes all the trouble but it was gone with the FR, then I figured out that the problem was with the "HOSTS" file, then to use ES File Explorer along with Kingroot to grant it root access to modify the Host, I did it and restart and everything....and now it shows another label: "Error retrieving information from server. RH-01" And still remains with that label.
I tried many lines of code for the Host file:
127.0.0.1 localhost <<--- Alone
And
127.0.0.1 localhost
#127.47.231.138 android.clients.Google.com mtalk.google.com <------with this variant too
None worked, i even use ADAWAY with root permission and didn't work too.
Already did the Non-root methods of deleting the data of all GPlay services the app itself and the framework without success too.
I've already wipe out the user data and done many factory resets without any success too
I really don't know what the hell is blocking the access to the Playstore and dunno what to do now, so every another solution will be very appreciated.
Greetings and thanks in advance!
Dude flash your stock ROM using Odin. Find these files either the Galaxy Tab 4 General or Development or Original Development. Flash the correct one for your model, its OK to flash the different region ROM but do a factory reset. Reply here if it helps
AJPuzon said:
Dude flash your stock ROM using Odin. Find these files either the Galaxy Tab 4 General or Development or Original Development. Flash the correct one for your model, its OK to flash the different region ROM but do a factory reset. Reply here if it helps
Click to expand...
Click to collapse
I tough about flashing it, but there's one inconvenience it seems like this Tablet had Android 4.4 and just find 4.4 stock versions to flash it, but mine has 5.1 installed already and in the device model it's shown as Nexus 5 device dunno why
So in order to flash it, I'll end doing a downgrade from 5.1 to 4.4 dunno if this can be dangerous
Up
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Flapjack said:
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Click to expand...
Click to collapse
If I'm understanding you right, you just want an OTA update applied? If that's the case, Frija is what you want to get the latest firmware for your device, and Odin will be your flasher. For stock rom flashes you don't even need an unlocked bootloader, much less root!
There are a ton of guides for Odin available, but still, if you have any questions please post!
Thanks for the reply!
I've used Odin quite a bit in the past, but I do know different situations need different files, so I'll probably do a quick refresher.
As for root, it definitely is a nice-to-have, mostly to remove bloatware, but if the debloat thread here works pretty good (and someone has info on just how much I can remove and keep Dex functionality), I would love to know that as well.
So, I am having a new problem. Using Frija, I downloaded the latest update. However, no matter what I do, I can't get a PC to recognize the tablet in download mode. It just says something about Windows not being able to recognize the device. In Device Manager, it says: "Device descriptor request failed". I've tried with and without the Samsung drivers, with three different USB cables, on two different PCs.
I'm worried that something is physically wrong with the USB port. That doesn't really make sense, though... as it charges fine, and shows up in Windows correctly once it's fully booted to Android.
**EDIT**
False alarm. I needed to press "up" again after getting into download mode and connecting the PC. So odd. It's updating now!