Didn't see a thread, but I just checked the Members app and saw the OneUI 3.0 beta registration was finally on there for G975U1. Registered and am downloading now.
{
"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"
}
Links:
BETA 1 - Android 10 ETJ3 -> ZTKI Update.zip link ( courtesy of @GreenDinoXD )
BETA 2 - ZTKI -> ZTL9 Update.zip link ( courtesy of @GreenDinoXD )
Rename .bin file to update.zip
Follow installation instructions from this thread:
Kapitein187 said:
ADB-method:
1. Download SDK platform tools from here https://developer.android.com/studio/releases/platform-tools
2. Extract them on your desktop.
3. Inside the extracted folder put the update.zip
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown the phone.
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (you scroll down using the volume buttons and select using the power button).
8. Connect the phone to the PC using original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
Click to expand...
Click to collapse
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
rikipy said:
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
Click to expand...
Click to collapse
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
Just redownload it.
Hello, please post update.zip file
please do you have the update.zip file , please share the link
is it for snapdragon?
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Ackeem.Salmon said:
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Click to expand...
Click to collapse
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
okay please if you hear any please let me know .. and thanks so much am grateful
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
PlutoDelic said:
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
Click to expand...
Click to collapse
Looks like the build date is November 30...
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
jeston said:
Looks like the build date is November 30...
Click to expand...
Click to collapse
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
jeston said:
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
Click to expand...
Click to collapse
There are quite a few on reddit, but no one sniffed the package. Bummer.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
yes its still posible and me on insta: Mateuzs_95 so i can help you with the steps:
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
I actually get updates my latest being last month.
PlutoDelic said:
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
There are quite a few on reddit, but no one sniffed the package. Bummer.
Click to expand...
Click to collapse
I guess they were quite hasty so nobody thought about grabbing the update
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Ackeem.Salmon said:
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Click to expand...
Click to collapse
the guy that created this post can do it right know but i don't know if he want to do it. i can help him but he needs to contact me so i can tell him the steps
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
GreenDinoXD said:
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
Click to expand...
Click to collapse
Can anybody confirm that's the correct update.zip before I include the link in the OP?
Related
A new approach!
Spoof the firmware version on the device, to trick Kies2.0.
But as you might understand, messing with system files is always dangerous and the possibility for a brick is always present. Hopefully this will not occur I'm doing my best to avoid that.
You should not use this app if you cannot get into Recovery and/or Download mode! (3 button combo) As always when you modifies system files!
Remember to disable any lagfix before updating!
For everyones safety I would recommend doing a manual backup of /system/build.prop and the complete /efs folder including nv_data.bin
The app does this automatically to the internal SDCARD, but just to be on the safe side I would recommend a manual backup to the computer aswell.
There is three steps where a reboot is required after step 2. The app will tell you what to do.
Step1.
Backup everything. If this fails, step2 is not available.
Step2.
Set the new ProductCode and PDA. Reboot!
Step3.
Set CSC and Phone. Do NOT reboot. Connect to Kies2.0 and update!
This setting is not permanent and will go back to previous setting after reboot.
Remember to disable any lagfix before updating!
Done!
-------------------------------------------------------------
How to Restore
Press restore in the menu. Reboot required.
If something fails, please send me your logcat.
So here it is: SpoofFw - requires ROOT and BusyBox
{
"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"
}
Online Market link
If you get problems to connect to Kies after you used this program, try remove the registry key "HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB"
Please let me now if it works out for you.
If you like my work, please consider a small donation.
Thanks a lot for your patch
Hi,
I'm new to the forum and am very interested in your work, at the moment the file to "fool " Kies 2.0 has not worked for me. I have the version 2.2 of Android 9000XWJPB/I9000FOPJP3/I9000XXJPP/I9000XWJPB and product code FOP. Sorry for my english, i'm from Spain.
what is new in this ??
It does'nt entirely work. Tried and it shows me update available.
But when it supposed to start downloading new rom, it say that latest software is already installed in my phone.Then Kies resets and start over offering update again.
So, I guess it detects the real rom in the phone.
Nice patch, though. Maybe you can see what is the problem.
Thanks
Same here - I just posted in the "original" theme about kies registry patcher.
Kies finds update, and when i start upgrading, the phone disconnects, and then after 1s reconects back. I cannot upgrade.
oh crap. didnt try to actually download it. thought it would work. I'll have a look at it. sorry guys.
No panic
Obviously some can upgrade, some cannot. We are the first with this problem.
I have jpx. Could this cause problems?
Those of you who have tried the patch, can you please post your info from the registry and tell me if it worked or not. Include both product code, hidswver, softwarerevision and modelname.
For me, in the registry is still JPY everywhere, after apply patch.
PRODUCT code : GT-I9000HKDXEU
HIDSWVER: I9000XXJPY/I9000OXAJPY/I9000XXJPY/I9000XXJPY
Model Name:GT-I9000
Software Revision: I9000XXJPY/I9000OXAJPY/I9000XXJPY/I9000XXJPY
HTH....
Running Kies 2.0.0.11014_49
HIDSWVER I9000XXJPO/I9000OXAJPO/I9000XXJPP/I9000XXJPO
Product Code GT-I9000HKDTMU
Model Name GT-I9000
Doesn't work unfortunately - it offers me an upgrade, appears to download the file then gives the Disconnected error.
I've also tried manually editing the registry as per kies 1.5 but no more luck.
I've tried on 2 PCs too.
HIDSWVER: I9000BUJP7/I9000GVD2JP5/I9000BUJP5/I9000BUJP7 (SofwareRev is same)
FW: I9000BUJP7/I9000GVD2JP5(CSC)/I9000BUJP5(modem)
PCode: GT-I9000HKDVD2 (VD2)
Kies: v2.0.0.11014_49
OS: Win7 Ultimate 64bit
I checked my registry but to no avail. Also tried deleting DeviceDB key to force kies into reconstructing it. It doesn't offer the fw upgrade option at all.
At least it's good to know someone is trying to develop a way to spoof kies 2.0. Did the patch work with any previous versions of kies 2.0?
I just got some another idea: could we try to hack ProductCode on device instead of on Kies side?
AFAIU ProductCode == CSC. I've googled we can change CSC in following ways:
1) *#272*HHMM# on Android 2.1 and older
2) *#272*IMEI# on Android 2.2 and newer
3) Opening preconfing with ADB
4) Editing /efs/nv_data.bin
Would it make Kies detecting different ProductCode?
There is still one more thing we have to consider: what if Kies detects our changed ProductCode but also firmware versions that were never released for given ProductCode?
Zajec5 said:
I just got some another idea: could we try to hack ProductCode on device instead of on Kies side?
AFAIU ProductCode == CSC. I've googled we can change CSC in following ways:
1) *#272*HHMM# on Android 2.1 and older
2) *#272*IMEI# on Android 2.2 and newer
3) Opening preconfing with ADB
4) Editing /efs/nv_data.bin
Would it make Kies detecting different ProductCode?
There is still one more thing we have to consider: what if Kies detects our changed ProductCode but also firmware versions that were never released for given ProductCode?
Click to expand...
Click to collapse
I have thought about it too. But we still need to change the PDA and PHONE aswell. But I have not yet located where they are stored. My guess is it's hard coded somewhere. Still the drivers need to take it from somewhere, the question is where.
LuffarJoh said:
I have thought about it too. But we still need to change the PDA and PHONE aswell. But I have not yet located where they are stored. My guess is it's hard coded somewhere. Still the drivers need to take it from somewhere, the question is where.
Click to expand...
Click to collapse
There is something like
getBasebandVersion, but I can't track RILRequest, how is is reading RIL_REQUEST_BASEBAND_VERSION... That could show us some file with baseband version maybe.
I have had some progress.
I have managed to change all necessary codes in the phone to be able to spoof Kies. This time I passed the step that the patch didnt!
Unfortunately it's not that simple, it requires root and changes system properties. But it's all reversible. I think I'll try to make an app of it during next week. First is a final exam on Monday.
watch this space.
well, it's much more fun to develop android application then study for an exam
I have successfully switched from XEN to XEE and to DBT.
I'm almost done, just some more bug testing. I'll probably release it tonight
Good news, wait for your release tonight.
luffarjoh said:
well, it's much more fun to develop android application then study for an exam
i have successfully switched from xen to xee and to dbt.
I'm almost done, just some more bug testing. I'll probably release it tonight
Click to expand...
Click to collapse
great news!!!
I have to push the release until tomorrow, I still have some fine tuning to do! Overall is works very well
svnZipper
As you may know developers like @LeeDroid and @baadnewz use Subversion so users can get the latest changes quickly. Although this results in users checking out the Subversion repository and zipping the ROM themselves. This doesn't sound too difficult and it isn't, but to make things easier I made a tool I like to call "svnZipper". It is a pre-built binary with all the dependencies to build a nightly ROM from @LeeDroid and @baadnewz repositories, this has support for Windows, Linux and Mac.
As we are not all perfect the tools does face issues, be it bugs or user issues, I am finding it hard to keep track of all these issues popping up in each thread. Therefore I made this thread to get the latest svnZipper, follow guides and report any issues for me to answers and solve (although it is in HTC 10 thread you can post HTC One M9 and HTC One M8).
The Guide
Step 1
Download the latest svnZipper:
LeeDrOiD get it here
ICE get it here
Put the svnZipper anywhere you like on your PC, I would recommend a folder you can easily access.
Step 2 (Only Required for Mac and Linux)
For Mac and Linux you will need to set the permissions of the binary to be executable. You are probably be familiar with this process if you are a Linux and Mac user but if you don't know the process I will explain it for you. Open up a terminal and change to the directory of the location of your svnZipper, then type the following command:
Mac:
chmod 0755 macSvnZipper followed by enter
Linux:
chmod 0755 linuxSvnZipper followed by enter
Step 3
Execute the svnZipper
Windows:
Double click the svnZipper.exe or open up command prompt in the location of the .exe and type:
svnZipper.exe followed by enter.
Mac:
With the terminal still open from Step 2, type the following command:
./macSvnZipper followed by enter
Linux:
With the terminal still open from Step 2, type the following command:
./linuxSvnZipper followed by enter
Once you have execute the screen you will be presented with a image as shown 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"
}
Step 4
Type the corresponding number next to the device you would like to build for and press enter. This will start the process of checking out files or updating the files that already exist if you have checked out before. This process will vary time consuming depending on how many files are needed to be download from the remote repository.
This process will complete the following steps:
1. Checkout/Update files from the remote repository for your device
2. Make a nightly .zip for your device
3. Make a md5 checksum file for .zip
All checked out files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME
HTC M9 it will be /LeeDrOiD_HIMA
HTC M8 it will be /LeeDrOiD_M8
ICE:
HTC 10 it will be /ice_pme
HTC M9 it will be /ice_hima
HTC M8 it will be /ice_m8
Once completed you will be presented with a screen shot similar to the ones below.
All nightly .zip and .md5 files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME/Builds
HTC M9 it will be /LeeDrOiD_HIMA/Builds
HTC M8 it will be /LeeDrOiD_M8/Builds
ICE:
HTC 10 it will be /ice_pme/Builds
HTC M9 it will be /ice_hima/Builds
HTC M8 it will be /ice_m8/Builds
The builds will be named in the following format:
LeeDrOiD:
HTC 10 it will be LeeDrOiD_PME_RXX.zip
HTC M9 it will be LeeDrOiD_HIMA_RXX.zip
HTC M8 it will be LeeDrOiD_M8_RXX.zip
ICE:
HTC 10 it will be ice_pme_nightly_rXX.zip
HTC M9 it will be ice_hima_nightly_rXX.zip
HTC M8 it will be ice_m8_nightly_rXX.zip
Step 5
If a update comes out and you would like to rebuild the ROM again, follow Step 3 and Step 4
FAQ
QUESTION: The build zip is extremely small and has missing files?
ANSWER: Delete the checked out files and execute the steps above again
QUESTION: The revision checked out by the tool is out of date and doesn't get the latest revision from the remote repository?
ANSWER: Delete the checked out files and execute the steps above again
Note: The FAQ will increase as I get more user experience.
Reporting a Issue
Take screen shot of the errors raised from the tool and post it in this thread. If I don't get as much information as possible I can not help you.
Note: Windows will automatically close is a issue arises, therefore I recommend that you execute the .exe in command prompt instead of double clicking.
XDA:DevDB Information
svnZipper, Tool/Utility for the HTC 10
Contributors
~clumsy~
Source Code: https://github.com/clumsy1991/svnZipper
Version Information
Status: Beta
Current Stable Version: 1.0.4
Stable Release Date: 2016-06-06
Created 2016-06-07
Last Updated 2016-06-07
Changelog
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug
V1.0.4
Considered as initial revision
Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Sent from my HTC 10 using XDA-Developers mobile app
The Great Dane said:
Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Click to expand...
Click to collapse
And press 1 to build
~clumsy~ said:
And press 1 to build
Click to expand...
Click to collapse
Shut up LMFAO [emoji12]
Different filesize
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!
twistednl said:
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!
Click to expand...
Click to collapse
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?
~clumsy~ said:
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?
Click to expand...
Click to collapse
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph
twistednl said:
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph
Click to expand...
Click to collapse
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!
twistednl said:
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!
Click to expand...
Click to collapse
I know! Much appreciated! This why I made the thread so i can capture bugs and peoples experiences.
Thank you!
Though resume download is broken in this SVN tool, it will see the files downloaded as complete and will not give an option to resume or force resume
great job,thanks!
~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Thanks for the heads up....
Sent from my HTC 10 using XDA-Developers mobile app
Just a minor fix, only 1 report case of the bug.
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug
Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.
Ndaoud360 said:
Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.
Click to expand...
Click to collapse
The tool is made for its ease of use and is independent so user don't have to install anything. It was requested by the devs. You can still use a manual solution.
Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Sent from my HTC 10 using XDA-Developers mobile app
I have the same problem as mentioned on the first page. The program does not work correctly if I run it from a network share. It finishes downloading prematurely and it creates a partial ROM which does not work.
I took clumsy's script, stripped some parts in order to create a minimal example and to see what it does (I removed the multiprocess operations). The result: each time I run it, it works for several minutes, then it ends with the following error:
pysvn._pysvn_3_5.ClientError: ra_serf: The server sent a truncated HTTP response body.
It happens each time.
kfasheldon said:
Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Click to expand...
Click to collapse
Sorry man, that will too much work as it wouldn't be possible with my current method.
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs).
I also know that there is a known solution to this problem.
However, there are users who report that they still have a problem with that.
I am writing a new thread to present (I hope) the final solution "Version unmatch"
Remember.
The solution presented in the MTCD - Verified Cross compatible MCUs thread still applies:
1. Before uploading new MCU (dmcu.bin), first export your settings to the dmcu.cfg file (FactorySettings, button Export)
2. After uploading new MCU, restore your dmcu.cfg (file dmcu.cfg on SD card, then MCU Update)
Below is the link to the application that unlocks the device from "Version unmatch"
Code:
https://www.sendspace.com/file/ijmf13
This is Android app so you must install it on your device.
After install and run you should see screen similar to that:
{
"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"
}
Press UNLOCK button. After you should see notifaction like below:
Reboot your unit.
After that, "Version unmatch" should gone
vote for sticky!
Works great!
thank you
Wadzio said:
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs).
I also know that there is a known solution to this problem.
However, there are users who report that they still have a problem with that.
I am writing a new thread to present (I hope) the final solution "Version unmatch"
Remember.
The solution presented in the MTCD - Verified Cross compatible MCUs thread still applies:
1. Before uploading new MCU (dmcu.bin), first export your settings to the dmcu.cfg file (FactorySettings, button Export)
2. After uploading new MCU, restore your dmcu.cfg (file dmcu.cfg on SD card, then MCU Update)
Below is the link to the application that unlocks the device from "Version unmatch"
Code:
https://www.sendspace.com/file/ijmf13
This is Android app so you must install it on your device.
After install and run you should see screen similar to that:
Press UNLOCK button. After you should see notifaction like below:
Reboot your unit.
After that, "Version unmatch" should gone
Click to expand...
Click to collapse
Very good work, Thanks
how to restore dmcu.cfg?
I place in root of drive before upgrade but was ignored.
I changed from LM to HA and had to manually set display and touch key settings
I had this version unmatched problem and was solved with the tool. thanks
For me, the version unmatch tool crashes every single time. Anyone else experience this? What to do now?!?!
Heard of anyone having an issue with their unit crashing when trying to run the app? Mine does. I even reinstalled it several times and even after a full restore, it still crashes. I have an H201.
does this app requires root ? can you please elaborate a little as how this app works ? as the app is not working it asks for reboot and comes back to menu.
Try to manually reboot. Go to the factory settings menu and type hctreboot (step 10).
same for me, Android 10 ,it crash everytime , there is an update ?
same issue , on Android 10 it crashes everytime
laptopmd said:
same issue , on Android 10 it crashes everytime
Click to expand...
Click to collapse
Yes I think a number of people have reported that. Keen to figure it out?
I'm proud to announce that i've found a way to disable that "version unmatch" by modifying the dmcu.img file. It has worked 3 times with 3 different files so i can confirm it work.
Without boring you with the details, what i've done was :
1. decompress the img file with mtcdmcutool , you obtain a dmcu.bin file.
2. open and decompile the file with Ghidra (see screenshot)
3. here i've found where the software check if the version is "unmatch" (by searching the strings into the file).
4. just before you can see a check (cmp param1,#0x0) and a jump in case it doesn't match (beq , etc etc..) , those strange words is called "assembler language".
5. at the end, simply re-compress the files into a valid dmcu.img file, and update your mcu like always.
My simple solution was to force that parm1 value to 0 , to do that i've modified the code from CMP to MOV param1,0x0 and so the jump happen everytime and you don't get the annoying message and the continuous "beep" of the autoradio. I'm actually using my android radio without issues.
laptopmd said:
I'm proud to announce that i've found a way to disable that "version unmatch" by modifying the dmcu.img file. It has worked 3 times with 3 different files so i can confirm it work.
Without boring you with the details, what i've done was :
1. decompress the img file with mtcdmcutool , you obtain a dmcu.bin file.
2. open and decompile the file with Ghidra (see screenshot)
3. here i've found where the software check if the version is "unmatch" (by searching the strings into the file).
4. just before you can see a check (cmp param1,#0x0) and a jump in case it doesn't match (beq , etc etc..) , those strange words is called "assembler language".
5. at the end, simply re-compress the files into a valid dmcu.img file, and update your mcu like always.
My simple solution was to force that parm1 value to 0 , to do that i've modified the code from CMP to MOV param1,0x0 and so the jump happen everytime and you don't get the annoying message and the continuous "beep" of the autoradio. I'm actually using my android radio without issues.
Click to expand...
Click to collapse
Hey, can you upload mtcdmcutool somewhere?
I can't find it anywhere!
Fakken said:
Hey, can you upload mtcdmcutool somewhere?
I can't find it anywhere!
Click to expand...
Click to collapse
You didn't searched really... it is all on this forum
This is the thread : https://forum.xda-developers.com/an...dification-t3745838/post75471198#post75471198
Try to download the file there
Fakken said:
Try to download the file there
Click to expand...
Click to collapse
So use google, he answered with this link : http://www.tehnari.ru/f180/t266132/
It's in russian but you can see the file link, tried and it work.
I don't want to upload it here without the permission of the developer.
Thank you, i don't know if you believe me, but if searched alot to find the file. I even translated the 4pda.ru to search it.
Eh, thank you very much!
i got "error reading a file!" in mtcdmcutools while trying to convert it to .bin file.
how do i go from here? im using a stock dmcu.img file from xtrons.
In my case it says "illegal system!" additionally to the "Unmatch" Banner.
The Tool crashes right after it is opened, my touch screen only works on the upper slide part and there are no "Car Settings" in the Settings anymore..
Any idea what to do there?
Xperia Chinese Keyboard modified to work on any device
Supports pinyin, zhuyin, stroke order, handwriting and Cangjie, as well as English input
Version: 25.1.A.0.45 Patch #6 Updated 2022-11-18
{
"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"
}
Download
From Mega.nz (file too large to attach here):
Patch 6 for LOS 19.1 / Android 12
Patch 5 for LOS 18.1 / Android 11
Spoiler: Other versions – for reference only
Patch 4 - Test (for Lineage 18.1, test workaround)
Patch 3 (for LineageOS 18.1, occasional crashes)
Patch 2 (for LineageOS 17.1)
Patch 1 (for LineageOS 16.0)
Installation
Best installed with: adb install -g <filename>
Otherwise, have to manually grant the permission: Settings → Apps & notifications → See all apps → Xperia Chinese keyboard → Advanced → Display over other apps: Allowed (will crash if you won't)
Enable the input method in Settings → Languages & input and switch to it using the keyboard icon on the navigation bar, which appears when you start editing text
Some Details
Based on firmware H9493_Customized TW_52.1.A.3.137-R4C for Sony Xperia XZ3 (Akatsuki)
Includes libraries to make it work as a user (not system) app:
libbase.so, libc++.so, and libnativehelper.so from LineageOS 18.1
libsqlite.so from SQLite's official precompiled Android binaries
Changed values loaded into $LayoutParams;->type:I from 0x000007dc = 0x000007d9 (TYPE_KEYGUARD_DIALOG) | 0x00000002 (TYPE_APPLICATION) | 0x00000001 (TYPE_BASE_APPLICATION), only allowed for system apps, to 0x000007f6 (TYPE_APPLICATION_OVERLAY) and updated the manifest accordingly to request the permission android.permission.SYSTEM_ALERT_WINDOW (which must be granted manually)
Patch 3: Remove dependency on Sony Vibration Effect library (com.sonymobile.vibrationeffect.api_1) from the manifest
Patch 3: Replace all references to Sony Vibration Effect library: invoke-static {p1}, Lcom/sonymobile/vibrationeffect/VibrationEffect;->get(I)Landroid/os/VibrationEffect;which were causing the app to crash, with standard Android calls:
const/4 p0, -0x1 (DEFAULT_AMPLITUDE)
const-wide/16 v2, 0xc (Duration: 12 ms)
invoke-static {v2, v3, p0}, Landroid/os/VibrationEffect;->createOneShot(JI)Landroid/os/VibrationEffect;
— for keypresses
const v0, 0x2 (EFFECT_TICK)
invoke-static {v0}, Landroid/os/VibrationEffect;->createPredefined(I)Landroid/os/VibrationEffect;
— for other events
Patch 4 - Test: Remove the invocation of a virtual method invoke-virtual {p0}, Lcom/sonyericsson/textinput/chinese/uxp/view/hw/HWFullView;->getVisibility()I that causes a crash under some circumstances in InputMethodServiceGlue. However the side effect of this change is that other UI elements cannot be interacted with while the keyboard is open. How to fix this completely needs further investigation. Since the crash seems rare, I recommend sticking with Patch 3 for now.
Patch 5: A different workaround for the above mentioned issue. If iget-object p0, p0, Lcom/sonyericsson/textinput/chinese/glue/InputMethodServiceGlue;->mHwFullView:Lcom/sonyericsson/textinput/chinese/uxp/view/hw/HWFullView; returns 0 (i.e. effectively NULL but there's no explicit check for that in Smali), then skip the call and return from the method. Otherwise, proceed. After a week of testing, this seems to work well: no rare crashes, and the UI is accessible too with the keyboard open.
Tested to work on two different LineageOS 18.1 devices. Should work elsewhere too. If it doesn't, it's probably because of the three libraries (libbase.so, libc++.so, and libnativehelper.so): check adb logcat and replace them with the versions from your system.
Patch 6: Fix compatibility with LOS 19.1/Android 12 where a call to jniGetFDFromFileDescriptor() from libnativehelper.so fails by design due to API changes (see: Google Issue Tracker), and the version of the library included with the app can no longer be used due to name conflict with the system library with the same name. The workaround: rename the bundled libnativehelper.so (same as Patch 5/Android 11/LOS 18.1, so unchanged) to libforeignenemy.so and change references to it in libcootek_pte_oem.so, libcootek_pte_oem_western.so and libcurve_oem.so accordingly. Also update libbase.so and libc++.so to current versions from LOS 19.1 (Android 12).
Related
Xperia keyboard for most languages port by @greenys'
Xperia Chinese keyboard version 10.1.A.0.1 (Android 4.4+, 2012-2013) by @danist727
That's some amazing work there. I wish there was a more up to date version for general languages not just the good ol 8.0.A.110 version that I've been using for 3 years or more across my devices. Thanks a lot.
Thank you for your work! However, the link is down, it is giving 410 error from XDA. Can you reupload it? Thanks again.
sjdhmtthm said:
Thank you for your work! However, the link is down, it is giving 410 error from XDA. Can you reupload it? Thanks again.
Click to expand...
Click to collapse
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Aqq123 said:
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Click to expand...
Click to collapse
It works now, must be having some errors just now. Thanks again.
Edit: Part 2 seems to not be able to download and corrupted, second try gives me the same error again.
I asked my friend who is not logged in to download and he experienced the same error.
It would be great if you can upload it elsewhere, the two tries I where I successfully downloaded part 2 returns corrupted. Thank you.
Edit 2: Changing browsers on mobile worked. Surprised that both Firefox on mobile and desktop returned an error for me. Thank you, problem is solved.
Is this keyboard for chinese only or can I use english as well? its been a while and long since we get an updated Xperia Keyboard version, still using the 2/3 years old v8.1.A.0.12 dated November 12, 2017.
SM-03 said:
Is this keyboard for chinese only or can I use english as well?
Click to expand...
Click to collapse
It can be used for English input too. If you take a look at the first 3 screenshots, there is a button (labelled "CN") that toggles between English and Chinese in the bottom right corner of the keyboard.
It supports word completion in English too but there's no way to type accented characters (for other languages written in the Latin script).
how to dl and extract this? I downloaded two p[arts but still getting error while extracting, any other parts there or missing?
is there any update for android10?
after update to 55.1.A.0.748
chinese keyboard keep crashed
SM-03 said:
any other parts there or missing?
Click to expand...
Click to collapse
Just checked again, it unpacks fine. Nothing is missing. The complete instructions are already in the first post. Not sure what else would need explaining.
frank3302 said:
is there any update for android10?
Click to expand...
Click to collapse
I don't use Android 10. Feel free to contribute an update, and I will link to it in the first post.
Aqq123 said:
Just checked again, it unpacks fine. Nothing is missing. The complete instructions are already in the first post. Not sure what else would need explaining.
Click to expand...
Click to collapse
Yes, it's working (extracted) as per the instructions written into the OP, but the font size is too small that I didn't see /notice that instruction earlier, you should've mentioned that in bold & highlighted for better & clear visibility.
SM-03 said:
I didn't see /notice that instruction earlier, you should've mentioned that in bold & highlighted for better & clear visibility.
Click to expand...
Click to collapse
This board is called XDA Developers for a reason. As a participant you are expected to possess a modicum of rudimentary computer skills and, more importantly, willingness to learn to solve your own problems. In particular, this thread is in the Development section. This is not the place to demand an illustrated step-by-step tutorial how to unpack a ZIP file.
Besides, as duly proven, even the best instructions won't help an ignorant person who can't be bothered to read them such as yourself. And finally, neither me nor anyone else here owes you anything just because you can't get something to work, so the only thing I "should have" is not indulged this behavior earlier.
Good luck with your future endeavors as you will need it with this kind of an attitude. Now, feel free to move on.
Aqq123 said:
This board is called XDA Developers for a reason. As a participant you are expected to possess a modicum of rudimentary computer skills and, more importantly, willingness to learn to solve your own problems. In particular, this thread is in the Development section. This is not the place to demand an illustrated step-by-step tutorial how to unpack a ZIP file.
Besides, as duly proven, even the best instructions won't help an ignorant person who can't be bothered to read them such as yourself. And finally, neither me nor anyone else here owes you anything just because you can't get something to work, so the only thing I "should have" is not indulged this behavior earlier.
Good luck with your future endeavors as you will need it with this kind of an attitude. Now, feel free to move on.
Click to expand...
Click to collapse
wow, so many words for just saying the small font & you should've written it with bigger font size for better visibility? You're rare & amazing.
I am not able to merge the two zipped files into one. I followed the instruction to rename as .zip and .z01 for both files but the second part stated no content inside to extract. should I download rar software to unrar it in desktop file explorer? Can someone kind hearted enough keep the file in one and upload somewhere for me to download?
atisha said:
I am not able to merge the two zipped files into one. I followed the instruction to rename as .zip and .z01 for both files but the second part stated no content inside to extract. should I download rar software to unrar it in desktop file explorer? Can someone kind hearted enough keep the file in one and upload somewhere for me to download?
Click to expand...
Click to collapse
I just checked and it unpacks with WinRAR and 7-Zip for me. Anyway, since I made another version later, here they are both, externally hosted:
Patch 2 (try this first, should be compatible with LineageOS 17.1 at least)
Patch 1 (original version as linked above)
I also updated the original post accordingly.
Found a Bug
Hi Aqq123,
This is some impressive work, thank you for making this!
Just wanted to post a bug I found: the "pull down menu" for the Chinese typing doesn't work. E.g. I want to type the word 蚝煎, but after clicking on the arrow on the right, nothing appears! So I wasn't able to type things beyond the suggestions in the first row.
I'm using Sony Xperia 10 II, Android 10 (Build number 59.0.A.10.5), and I used Patch 2 of your download. Would really appreciate if you could solve the bug, because this keyboard is such a life saver for me. Thanks!
Screenshot: https:// drive. google. com/ file/ d/ 12eEBAzBalbq0ZKfQMh2SLI-045-Gb1Z1/ view?usp=sharing
(Included the spacing because the forum just wouldn't let me post it)
johnsyh said:
Just wanted to post a bug I found: the "pull down menu" for the Chinese typing doesn't work
Click to expand...
Click to collapse
You're right, thanks for spotting it. It used to work in the first version though, so it's probably down to some library incompatibility (and the first version itself won't work with the newer Android). I'll look into it when I have the time. A better approach though might be to ditch it altogether and look at adopting a newer APK version instead. Meanwhile, a lousy workaround is to just hand-write the character.
Since you're using Sony stock firmware, have you tried downloading the Hong Kong or Taiwan version for your device with XperiFirm, extracting the APK from there (for example with UnSIN), and installing it? It'd either work immediately or, if not, the exact library versions to make it work would also be there.
Aqq123 said:
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Click to expand...
Click to collapse
Thank you so much. I am able to download patch 2 and install directly. So so very grateful as this is the best T9 keyboard ever! (Could be better if it supports Malay too with black layout white font but one shouldnt be too greedy).
Aqq123 said:
You're right, thanks for spotting it. It used to work in the first version though, so it's probably down to some library incompatibility (and the first version itself won't work with the newer Android). I'll look into it when I have the time. A better approach though might be to ditch it altogether and look at adopting a newer APK version instead. Meanwhile, a lousy workaround is to just hand-write the character.
Since you're using Sony stock firmware, have you tried downloading the Hong Kong or Taiwan version for your device with XperiFirm, extracting the APK from there (for example with UnSIN), and installing it? It'd either work immediately or, if not, the exact library versions to make it work would also be there.
Click to expand...
Click to collapse
HI would you have general sony xperia keyboard (non Chinese, English) apk as well to share? with layout skin colour if possible.
On behalf of my wife, who has just upgraded from Xperia XZs to the new Xperia 1 III, and couldn't get over how bad gboard is over the Xperia 注音 input (she has a very unusual character in her name, which gboard doesn't recognize, it spoiled her fun of getting a new device when she couldn't even type her name in correctly during setup) - thank you! You have made me a hero around the house for finding this, and installing it on her phone. My old account on this forum got lost in time, gone with an e-mail domain that no longer exists, but I set up a new one just to thank you for your work!
{
"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"
}
(EXYNOS ONLY) Samsung Galaxy S10 series OneUI 3.0 Android 11 Beta Thread.
Samsung has started the Android 11 Beta program for the Galaxy S10 series
This thread will be for sharing tips and help and update.zip/.bin files (when available) for the upcoming OneUI 3.0 Android 11 Beta for the Galaxy S10 series (Exynos/International/Unlocked) version.
Eligible models
-Galaxy S10e (SM-G970F)
-Galaxy S10 (SM-G973F)
-Galaxy S10+ (SM-G975F)
ADB-method:
1. Download SDK platform tools from here https://developer.android.com/studio/releases/platform-tools
2. Extract them on your desktop.
3. Inside the extracted folder put the update.zip
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown the phone.
6. Holding power+bixby+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (you scroll down using the volume buttons and select using the power button).
8. Connect the phone to the PC using original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+bixby+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
Please don't keep asking over and over again about the update.zip files, If it's available then it will be present in the latest posts or in this thread. If not then no one has pulled it yet.
It's recommended to make a backup of your data before updating to the Android 11 Beta.
-Update.zip FOTA links:
S10e (SM-G970F):
Beta 1 DTJA -> ZTKF
Direct Link to Beta 2 from Android 10 (DTL1):
Beta 2 DTL1 -> ZTL8
S10 (SM-G973F):
Beta 1 DTJA -> ZTKF
Beta 2 ZTKF -> ZTL8
Direct link to Beta 2 from Android 10 (DTL1):
Beta 2 DTL1 -> ZTL8
S10+ (SM-G975F):
Beta 1 DTJA -> ZTKF
Beta 2 ZTKF -> ZTL8
Beta 3 ZTL8 -> ZTLJ
OneUI 3.1 EUA4 -> FUBD thanks to @AndrzejDwo
S10 5G (SM-G977N):
Beta 1 DTJ8 -> ZTKF
Beta 2 ZTKF -> ZTL8
-Update.zip Gdrive Links:
In case links above are not working for you.
S10e (SM-G970F):
Beta 1 (DTJA -> ZTKF)
GDrive Link
S10 (SM-G973F):
Beta 1 (DTJA -> ZTKF)
GDrive Link
S10+ (SM-G975F):
Beta 1 (DTJA -> ZTKF)
GDrive Link
As of Beta 1, when you try to update to Beta 2 with SD Card method, adb will not recognize the SD Card for some reason, you will need to use the ADB method in order to flash Beta 2.
Rename the .bin file to update.zip in order to be able to flash it from recovery.
A common mistake done by some people is that they see the file name update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, Make sure you do it right.
Important Notes:
1. You cannot go into recovery using the old method in this beta, However, there are two work arounds
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or use the AKG earphones.
3. Hold down Volume up + Bixby + Power buttons and keep pressing them until you enter recovery mode.
2. GPay Does not work in the Beta, And will continue not to work until the stable version gets released.
Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released for your CSC, thats most likely not happening before the BETA is over.
Small note:
My S10+ device isn't from a country that has a beta program, so i will not be able to pull the update.zip file unfortunately, But i will try my BEST to keep the thread updated with the latest beta update.zip file (If/when someone pulls it)
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
This thread was heavily inspired by @henklbr's great efforts in the last beta threads for different samsung devices, Also thanks to him for letting me copy little parts from his threads.
Wait and see. ?
I'm waiting eagirly to try it??
The exynos Galaxy Note 10+ started receiving the beta yesterday, Im expecting the S10 series to receive the beta Tuesday or Wednesday. Lets wait and see..
AhmedMomen said:
The exynos Galaxy Note 10+ started receiving the beta yesterday, Im expecting the S10 series to receive the beta Tuesday or Wednesday. Lets wait and see..
Click to expand...
Click to collapse
Do you have the link for the update file ?
I have a exynos, but I am not in one of the countries where you can apply for the beta
ashes said:
Do you have the link for the update file ?
I have a exynos, but I am not in one of the countries where you can apply for the beta
Click to expand...
Click to collapse
It's not out for the galaxy s10 series yet.
Hopefully it will come out in the next 2 days.
waiting.
Waiting :good:
Mohamad Gahed said:
Waiting :good:
Click to expand...
Click to collapse
Alrighty then
Mhh...this delay is weird. I'm afraid we'll have to wait a few more weeks.
Noooooo!
Excited!
Gonna get my S10 out again. Highly anxious to try it out again. Love that phone!
BinaryShadow said:
Gonna get my S10 out again. Highly anxious to try it out again. Love that phone!
Click to expand...
Click to collapse
Welcome.
Dobro došao.
Also today still nothing...
I mean the note 10 got it last saturday so i dont think the s10 update will be delayed much, seems like its either tommorow or friday-saturday then.. (hopefully not later than that). Fingers crossed.
AhmedMomen said:
I mean the note 10 got it last saturday so i dont think the s10 update will be delayed much, seems like its either tommorow or friday-saturday then.. (hopefully not later than that). Fingers crossed.
Click to expand...
Click to collapse
And I think it should come this week. I am SEE (South East Europe).
I hope so to!
GALAXY S10, Z FLIP & FOLD 2 ONE UI 3.0 BETA UPDATE POSTPONED
https://www.tizenhelp.com/galaxy-s10-z-flip-fold-2-one-ui-3-0-beta-update-postponed/
ZmisiS said:
GALAXY S10, Z FLIP & FOLD 2 ONE UI 3.0 BETA UPDATE POSTPONED
https://www.tizenhelp.com/galaxy-s10-z-flip-fold-2-one-ui-3-0-beta-update-postponed/
Click to expand...
Click to collapse
Its either friday-saturday or next tuesday then it seems...
ZmisiS said:
GALAXY S10, Z FLIP & FOLD 2 ONE UI 3.0 BETA UPDATE POSTPONED
https://www.tizenhelp.com/galaxy-s10-z-flip-fold-2-one-ui-3-0-beta-update-postponed/
Click to expand...
Click to collapse
I would have bet on it.