A friend's S7 is stuck on Android 7.0 but they brought it to me because their wife has the same phone but it upgraded to Android 8.0. Despite reboot, and factory data reset, when I press System update nothing happens, there is no UI response at all.
There has been some confusion over over which firmware to use as when I have provided screenshots as different people have told me because I am in Ireland I should use XEU, others have told me I should use INS or something else. The about device menu, the download firmware upload screen, the CSC dial code, and the Phone Info app all report the phone is a different model. Please see the different models and device information observed below.
SM-G930F observed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Initially based on this with Odin I tried flasing https://samfw.com/firmware/SM-G930F/XEU/G930FXXU8ETI2 :
Looking at Odin it seemed to work, but I read on successful flash a new reset button should appear where the green pass box is displayed but at the end this just appeared for a split second before reverting to the green pass box, before the phone restarted itself. On checking nothing has changed, still Android 7.0, despite reboot, and trying to flash again.
On further investigation, apparently the CSC that's an Indian dual sim SM-G930FD:
But this is a single SIM model:
SM-G930P observed:
I tried the same firmware again, this time using the CSC file instead of CSC home:
Phone Info app screenshots, SM-G930V observed:
The main purpose of trying to upgrade is to enable the owner to link a heart rate monitor watch device to it with Bluetooth which required 8.0, as to alert them to any heart abnormalities. Due to this, I would rather not use any custom ROM and only stock.
Is there a stock version firmware that will work with this device, and are there any higher than normal risks involved with flashing it with Odin? It was mentioned to me that because the device is an apparent refurb the risks are 50/50, and I would rather make the owner aware of this before flashing if that is the case.
CPU-Z:
I might be able to help you,
Is the phone model SM-G930F or SM-G930/A/P/V/some other kind of USA variant?
Can you show a picture of the device in stock recovery mode as-well as a picture OEM unlock in the developer menu?
The phone seems to display multiple times, the Snapdragon variant of the S7.
The phone also seems to show the bootloader and the baseband/modem, as G930P, the Sprint version of the S7,
the build version/PDA, and the CSC shows G930V, meaning the Verizon version of the S7. These two models probably shows that the S7 used to be a Snapdragon S7, not the Exynos version (G930F)
You said the phone is a apparent refurb, right?
The only reason I could think of why Odin somehow flashed SM-G930F firmware is that it probably has some kind of USA/Snapdragon variant of the S7 logic board and has the rest of the part with the model SM-G930F.
Not sure yet, but you may want to try flashing a USA variant of the S7 firmware.
Alternativly, if it is overruled that the phone is not a Snapdragon S7, you may choose to use this custom ROM/firmware. Everything works as it is just regular stock ROM (android oreo 8).
Things you can try:
Flash the latest Nougat firmware, then flash Oreo.
Flash the firmware in separate (eg. Bootloader only, CP only, ...)
Flash the latest recovery (extract it from the firmware) and wipe the phone with it, then head to the updated Bootloader (that you flashed separately) and try flashing again.
Use custom stock ROMs, if all you need is just Samsung Health, otherwise, even AOSP ROMs can make the deal.
Flash an earlier version of Oreo.
It doesn't matter a lot if the phone is refurbished or not, you only write to the motherboard, so knowing what chip and model your motherboard have is the only pillar you need.
Related
I broke my Z3 and got a replacement a few days ago.
After I flashed pre-rooted 23.4.A.0.546, linked here, the he replacement shows the dreaded Invalid Card. Emergency calls only:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I never tested the device, I went directly for the root, ZX discovery and pre-rooted flash.
As quick explanation:
I got the device.
I never inserted a SIM, I immediately followed the instruction to root a Z3 with a locked BL:
- downgraded phone with D6603_23.0.A.2.93 ftf linked here.
- ran giofroot exploit. used v3.1. had to run it twice.
- mounted /system rw with ES Explorer.
- installed Z3 Dualrecovery for locked BL.
- then flashed 23.4.A.0.546 linked here.
Phone turned on without a hitch.
When I placed the SIM, I noticed the Invalid Card notice.
Tried (and failed) attempts:
Since then, I've rolled back to D6603_23.0.A.2.93.
Installed PC Companion (eeew) and done a system repair.
Downloaded the latest firmware from xperifirm for Telcel's branded ROM.
nothing. device still says Invalid Card.
a few screenshots that might help someone get a better understanding of what happened;
can anyone confirm if I have a SIM-locked device or if I flashed the wrong firmware?
How can I roll back? what measurements can I take to better understand the problem?
Hobbess2099 said:
I broke my Z3 and got a replacement a few days ago.
After I flashed pre-rooted 23.4.A.0.546, linked here, the he replacement shows the dreaded Invalid Card. Emergency calls only:
I never tested the device, I went directly for the root, ZX discovery and pre-rooted flash.
As quick explanation:
I got the device.
I never inserted a SIM, I immediately followed the instruction to root a Z3 with a locked BL:
- downgraded phone with D6603_23.0.A.2.93 ftf linked here.
- ran giofroot exploit. used v3.1. had to run it twice.
- mounted /system rw with ES Explorer.
- installed Z3 Dualrecovery for locked BL.
- then flashed 23.4.A.0.546 linked here.
Phone turned on without a hitch.
When I placed the SIM, I noticed the Invalid Card notice.
Tried (and failed) attempts:
Since then, I've rolled back to D6603_23.0.A.2.93.
Installed PC Companion (eeew) and done a system repair.
Downloaded the latest firmware from xperifirm for Telcel's branded ROM.
nothing. device still says Invalid Card.
a few screenshots that might help someone get a better understanding of what happened;
can anyone confirm if I have a SIM-locked device or if I flashed the wrong firmware?
How can I roll back? what measurements can I take to better understand the problem?
Click to expand...
Click to collapse
Maybe this is important; when I downgraded the first time, I checked the following exemptions:
- KERNEL
- FOTA
- BASEBAND
Hobbess2099 said:
Maybe this is important; when I downgraded the first time, I checked the following exemptions:
- KERNEL
- FOTA
- BASEBAND
Click to expand...
Click to collapse
You did it wrong. NEVER check to exclude FOTA BASEBAND AND KERNEL.
baseband is what controls the radio (network) and it is very important. Flash again properly and don't check anything in exclude, but ALL in WIPE. In downgrade you MUST wipe everything.
Sent from my D6603 using Tapatalk
Thanks.
Is there a way to know which carrier is locking the device? Besides trying Sims from each carrier, I mean.
Sent from my SGP611 using Tapatalk
Hobbes2099 said:
Thanks.
Is there a way to know which carrier is locking the device? Besides trying Sims from each carrier, I mean.
Sent from my SGP611 using Tapatalk
Click to expand...
Click to collapse
No, but it is not probable that it is simlocked. It is almost 100% because you have wrong Baseband / Firmware combination. The older firmware (downgraded) does not support newer baseband you left in the device unflashed.
so I tried two different flashes including FOTA, BB and Kernel;
- D6603_23.0.A.2.93 from the original OP.
- latest firmware from xperifirm for Telcel's branded ROM; 23.4.A.0.546
in both cases, i left the entire Exception section unticked.
in both cases, after initual bootup, I still get the "Invalid Card." warning.
I'd like to start discarding possibilities.
- can flashing affect SIM lock? either way, locking or unlocking devices? My understanding is that it shouldn't. Could someone please confirm?
- is there a way with which carrier the devices is locked? The screenshot shows a [X] on network lock with a 5.
is there a way to find out that does not involve getting SIMs from every carrier?
Hobbes2099 said:
so I tried two different flashes including FOTA, BB and Kernel;
- D6603_23.0.A.2.93 from the original OP.
- latest firmware from xperifirm for Telcel's branded ROM; 23.4.A.0.546
in both cases, i left the entire Exception section unticked.
in both cases, after initual bootup, I still get the "Invalid Card." warning.
I'd like to start discarding possibilities.
- can flashing affect SIM lock? either way, locking or unlocking devices? My understanding is that it shouldn't. Could someone please confirm?
- is there a way with which carrier the devices is locked? The screenshot shows a [X] on network lock with a 5.
is there a way to find out that does not involve getting SIMs from every carrier?
Click to expand...
Click to collapse
Flash only firmware from XperiFirm. Others of unknown origin can be provider specific. However, the SIM LOCK is firmware independent.
I omitted some of your pictures. The X mark on Network means that is IS provider LOCKED and you have 5 retries to enter unlock code.
I am a pretty decent android er. But damn, I got in trouble with my unlocked s7, flashing the new superman 1.5. I used the att csc option in aroma, and I had no SIM service. Nor imei, I tried to go back to 1.4.1 with corresponding BL, nothing, so I odin'd a stock package, and I did take, but still, everything SIM related or 5 ghz WiFi is down, since I've already dl'ed and installed a stock package from sammobile, what else are my options? Thanks a lot for anyhelp, I read that w other guys had a similar issue until it was noted that the att and tmo cscs were incompatible.
This is similiar to the problem I had. The CSCs for ATT and TMB (possibly sprint and Verizon if they exist) are bad. They are designed for a qualcomm device. T-mobile also uses a custom ims profile for their wifi/volte that has not been ported in the S6 or Note5 to international models even though they share the same chipset. - this may be cause for a bounty.
What I did after having this issue was reinstall the rom after a wipe, choosing a non-US carrier (the default one, for instance). It worked fine afterwards.
rp3 said:
This is similiar to the problem I had. The CSCs for ATT and TMB (possibly sprint and Verizon if they exist) are bad. They are designed for a qualcomm device. T-mobile also uses a custom ims profile for their wifi/volte that has not been ported in the S6 or Note5 to international models even though they share the same chipset. - this may be cause for a bounty.
What I did after having this issue was reinstall the rom after a wipe, choosing a non-US carrier (the default one, for instance). It worked fine afterwards.
Click to expand...
Click to collapse
That was my first instinct but everything I flash doesn't help, reflashing 1.5 and choosing sweeden, Nordic or Australian is the same, same with 1.4.1, and I reflashed a sock OS via Odin and still nothing, and then I refreshed twrp and redid 1.5 and still! Which has me worried
Did you wipe first? Also, are you using a 930f or a 930FD. If FD, there could be other problems.
rp3 said:
Did you wipe first? Also, are you using a 930f or a 930FD. If FD, there could be other problems.
Click to expand...
Click to collapse
Yeah, i mean i have to do a wipe to go from encrypted to un encrypted, I also only have the single sim. But i mean anyways, i def am solid on flashings and full wipes and stuff, I mean doing a stock OS through odin would def fix this normally, I can figured what little poison this superman left behind that isnt getting reset after flashes and wipes
I'm having the same issue. I have the FD (SM-G930FZSUXSG) I'm trying to find a factory image but am having no luck so far. I'll be keeping an eye on this thread to see if you get it resolved.
zombicidal maniac said:
I'm having the same issue. I have the FD (SM-G930FZSUXSG) I'm trying to find a factory image but am having no luck so far. I'll be keeping an eye on this thread to see if you get it resolved.
Click to expand...
Click to collapse
doing a little more research, i wonder if i didnt lose my IMEI somehow, it looks like the same symptoms
All the different firmware I've been flashing lets it boot into android but the Baseband only shows unknown. I don't know for sure which one would be the correct version for the model I have
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit- After more searching it seems my model is the United Arab Emirates model. Now I just have to figure out which firmware is the correct for that model and hope I can fix it with that but who knows.
zombicidal maniac said:
All the different firmware I've been flashing lets it boot into android but the Baseband only shows unknown. I don't know for sure which one would be the correct version for the model I have
Edit- After more searching it seems my model is the United Arab Emirates model. Now I just have to figure out which firmware is the correct for that model and hope I can fix it with that but who knows.
Click to expand...
Click to collapse
So you have the same issue?
Yes. Everything was good when I got the phone new but now I need to find the factory firmware but so far no luck.
Warning: This guide requires unlocking the bootloader, which will void your warranty.
Confirmed working for T-Mobile/MetroPCS. I welcome other XT1548 users to try this process for themselves.
1) Unlock the bootloader, install a recovery, and root the device. Follow instructions in this forum already as other people have made much higher quality guides than I could make.
2) Perform the tutorial located here to flash XT1540 modem and associated files: http://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362
3) Flash the latest version of CM13: https://download.cyanogenmod.org/?device=osprey
4) Install GApps/all other necessary apps for CM13
5) Dial *#*#4636#*#* to switch to LTE/GSM (auto) mode
6) Enter the correct APN for your carrier
7) Enjoy your GSM unlocked device!
Few remarks: it may not be needed to flash the XT1540 files. It seems like the block is only on US Cellular's software. But I'm leaving the step added in as it is what worked for me. Any suggestions for polishing the tutorial would be appreciated.
A few photos: (note that this was done on an active SIM, but without paid for service. 611 works correctly, as does the T-Mobile/MetroPCS portal).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dwegiel said:
Warning: This guide requires unlocking the bootloader, which will void your warranty.
Confirmed working for T-Mobile/MetroPCS. I welcome other XT1548 users to try this process for themselves.
1) Unlock the bootloader, install a recovery, and root the device. Follow instructions in this forum already as other people have made much higher quality guides than I could make.
2) Perform the tutorial located here to flash XT1540 modem and associated files: http://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362
3) Flash the latest version of CM13: https://download.cyanogenmod.org/?device=osprey
4) Install GApps/all other necessary apps for CM13
5) Dial *#*#4636#*#* to switch to LTE/GSM (auto) mode
6) Enter the correct APN for your carrier
7) Enjoy your GSM unlocked device!
Few remarks: it may not be needed to flash the XT1540 files. It seems like the block is only on US Cellular's software. But I'm leaving the step added in as it is what worked for me. Any suggestions for polishing the tutorial would be appreciated.
A few photos: (note that this was done on an active SIM, but without paid for service. 611 works correctly, as does the T-Mobile/MetroPCS portal).
Click to expand...
Click to collapse
You did a whole ton of extra work. The USC Motorola phones are factory unlocked so any rom (even stock) would work out of the box. It's only the Sprint/Virgin Moto phones are are locked.
purplefruity said:
You did a whole ton of extra work. The USC Motorola phones are factory unlocked so any rom (even stock) would work out of the box. It's only the Sprint/Virgin Moto phones are are locked.
Click to expand...
Click to collapse
Wrong, by default the XT1548 only gets LTE signal. Even setting/forcing GSM on in the testing menu does not allow it to get service for talk/text on T-Mobile.
dwegiel said:
Wrong, by default the XT1548 only gets LTE signal. Even setting/forcing GSM on in the testing menu does not allow it to get service for talk/text on T-Mobile.
Click to expand...
Click to collapse
Thats weird. The best I can get for GSM on my Sprint variant is International sim. For the international sim, it works without any issues on stock rom. USC might be a little different.
Is there any type of updated guide for this because I have the XT1548 and I have had no luck with unlocking it. Any tips would be extremely useful.
I'll try to be as succinct as I can:
1. Bought phone from eBay UK which claimed to be the International version.
2. Got prompted on phone to update OTA to Android 7.0 a few months later.
3. Attempts to install update failed - error message as below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Contacted HTC UK (as phone was still under warranty at the time) for help and they said to return the phone to them to sort it.
5. HTC then emailed me back to say it couldn't be returned for servicing as IMEI shows phone is actually an AT&T device.
6. They advised that I should flash the official AT&T RUU for Android 6.0 then update from there, and I should contact Support at HTC USA for assistance.
7. I went to the website, found and downloaded the correct RUU but then it occurred to me that whatever the modifications are that were made to my phone, they do allow me to use any sim in the UK. Flashing the official AT&T RUU might render my phone incapable of making and receiving calls in this country.
8. I emailed HTC USA for advice about what to do but they're not replying so IDK what to do
Can anyone help please?
Will flashing the official AT&T RUU render my phone pretty useless in the UK?
Thanks!
Is there not a single person here who can answer my question please?
Blandroid said:
I'll try to be as succinct as I can:
1. Bought phone from eBay UK which claimed to be the International version.
2. Got prompted on phone to update OTA to Android 7.0 a few months later.
3. Attempts to install update failed - error message as below:
4. Contacted HTC UK (as phone was still under warranty at the time) for help and they said to return the phone to them to sort it.
5. HTC then emailed me back to say it couldn't be returned for servicing as IMEI shows phone is actually an AT&T device.
6. They advised that I should flash the official AT&T RUU for Android 6.0 then update from there, and I should contact Support at HTC USA for assistance.
7. I went to the website, found and downloaded the correct RUU but then it occurred to me that whatever the modifications are that were made to my phone, they do allow me to use any sim in the UK. Flashing the official AT&T RUU might render my phone incapable of making and receiving calls in this country.
8. I emailed HTC USA for advice about what to do but they're not replying so IDK what to do
Can anyone help please?
Will flashing the official AT&T RUU render my phone pretty useless in the UK?
Thanks!
Click to expand...
Click to collapse
"Variant system version" is the error you'll get when trying to update a phone that was improperly converted from a carrier version to another.
What the previous owner probably did is replacing the software on the phone without changing the phone CID and MID values to match the new software version.
The CID is a number tied to your region/phone operator (i.e at&t CID is CWS__001, International CID is HTC__001)
The MID is the number identifying your hardware (different variant of the A9 will have different MID) For example the gsm variant is 2PQ912000 and the Sprint cmda variant is 2PQ930000.
When updating the software, the phone will check if the downloaded update version match the CID and MID expected for that version and if not, it will give you this error.
So you either need to write the correct CID and MID in your phone (best option imo) or flash back the original at&t software.
Btw the at&t variant never got the update to lollipop so it's a little funny that htc tech support said to " flash the official AT&T RUU for Android 6.0 then update from there" cause there is no update at all :laugh:
The correct CID and MID for a phone running software x.xx.401.x is HTC__001 and 2PQ910000.
What is your current version-main, cid and mid? Use these commands:
Code:
fastboot getvar version-main
fastboot getvar cid
fastboot getvar mid
is you rphone s-off?
Code:
fastboot getvar security
So I wanted to try something so I flashed the Brazil ROM. tried to flash back to XEO but now in the settings it says "SER/SER,SER/XEO" and when resetting installs Russian bloatware. What can I do to restore the XEO ROM?
Dis you do a factory reset?
physwizz said:
Dis you do a factory reset?
Click to expand...
Click to collapse
yeah i did but its still stuck with ser csc
Flash stock ROM
@Malware said:
Flash stock ROM
Click to expand...
Click to collapse
did that many times but it still didn't change but for now im okay with it just disabled updates so i wont get stuck with russia rom without an option of downgrading via alliance shield x and it works fine
hxudsh said:
did that many times but it still didn't change but for now im okay with it just disabled updates so i wont get stuck with russia rom without an option of downgrading via alliance shield x and it works fine
Click to expand...
Click to collapse
That is weird. Full Brazilian stock firmware set? AP, BL, CP and CSC_OMC_ODM? Once the device is restarted after flashing get into the recovery straight away (hold power + volume up with the USB cable connected to PC). Don't let it boot Android! In the recovery do Factory Reset, format the data partition (if it's possible in the stock recovery, I don't remember) and wipe all the caches and only then boot the system. Also try removing the SIM card before flashing and also do the first boot of Android without SIM (although it shouldn't matter but who knows).
uluruman said:
That is weird. Full Brazilian stock firmware set? AP, BL, CP and CSC_OMC_ODM? Once the device is restarted after flashing get into the recovery straight away (hold power + volume up with the USB cable connected to PC). Don't let it boot Android! In the recovery do Factory Reset, format the data partition (if it's possible in the stock recovery, I don't remember) and wipe all the caches and only then boot the system. Also try removing the SIM card before flashing and also do the first boot of Android without SIM (although it shouldn't matter but who knows).
Click to expand...
Click to collapse
yeah it was the full set but it also didnt fix it but im fine with it unless as my sim card and mobile data will stop working but currently even volte is working so im fine with it
hxudsh said:
yeah it was the full set but it also didnt fix it but im fine with it unless as my sim card and mobile data will stop working but currently even volte is working so im fine with it
Click to expand...
Click to collapse
I remember that when I did disassembling of the Prism partition of different country versions I've discovered that most of the European firmwares contain the full set of Russian bloatware. In fact, all the firmwares with the size of more than 5 GB are all nearly identical in regards of bloatware included. So I can suggest you to temporarily install a Nepal or Papua New Guinea firmware, do the factory reset with it, go fully through the setup process, and then try again to flash the Brazilian version. It may help. Or you can stay with the Nepalese firmware, it's quite minimalistic and includes Samsung Pay (if you need it).
uluruman said:
I remember that when I did disassembling of the Prism partition of different country versions I've discovered that most of the European firmwares contain the full set of Russian bloatware. In fact, all the firmwares with the size of more than 5 GB are all nearly identical in regards of bloatware included. So I can suggest you to temporarily install a Nepal or Papua New Guinea firmware, do the factory reset with it, go fully through the setup process, and then try again to flash the Brazilian version. It may help. Or you can stay with the Nepalese firmware, it's quite minimalistic and includes Samsung Pay (if you need it).
Click to expand...
Click to collapse
ok but the m127f model doesnt have a nepal or papua new guinea firmware
Try Bolivia: https://samfw.com/firmware/SM-M127F/BVO
The general rule of thumb is the smaller firmware is the less bloated it is. Also prefer firmware for the poor and commercially unpromising countries, the so-called "3rd world".
sorry for reviving this thread but is there a way to get lte back? all i want is "good" mobile data and lte works good on my huawei, so can i get it back on my samsung without somehow changing the csc? (the carrier i use is Play in Poland)
after around 8 months, today i finally got my lte back via the samfw frp tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}