Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
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?
I wanted to root my Galaxy Note 4 (SM-N910F UK carrier H3G) so I could use the mirroring option in Airdroid.
Long story short, I'm severely disabled so wanted full access to my phone whilst on my pc, without struggling to get my phone all the time. (SWTOR Security Key is one of the many reasons for wanting to not have to grab my phone every time I need to do something on it)
(I can't put phone where it's easily accessible whilst on pc, because of the board I use for keyboard and mouse rested across the arms of my chair)
I THOUGHT I had it sussed, as I had successfully rooted and booted my S3, S4 and Note 2, 3 and 8.0 devices.
However, I didn't read the fine print when using CF-autoroot in that it doesn't work on 5.1.1 atm. Or something along those lines...
Anyway, with my usual eagerness and impatience to do geeky/nerdy deeds, I ended up with my phone in a constant boot loop no matter what I tried.
I scoured the Internet for 3 hours, trying to find the original stock rom for my device and was livid that my usual Google-Fu was failing miserably.
I found one, so I thought, installed the kernel, (couldn't find stock kernel either) installed SuperSU, installed Twprs or whatever it is, (excuse my lack of knowledge please) then installed this "stock" rom.
Turns out it possibly IS the H3G network's Stock Note 4 (SM-N910F) ROM. IF I lived in Italy.
I still would like root access on my phone, but I would like to try and get stock rom back, or something EXCEPTIONALLY similar.
Please, again, excuse my apparent thickness... (and I'm not talking sliced bread here) is it the kernel where rooting takes place, the ROM, or do both have to be involved in the adaptation?
I know very very little about Linux and kernels etc.
I hope that I have described my predicament clearly, and that when one has picked oneself up off the floor from rolling around with much merriment, one (anyone) is able to assist with my screw up.
Best wishes,
(Applebogies for waffling on more than the meat content of a Belgian Blue, (I'm not talking Blue Waffle, but of four legged animals that chew the cud)
(Applebogies also for mentioning The Waffle of Blue-ness in more than one sense of the word, if it makes you Google it and you only just ate and you've never seen it before)
(Finally, applebogies for my rotten and feeble attempts humour, please try to cut through my crap and get to the point ofwhat my conundrum actually is)
So basically in a nutshell, you've bricked your phone? I do know that when I flashed stock ROM the other day, I had to pull the battery, boot into recovery (vol up + home + power) and wipe data/factory reset and wipe cache too. Then it booted just fine try that.
you can find different stock roms for your phone at sammobile (google it) download the firmware from there and flash it with odin. Watch youtube videos on how to flash firmware with odin. its simple
See if you can boot the phone into Download Mode via volume up+home+power. If it boots into download mode that means its not hard bricked. If it doesnt boot into DL the first time you try, do a battery pull for 15-20 seconds, then try again. If that doesnt work, then check your specific device versions forum for an unbrick method, and check for a general unbrick that can be used for all N4's.
If it does boot into download mode, download the stock firmware for your specific N4, flash it via Odin, (instructions are generally included in the thread where you find the stock ROM download) and you should be good to go after that.
Edit: SamMobile does indeed have a firmware for your specific device. Do a google search for sammobile, go to that site, and input SM-N910F into the device search bar. That will take you to a page with a list of firmwares. Theres a list box where you can select your country, that includes country and carrier combinations. Yours will be listed as United Kingdom (H3G)(H3G). Select firmware with PDA version N910FXXU1COJ3.
Not sure why you all think my phone is bricked, I am on it now?
I am however, currently running the Italian version of 3 mobile rom. Looks like asrah has solved that problem though xD
To shorten my previous post:
Where does root happen, on kernel or rom?
Ie - can I have stock rom but still have root access on my phone?
Thank you to asrah for finding my rom.
Thanks all and a very Merry Christmas!
Note - this is for the SM-G930A AKA AT&T model only. Unrooting and flashing firmware works the same way for other carriers, but with different files.
Hi everyone, I just thought I should share how I went about unrooting my S7. I initially rooted it while it was running Nougat already, and I liked the extra customization options. However, I found after several months of using it that the only real feature that I personally liked about having a rooted S7 was the ability to "try" paid apps for free using Lucky Patcher.
The downside of rooting, for me anyway, was severely slow laggy touch inputs and general phone performance. Sometimes - especially after a reboot - I experienced slightly better performance, but overall it just got too annoying. The app that gave me the most trouble was Google Maps. That's why I decided to cut my losses and unroot; I'd figured out which apps I actually wanted to buy since I'd already used them for a while (I will miss free in-app purchases though ).
So after some Googling and reading up, I decided to try for myself. I was already running baseband version G930AUCU4BQA4 before I rooted, so I thought maybe I could just flash stock Nougat and be done. However, all the guides I read say to flash a stock firmware, so that's what I did to be safe.
So first I downloaded the stock firmware for my phone from a website called rootmygalaxy, on the Download Stock ROM For AT&T Galaxy S7/S7 Edge (SM-G930A/SM-G935A) page (being a new user sucks).
After that, I used the stock, unpatched version of Odin v3.12.3, (from Odin's website) to flash the stock firmware onto my phone. It should be noted that the steps you take to flash a firmware to download mode should be 1. Open Odin, 2. Put phone in download mode, 3. plug the phone in. I had some failures in Odin because I was doing that wrong. Steps one and two are probably interchangeable, but just make sure plugging in the phone is the last thing you do. Also, make sure you have ticked USB Debugging and OEM Unlock under developer options before you do any flashing.
Once that was complete, I rebooted my phone and set up Android 6.0.1 on the phone. After a full 24 hours, I still couldn't get any OTA updates, so I decided to manually flash Nougat because it is so much better than Marshmallow.
This guide on the website droidviews called Install Android 7.0 Nougat on AT&T Galaxy S7/ S7 Edge (SM-G930A/ G935A) was very helpful.
Take note of the fact that the guide references baseband versions by the last 4 characters, i.e. G930AUCU4BQA4 becomes just BQA4. I checked my baseband version, which ended in APJ4. According to that guide, all I had to do was flash APK1 and then I'd be set to update to Nougat, so that's exactly what I did.
After again flashing via the 4-file method with Odin, I set up the phone again so I was back at the home screen. I downloaded both the APK1 and the .zip file containing Nougat while my phone was charging (from 90%, my phone was at ~50% by the time I had Nougat up and running), and I placed the .zip Nougat update onto an SD card that I usually keep in the phone. Once APK1 was set up, I put the SD card back in, rebooted into Recovery Mode, and waited until the manual screen came up. Then I simply chose update from SD card, chose the .zip file I'd placed in there, and waited. After a while, I was greeted by a new setup screen. I set up Nougat and now it's running just fine.
The only issue I'm seeing is that I'm still not getting any OTA updates. I hope that doesn't continue, but if it does I can just update via .zip or something.
Thanks for reading!
where did you get the nougat.zip?
Hi
I got my wife a Samsung S8, SIM free as it was cheaper to buy the phone out right and get a 3 SIM only deal.
Only problem is because we got the phone from a online retailer, 3 won't activate the wifi calling.
So I have decided to flash the 3 S8 firmware via odin to my wife's phone but before I do that I have a few questions so I know I don't mess things up.
I will list the questions in number form so could you list the answers in number form with answer matching the question number, so I know what people are talking about.
1. When I glanced at Sammobile, I saw nothing mentioned about 3. Only thing I saw was H3G does this mean 3....if not what is 3 software listed as.
2. Will flashing this firmware wipe or factory reset her phone. (I know that I need to back things up anyway)
3. Will doing this Firmware flash void her insurance. As it's official Samsung software, I didn't think so but I want to be sure.
4. After the update will her phone be locked to 3.
5. Has anyone got any tips and guides which can help with this.
6. I hear that you can google blocked doing this type of thing, how do you get around getting blocked and if I do, how do I unblock a google blocked phones.
7. Will flashing 3 firmware actually give me wifi calling in the end.
8. After I have installed the firmware....will I receive future android/ Samsung updates. E.g. android 7 to android 8 updates, security patches and bug fixes
Thanks guys I will leave those questions for now....if I have anymore I will add them on another comment.
Hope you can help me I have attached some stuff I saw on the net incase it helps in anyway
Owenboy89 said:
Hi
I got my wife a Samsung S8, SIM free as it was cheaper to buy the phone out right and get a 3 SIM only deal.
Only problem is because we got the phone from a online retailer, 3 won't activate the wifi calling.
So I have decided to flash the 3 S8 firmware via odin to my wife's phone but before I do that I have a few questions so I know I don't mess things up.
I will list the questions in number form so could you list the answers in number form with answer matching the question number, so I know what people are talking about.
1. When I glanced at Sammobile, I saw nothing mentioned about 3. Only thing I saw was H3G does this mean 3....if not what is 3 software listed as.
2. Will flashing this firmware wipe or factory reset her phone. (I know that I need to back things up anyway)
3. Will doing this Firmware flash void her insurance. As it's official Samsung software, I didn't think so but I want to be sure.
4. After the update will her phone be locked to 3.
5. Has anyone got any tips and guides which can help with this.
6. I hear that you can google blocked doing this type of thing, how do you get around getting blocked and if I do, how do I unblock a google blocked phones.
7. Will flashing 3 firmware actually give me wifi calling in the end.
8. After I have installed the firmware....will I receive future android/ Samsung updates. E.g. android 7 to android 8 updates, security patches and bug fixes
Thanks guys I will leave those questions for now....if I have anymore I will add them on another comment.
Hope you can help me I have attached some stuff I saw on the net incase it helps in anyway
Click to expand...
Click to collapse
Firstly, there are Dozens and dozens of flash guides all over the web on flashing a SS phones with ODIN, 2nd'ly, its one of the easiest phones to flash..
Before you do anything download and install the latest SS USB drivers.. plug your phone in so they are detected.. then goto>settings and turn ON USB debugging in developer options.. plug in phone again.. so the device is detected again, then unplug... this installs the (A)ndroid (D) ebug (B)ridge driver, leave USB Debugging ON..
Your questions:,,
1) Yes H3G is 3UK... also EE use wifi calling..
2) Yes, it will wipe her phone... When you download your H3G firmware.. there are 2 CSC files in the folder.. I recommend using CSC... do not use HOME_CSC
3) No it will not void the warranty... its only when you trip KNOX by rooting, or custom roms that you invalidate warranty... Stock is fine
4) Yes it will... you will have to get an Unlock code to SIM unlock her phone.. SIM Unlock.. is not Flashing a rom.. What makes SS devices so cool.. is that you can flash any stock rom from any provider.. and it doesnt affect the bootloader, so you could flash an unbranded (open), EE or O2 rom on your 3 SIM locked phone..
5) Theres so many on the web and on XDA for SS phones and ODIN flashing, just type "Galaxy S8 back to stock" into search. My advice.. READ READ and more READ the guides ALL THE WAY Through, before you do ANYTHING AT ALL.. and make sure the phone you have has no SIM locks or security locks on it before you start.
6) Never heard of this... its only a stock rom your flashing, youll be fine
7) If 3 support Wifi Calling and the Rom your flashing has it coded in, then Yes it should work fine. EE also support Wifi calling
8) Yes... its a STOCK Rom with a STock recovery and STOCK Knox... so you will recieve updates according to when they are rolled out by that prvider... So, if its a 3 Rom, youll get updates when 3 push them out... if its an O2 rom, youll get them from O2.. and so on.... That is why soo many people flash Unbranded/Unlocked Open Roms... because unlocked phones have, in the past, gotten updates first and factory unlocked phones / roms dont come with Bloatware / carrier rubbish apps installed ..
Remember.. Just READ everything
Hope this helps
NightOrchid said:
Firstly, there are Dozens and dozens of flash guides all over the web on flashing a SS phones with ODIN, 2nd'ly, its one of the easiest phones to flash..
Before you do anything download and install the latest SS USB drivers.. plug your phone in so they are detected.. then goto>settings and turn ON USB debugging in developer options.. plug in phone again.. so the device is detected again, then unplug... this installs the (A)ndroid (D) ebug (B)ridge driver, leave USB Debugging ON..
Your questions:,,
1) Yes H3G is 3UK... also EE use wifi calling..
2) Yes, it will wipe her phone... When you download your H3G firmware.. there are 2 CSC files in the folder.. I recommend using CSC... do not use HOME_CSC
3) No it will not void the warranty... its only when you trip KNOX by rooting, or custom roms that you invalidate warranty... Stock is fine
4) Yes it will... you will have to get an Unlock code to SIM unlock her phone.. SIM Unlock.. is not Flashing a rom.. What makes SS devices so cool.. is that you can flash any stock rom from any provider.. and it doesnt affect the bootloader, so you could flash an unbranded (open), EE or O2 rom on your 3 SIM locked phone..
5) Theres so many on the web and on XDA for SS phones and ODIN flashing, just type "Galaxy S8 back to stock" into search. My advice.. READ READ and more READ the guides ALL THE WAY Through, before you do ANYTHING AT ALL.. and make sure the phone you have has no SIM locks or security locks on it before you start.
6) Never heard of this... its only a stock rom your flashing, youll be fine
7) If 3 support Wifi Calling and the Rom your flashing has it coded in, then Yes it should work fine. EE also support Wifi calling
8) Yes... its a STOCK Rom with a STock recovery and STOCK Knox... so you will recieve updates according to when they are rolled out by that prvider... So, if its a 3 Rom, youll get updates when 3 push them out... if its an O2 rom, youll get them from O2.. and so on.... That is why soo many people flash Unbranded/Unlocked Open Roms... because unlocked phones have, in the past, gotten updates first and factory unlocked phones / roms dont come with Bloatware / carrier rubbish apps installed ..
Remember.. Just READ everything
Hope this helps
Click to expand...
Click to collapse
Thank you so much. I will make sure to do my research. I have used odin before so I have some experience using the tool but not for big things like this. Last thing I used it for was to download TWRP to my rooted tablet.
I will also pull out her memory card so she can save her photo......she will be pissed about the wiping the phone part but if we want wifi calling then needs are a must.
Anyway of backing up her phone on a level where I can just put in her user name and password it will literally restore back to the point of the last back up....eg install all her the apps and themes the way she had them before the firmware update.
It's really important I nail this, as this is the first time we have gone SIM free and I don't want to be going back to paying extra for contracts just because we need the wifi calling. (And we both hate the three in touch app)....so my success with this will be important for the next phones we buy.
NightOrchid said:
Firstly, there are Dozens and dozens of flash guides all over the web on flashing a SS phones with ODIN, 2nd'ly, its one of the easiest phones to flash..
Before you do anything download and install the latest SS USB drivers.. plug your phone in so they are detected.. then goto>settings and turn ON USB debugging in developer options.. plug in phone again.. so the device is detected again, then unplug... this installs the (A)ndroid (D) ebug (B)ridge driver, leave USB Debugging ON..
Your questions:,,
1) Yes H3G is 3UK... also EE use wifi calling..
2) Yes, it will wipe her phone... When you download your H3G firmware.. there are 2 CSC files in the folder.. I recommend using CSC... do not use HOME_CSC
3) No it will not void the warranty... its only when you trip KNOX by rooting, or custom roms that you invalidate warranty... Stock is fine
4) Yes it will... you will have to get an Unlock code to SIM unlock her phone.. SIM Unlock.. is not Flashing a rom.. What makes SS devices so cool.. is that you can flash any stock rom from any provider.. and it doesnt affect the bootloader, so you could flash an unbranded (open), EE or O2 rom on your 3 SIM locked phone..
5) Theres so many on the web and on XDA for SS phones and ODIN flashing, just type "Galaxy S8 back to stock" into search. My advice.. READ READ and more READ the guides ALL THE WAY Through, before you do ANYTHING AT ALL.. and make sure the phone you have has no SIM locks or security locks on it before you start.
6) Never heard of this... its only a stock rom your flashing, youll be fine
7) If 3 support Wifi Calling and the Rom your flashing has it coded in, then Yes it should work fine. EE also support Wifi calling
8) Yes... its a STOCK Rom with a STock recovery and STOCK Knox... so you will recieve updates according to when they are rolled out by that prvider... So, if its a 3 Rom, youll get updates when 3 push them out... if its an O2 rom, youll get them from O2.. and so on.... That is why soo many people flash Unbranded/Unlocked Open Roms... because unlocked phones have, in the past, gotten updates first and factory unlocked phones / roms dont come with Bloatware / carrier rubbish apps installed ..
Remember.. Just READ everything
Hope this helps
Click to expand...
Click to collapse
Hi....i seem of got myself in a pickle.
I read countless amounts of guides and watch loads of videos but still not gone right. (Phone isn't broken thankfully)
Basically I do everything guides tell me, but it's when I press start on odin the problem happens. It doesn't fail but it doesn't progress....on the text box it stops at a point that says Nand START (something like that) but doesn't get past that point....i sat for an hour the first time I tried it and 30 mins every time after that. Another thing it does is at the top where you get the green loading bar....that part goes white and says something like select Partition (not near my pc at the mo and when I was with the pc my wife had my phone, so couldn't take a photo)
I have 3 solutions that could be causing the problem but I just want to get a second opinion.
1. I read everywhere about device drivers and I was under the impression that they downloaded automatically when I plugged the phone to the pc....is there secondary drivers I need to download (sorry for the basic question)
2. My odin wasn't the latest version....i was using odin 3.09 and now there is odin 3.13 (I think) will using the latest version stop this problem.
3. I wonder if my antivirus is blocking it....do antivirus's ever get in the way of flashing firmware.
Hope some can help before tonight
Owenboy89 said:
Hi....i seem of got myself in a pickle.
I read countless amounts of guides and watch loads of videos but still not gone right. (Phone isn't broken thankfully)
Basically I do everything guides tell me, but it's when I press start on odin the problem happens. It doesn't fail but it doesn't progress....on the text box it stops at a point that says Nand START (something like that) but doesn't get past that point....i sat for an hour the first time I tried it and 30 mins every time after that. Another thing it does is at the top where you get the green loading bar....that part goes white and says something like select Partition (not near my pc at the mo and when I was with the pc my wife had my phone, so couldn't take a photo)
I have 3 solutions that could be causing the problem but I just want to get a second opinion.
1. I read everywhere about device drivers and I was under the impression that they downloaded automatically when I plugged the phone to the pc....is there secondary drivers I need to download (sorry for the basic question)
2. My odin wasn't the latest version....i was using odin 3.09 and now there is odin 3.13 (I think) will using the latest version stop this problem.
3. I wonder if my antivirus is blocking it....do antivirus's ever get in the way of flashing firmware.
Hope some can help before tonight
Click to expand...
Click to collapse
Hi again everyone.
I feel like I am talking to myself here. I have managed to sort it.
I downloaded some secondary device drivers for her phone and then update odin to, Odin v3.12.7 and it worked first time.
I also used the original charging cable instead of the official charging cable for the gear 360 camera.
To restore her data, I backed up to samsung cloud in the settings, signed her in and restored the date I backed up....didn't originally think it would be any good but I am impressed.
Result is I have a phone that has wifi calling and I read somewhere that if you take the SIM out of your phone when you download the firmware it doesn't SIM lock the phone.....and it seems to have worked. (Not sure how true it is or if I was just lucky)
Hope this thread helps, I want to cover a few different things in it and learn something on the way.
(Thanks to the person that commented and supplied most of the info in this thread)
#happywifehappylife
Hi everyone.......again.
My last post I promise.
I wrote a bit of a guide for myself for when I need to do this again. I thought would post it here so people can see it and use it if they wish.
(The notes before the method is apart of my guide. Hope it all helps)
Notes Before The Method
the cable you are using to connect to the pc should be the original charging cable. (If you don't have the original then use the one your using and see if it works but try to find a official Samsung charging cable)
Your phone needs to be at least at 60% battery.
Older phones sometimes don't work with newer versions of Odin so if this is happening download a older version.
If it's a new phone and you want to personalize it from scratch then no need to back up and restore any data.
After removing your memory card, plug it into your computer using a memory card extension and copy photos to your computer. Just in case the phone formats the memory card when entered back in to the phone, after the firmware is installed.
Method
1. Go to Sammobile via Google chrome in incognito mode. (If you don't do this they will re-direct you to a sign up page, everytime you press download)
2. Download Firmware, find this by picking the lastest firmware thats with your network and match the Baseband version or the last part of build number. (found in system info in the settings)
3. Install the latest version of Odin and install secondary device drivers on your pc/Laptop.
4. (On your mobile) back up your data in the samsung cloud.
Setting>Cloud and Accounts>Samsung Cloud>Backup settings> Back up.
If you have a memory card, move all your photos ect, to it and remove it from your phone.
5. Go into setting and tap build number 7 times to unlock developer options. After unlocking it, enter developer options and enable usb debugging.
Setting>developer options>USB Debugging.
6. Once the firmware file has stopped downloading on your pc extract it and send send it to your Downloads File.
7. Open Odin and load each part of firmware in the right box e.g. AP with AP, BL with BL, CSC with CSC ect (Do not load up Home CSC this is used for when your moving a branded device to another brand, E.g. EE to 3)
8. Before you plug your phone up to the computer. Turn your phone off and enter Odin mode(Download mode). Each device has a different way of doing this so just google how to do it on your specific device.
9. Once your phone is in download mode plug it into the computer and press start. This should take a few minutes but some files may take longer.
10. Once the Odin confirms the process is done, by showing the pass sign unplug your phone and turn it on. (First time you turn it on May take a minute or two to load. )
11. Enter your google email and password, and restore all your data on google.
12. Then enter your Samsung user and password, after that press restore and choose the date you backed up on before you flashed your phone (at point 4)
13. Enjoy....your all done.