I bought this phone in version: G965F with system version: Android 9.
I waited for my phone to get an update to Android 10 like everyone else but saw that the update was not coming.
After in-depth testing, I checked the IMEI number on a particular site and saw that my device details were not as mentioned above.
To my surprise, I discovered that my device's version is basically a G965U.
Long story short:
I downloaded an operating system that is compatible with a device version according to IMEI The installation was successfully performed through Odin.
After the phone was switched on I saw that the language of the device is divided into two Hebrew and English.
first question:
How does it make sense after the operating system update model number changed from G965F to G965U?
second question:
How does that make any sense in a non-hackable G965U model?
Third and most important question:
How do I fix the language problem? I can't choose the Hebrew language because it's not there.
Note:
This whole story happened after trying to install a G965F ROM and of course without success.
After all the failures, I tried to figure out why I couldn't install the ROM and then checked the IMEI number which, to my surprise, revealed to me that my phone was G965U.
Once I realized this, I decided to install the newest version compatible with my phone model and unfortunately I discovered the newest version not have my native language (Hebrew)
Another note that is important to mention is that my phone has been much slower since the update.
PLEASE HELP ME TO SOLVE THIS ISSUE.
If anyone has a solution I would love and thank him very much.
I uploaded a screenshot of the phone version according to IMEI:
{
"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"
}
That's is my current details :
Regards,
Liran
Related
Hello Team,
I recently purchased a new Samsung Galaxy J5 (2016) few days back. After the initial settings, I got a new ROM OTA update. However, I being a true Android lover tried Rooting my J5 (2016). However, the link that I used did not worked and now my Device status has changed from 'Official' to 'Custom'.
EDIT - The above Issue has been Resolved since I flashed STOCK ROM that changed my Device Status back to "Official". However, a new issue has been cropped up now.
You can take a look at the current Software Info. that would give you an insight onto the current OS that is installed on the device after the flashing of STOCK ROM which I downloaded from Sam Mobiles.
{
"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"
}
and this:
Here is another screenshot that tells you the exact error which I receive now whenever I try looking for Software Updates manually.
I want to know what could be the issue here since earlier the Device Status changed to CUSTOM (when I tried rooting the device). However, when I downloaded the STOCK ROM from SAM MOBILES and flashed it properly through ODIN, this is the new error that is troubling me.
NOTE: After flashing the STOCK ROM, I did not perform any kind of: Data Wipe or Cache Wipe.
Can that be creating this error here? I don't think just because I did not Clean Wiped my Cache and Data could be the reason behind this issue. However, still I am looking forward to hearing some response from the official developers on this.
Thanks and regards.
Manu Mathur
(XDA-member)
{
"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"
}
the best program for CUBOT_X19 imei repair
The problem was solved by the program SP_Meta_v9.1724.0.00.zip
Instructions :
How to use Maui Meta to Write or Repair IMEIuse CUBOT_X19_9021C_1_V07_20190612 / database /MDDB_InfoCustomAppSrcP_MT6763_S00_MOLY_LR12A_R2_MP _V74_15_1_ulwtg_n.EDB
Or file : .EDB Of any Stock rom firmware/CUBOT X19
CUBOT_X19_9021C_1_V08_20190627 android 9.0
CUBOT_X19_9021C_1_V07_20190612 android 9.0
CUBOT_X19_9021C_2_V02_20190802 android 9.0 specific US version
NEXT
[GUIDE] CUBOT X19
Do you happen to have a copy of the CUBOT_X19_9021C_1_V07_20190612 rom? That version's link is broken in CUBOT's support page and my phone's camera won't work with versions 08 and 12. Rooting didn't go that well for me.
Thanks in advance.
Voidbert said:
Do you happen to have a copy of the CUBOT_X19_9021C_1_V07_20190612 rom? That version's link is broken in CUBOT's support page and my phone's camera won't work with versions 08 and 12. Rooting didn't go that well for me.
Thanks in advance.
Click to expand...
Click to collapse
Greetings. I will try my best to find an alternative link.(CUBOT_X19_9021C_1_V07_20190612). I just let you know that my internet speed is slow unfortunately. Otherwise, I would have responded to your request immediately.
An alternate link has been provided
Download hidden settings. Scroll to the bottom. Second last option click save then click the last option to write it
Hello, U12+ Korean user with the lowest number of users in the world. First of all, it's nice to meet
I modified Qualcomm efs files related to volte, modified buildprops, and entered forced commands. Ims is activated. I'm wondering what else I need.
(I'm sorry that the screenshot is not in English) ims registered, and it says that video calling is possible, but volte is impossible.
{
"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"
}
Previously, it was possible to replace the Qualcomm efs file in original ROM and create the carrier code xml in system-customize-MNS through the volte activation menu in the basic phone app.
For reference, htc was withdrawn from the Korean market 10 years ago. I purchased the Taiwan version and copied the Qualcomm ims files of the Korean telecommunication company from Sony Xperia xz2 firmware, the same Snapdragon 845 model released in Korea, and opened the forced port through the adb shell command. After replacing the file in efs explorer, I made a Korean carrier (45008etc.xml) in the mns folder by looking at the Taiwanese carrier code and getting a hint, and also modified mns.map.xml in the customize folder, so volte in the original phone app-config The activation menu appears, so even though it is not released to Korean users, we applied tta .volte, which is only available in Korea.
Hey Guys !
It's been a long time since I left Android mods and a lot has changed since 2015
I managed to lost both the IMEI from my cousin Samsung A12(dual SIM) after tried this guide https://forum.xda-developers.com/t/installing-twrp-and-linageos.4334465/ .
The fault it's on me and not on the guide, I lost the backup file.
I managed to get until the last step before flash the Lineage OS from ADB Sideload.
I format everything and then i couldn't make a connection with the ADB sideload and tried to get back to stock firmware with ODIN.
After flash the firmware i lost both IMEI.
Things I tried :
~ Clean install with ODIN (from the guide)
~Tried to change the IMEI with different apps with root
~Right now I'm trying to install every possible ROM from this site https://samfw.com/firmware/SM-A125F/COS
{
"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"
}
All replies are welcome !
Best regards,
Leon
I thought MediaTek will change but its still the same pain in the ...
EDIT
I managed to get back both IMEI with this version, A125FXXU1AUC3 .
Just to help any other with the same problem.
Best regards,
Leon
Deleted but another alternatives is the downgrade or flash android 10 CP with the last update (This only works with binary 1 firmwares)
In my opinion is so stupid this bug/error and I tink the Knox 0x1 affects this problem (All firmwares with no imei problem has the secured by Knox splash) but is my opinion
I tried for the first time flashing on of my devices. Samsung supported the tablet until Android version 5 and now I tried to load Lineage OS 18.1 Android 11. I used Odin and TWRP. It was fine only Google services didn't work (tried OpenGapps, NikGapps and they loaded fine but no Google apps worked on the device) so I tried to flash it back to stock. I didn't have a backup, so I went online and downloaded from sfirmware a firmware from Argentina, which is not my region, was fine but WIFI didn't work. Then flashed a Romanian (my region) firmware from samfw.com but it is a weirdo developer version on Android 4.4.2 with a changed bootloader.
{
"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"
}
My concern now is that I can't load TWRP anymore onto the tablet Odin stuck on SetupConnection, the cable is good, Developer Options are enabled. I would like to wipe the tablet and download the stock Android 5 or any other Android that would work well with 1.5gb of ram.
I assume you went through all 78 pages of the help subforum for your device and didn't find the solution ?
Galaxy Tab 4 Q&A, Help & Troubleshooting
This forum is for all of your questions about the Samsung Galaxy Tab 4. If you need help troubleshooting a problem, please be as specific as possible by describing your software configuration, including the ROM, kernel, and any modifications you've done.
forum.xda-developers.com
Not really, as I said the twrp version I am using doesn't want work on the device anymore and I just want to wipe it for now so I can flash normal Android to it.
EDIT A helpful user on that forum said that in 4.2.2 the button combinations were different for some reason, now I'm inside twrp.