when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.
Aditya2512 said:
when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.
Click to expand...
Click to collapse
I'm facing the same problem ... then I tried to remove this META-INF/com/google/android/updater-script/assert(cm.verify_baseband("2.0.2.C1.4-00039") == "1"); line, worked for me... it flashed .. booted .. but at second rebooting (due to data toggle error) its nav bar got inactive ... recent apps were not showing up... so I need to leave it .. at often it was getting into bootloops
Anjan Roy said:
I'm facing the same problem ... then I tried to remove this META-INF/com/google/android/updater-script/assert(cm.verify_baseband("2.0.2.C1.4-00039") == "1"); line, worked for me... it flashed .. booted .. but at second rebooting (due to data toggle error) its nav bar got inactive ... recent apps were not showing up... so I need to leave it .. at often it was getting into bootloops
Click to expand...
Click to collapse
I tried it but not working even not flashing.
BTW thanks.
Try using TWRP 2.8.7.0 for flashing ROM.
Aditya2512 said:
when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.
Click to expand...
Click to collapse
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
P.S.
You can also use TWRP 3.0.2.0 for jalebi.It works fine.
SSAURABHH said:
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
Click to expand...
Click to collapse
Edit Updater Script and Delete all its Content & Paste this
assert(getprop("ro.product.device") == "jalebi" || getprop("ro.build.product") == "jalebi" || abort("E3004: This package is for device: jalebi; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
I have installed lineage all was ok. But suddenly after 1/2 an hour it got off..
When I try to switch on its got bloated
I've got the same issue and thats why I cannot upgrade to 14.1.It shows failed to verify the current baseband version: 2.
please help.
SSAURABHH said:
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
Click to expand...
Click to collapse
i'm on 2.8.7.0 but still facing the issue
---------- Post added at 07:10 PM ---------- Previous post was at 06:33 PM ----------
Indrajeet Singh said:
Edit Updater Script and Delete all its Content & Paste this
assert(getprop("ro.product.device") == "jalebi" || getprop("ro.build.product") == "jalebi" || abort("E3004: This package is for device: jalebi; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
Click to expand...
Click to collapse
Comparing BASEBAND version 2.0.2.C1.4-00039 to 2.0.2.C1-36914ERROR: It appears you are running an unsupported baseband.
ERROR: It appears you are running an unsupported baseband.script aborted: assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
NageshGeek said:
i'm on 2.8.7.0 but still facing the issue
---------- Post added at 07:10 PM ---------- Previous post was at 06:33 PM ----------
Comparing BASEBAND version 2.0.2.C1.4-00039 to 2.0.2.C1-36914ERROR: It appears you are running an unsupported baseband.
ERROR: It appears you are running an unsupported baseband.script aborted: assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
Click to expand...
Click to collapse
Your device's baseband is updated(20151215),and btw the issue is not the same,both errors are diffrent.TWRP 3.0.3.0 for jalebi.img has some issue while reading the baseband(Probably only in LOS),if u want to use 3.x version u can use twrp 3.0.2.0 for jalebi.img,it works fine,but in your case the issue is different,you have to downgrade to the oldest baseband for the device.And please do not edit the script,if the baseband version do not match(like in your case) and u installed the ROM somehow,you may end up with a bricked device.
Btw LOS 14.1 is not booting up,if boots,then in the next reboot it stucks at boot animation.
Do anyone has working solution?
yes i do.
Dush4711 said:
Do anyone has working solution?
Click to expand...
Click to collapse
follow these steps to remove the zip verification codes.
1.) unzip the rom in Pc
2.) go to extracted rom folder\META-INF\com\google\android and open updater-script using note pad (notepad ++ )
3.) delete the first two lines of the script and recompress
4.) Flash and enjoy
if you didn't get what im saying search for this video in youtube named " How to Solve Status 7 Error when installing custom rom ( LG G3 CyanogenMod 14.1 ) " by Techious.
P.S: im not allowed to share links, new to xda.
:good:
solution.
Bro,I had the same problem where twrp said "failed to read current baseband version:2".
So,I flashed my stock rom (you can find the procedure in xda) and flashed twrp 2.8.7.0 and then flashed the lineage os and it worked properly.
I Have Yunique plus n i hv successfully installed Lineage rom.. Jst changed the update script with other unofficial lineage roms script.. Work fine:good: I roll back bcz i need volte waiting fr it
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
kumarakash938 said:
Bro,I had the same problem where twrp said "failed to read current baseband version:2".
So,I flashed my stock rom (you can find the procedure in xda) and flashed twrp 2.8.7.0 and then flashed the lineage os and it worked properly.
Click to expand...
Click to collapse
How did you flashed stock ROM?est tool or flashable zip?
baseband problem wih lineage os
prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
Stock rom have two versions , lineage os rom work on baseband version of the 1st version of stok rom.
so try flashing 1st version of stock rom and then official lineage os.
And official lineage os in non volte rom.
what error you're getting while flashing
prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
I think it's because the firmware is different.
I'm not sure about this, but I think you need to migrate from cm firmware.
---------- Post added at 02:32 PM ---------- Previous post was at 02:32 PM ----------
shikhar adhikari said:
what error you're getting while flashing
Click to expand...
Click to collapse
Error 7
shikhar adhikari said:
what error you're getting while flashing
Click to expand...
Click to collapse
prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
iamanurag said:
I Have Yunique plus n i hv successfully installed Lineage rom.. Jst changed the update script with other unofficial lineage roms script.. Work fine:good: I roll back bcz i need volte waiting fr it
Click to expand...
Click to collapse
---#Saransh#--- said:
follow these steps to remove the zip verification codes.
1.) unzip the rom in Pc
2.) go to extracted rom folder\META-INF\com\google\android and open updater-script using note pad (notepad ++ )
3.) delete the first two lines of the script and recompress
4.) Flash and enjoy
if you didn't get what im saying search for this video in youtube named " How to Solve Status 7 Error when installing custom rom ( LG G3 CyanogenMod 14.1 ) " by Techious.
P.S: im not allowed to share links, new to xda.
:good:
Click to expand...
Click to collapse
ashwin.varma4441 said:
I think it's because the firmware is different.
I'm not sure about this, but I think you need to migrate from cm firmware.
---------- Post added at 02:32 PM ---------- Previous post was at 02:32 PM ----------
Error 7
Click to expand...
Click to collapse
So guys here's a solution for successfully installing lineage os on yu yunique ... I'm currently on lineage and that's super awesome and highly fluid... Just flash cm 14.1 zip link : https://drive.google.com/file/d/0ByL...xpQXd5T1U/view
using twrp link : https://drive.google.com/file/d/0ByL...lsMTlCMjA/view
; and this installation will update yunique's splash and boot image both with stock's one ... so now you need to go for installation of latest cos modem , actually due to lack of that we are gettiing the baseband 7 error ... link for cos modem : https://www.androidfilehost.com/?fid=817550096634760193
command : fastboot flash modem NON-HLOS.bin go to fastboot mode by enabling debugging mode on your device and unlocking oem ... and go to terminal / cmd and type >>
adb devices
adb reboot bootloader or adb reboot-bootloader fastboot devices
fastboot oem unlock-go
fastboot flash modem NON-HLOS.bin
fastboot reboot
Now latest cos modem .. you have ... go to recovery (twrp) and grab latest los (lineage) release and flash (clean flash strongly recommended ... do it surely) and no error ... yes no erros ... you'll be booted to most -awaited los within 3mins ... have fun... and the problem was occurring due to lack of stock splash.img , boot.img and latest cos modem(mismatching of baseband ) ... thank you ...
---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------
Anjan Roy said:
So guys here's a solution for successfully installing lineage os on yu yunique ... I'm currently on lineage and that's super awesome and highly fluid... Just flash cm 14.1 zip link : https://drive.google.com/file/d/0ByL...xpQXd5T1U/view
using twrp link : https://drive.google.com/file/d/0ByL...lsMTlCMjA/view
; and this installation will update yunique's splash and boot image both with stock's one ... so now you need to go for installation of latest cos modem , actually due to lack of that we are gettiing the baseband 7 error ... link for cos modem : https://www.androidfilehost.com/?fid=817550096634760193
command : fastboot flash modem NON-HLOS.bin go to fastboot mode by enabling debugging mode on your device and unlocking oem ... and go to terminal / cmd and type >>
adb devices
adb reboot bootloader or adb reboot-bootloader fastboot devices
fastboot oem unlock-go
fastboot flash modem NON-HLOS.bin
fastboot reboot
Now latest cos modem .. you have ... go to recovery (twrp) and grab latest los (lineage) release and flash (clean flash strongly recommended ... do it surely) and no error ... yes no erros ... you'll be booted to most -awaited los within 3mins ... have fun... and the problem was occurring due to lack of stock splash.img , boot.img and latest cos modem(mismatching of baseband ) ... thank you ...
Click to expand...
Click to collapse
First two links will not work now , I got them a long ago , I can't help u with that
Dush4711 said:
How did you flashed stock ROM?est tool or flashable zip?
Click to expand...
Click to collapse
First try to revert back to TWRP 2.8.7.0 and then install lineageOS firmware + LineageOS ROM.
Related
http://goo.gl/4G5Fs
Verizon Samsung Galaxy S3 modified OTA updates
Released: October 30, 2012
Last update: March 6, 2013
Download:
v1
MD5 (unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip) = 476f0b25b4244743dd7b8559db2f91e4
MD5 (unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALG1-ota-goo.gl-4G5Fs-v1.zip) = e17739a0614c5fd69ef5d176546851ae
MD5 (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip) = 28b22ba5189ab46e39bb9841b648e128
MD5 (unsigned-d2vzw-JRO03L.I535VRBLK3-from-IMM76D.I535VRALHE-ota-goo.gl-4G5Fs-v1.zip) = a41dfa86a8201f3641ac52ffd5f157e5
MD5 (SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-goo.gl-4G5Fs-v1.zip) = 2a65ab4545538b2905cea6b879587683
MD5 (unsigned-d2vzw-JZO54K.I535VRBMB1-from-JRO03L.I535VRBLK3-ota-goo.gl-4G5Fs-v1.zip) = 367c422abdf00db4311d0759267144b8
Original OTA updates (just mirroring them here, don't apply these):
MD5 (signed-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota.zip) = 6755655c06048808e6f91b3589027f32
MD5 (signed-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALG1-ota.zip) = b4dc0238718c8f4320e19c31ba37e906
MD5 (signed-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota.zip) = 3f1cb228b624ab93af8bf3ae9dd4974d
MD5 (signed-d2vzw-JRO03L.I535VRBLK3-from-IMM76D.I535VRALHE-ota.zip) = 82f73037919666c72fc4d94afa1dc82f
MD5 (signed-d2vzw-JZO54K.I535VRBMB1-from-JRO03L.I535VRBLK3-ota.zip) = 3ee54dedd48f8f2e47717fbf3e9d7ec0
If you are upgrading to Jelly Bean and have Google Wallet installed, you should upgrade Google Wallet to the latest modified version first before applying the modified OTA. Immediately after applying the modified VRBLK3 OTA, apply the SGS3 Jelly Bean NFC libraries for Google Wallet. The US variant libraries are mirrored here, see the original thread for other variants.
These updates are for Verizon Samsung Galaxy S3’s that have been rooted, custom recovery flashed, bootloader unlocked, and have Google Wallet and the associated NFC libraries installed. If you did all those things to your S3 and want to apply the stock OTA updates, this is for you.
Restore your stock build.prop if you have modified it to activate Google Wallet. Make sure you are running the latest version of your custom recovery software and apply the modified update for your software version. The recommended recovery to use is ClockworkMod Recovery 6.0.1.2 (or greater) which can be installed using ROM Manager.
To create the modified updates, I took a stock Verizon SGS3 running IMM76D.I535VRALF2, rooted it, flashed a custom recovery, unlocked the bootloader and installed Google Wallet using known methods. Then, I downloaded each OTA update in turn and unpacked it, edited the updater-script to remove references to aboot, recovery and the stock NFC libraries and added a line to correct the permissions for the superuser binary, then repacked the update and applied it. This successfully updated the device without affecting the aboot or recovery partitions or failing due to NFC library checks and maintained root access.
Only the updater-scripts have been modified. The original OTA updates are provided for comparison.
Can you fix your link for (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip)
i got a status 7 error when trying to install.... failed getprop ("ro.product.device") == "d2vzw" II get prop ("ro.build.product") == "d2vzw"
guyd said:
Can you fix your link for (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip)
Click to expand...
Click to collapse
Got it, thanks.
Seanzle said:
i got a status 7 error when trying to install.... failed getprop ("ro.product.device") == "d2vzw" II get prop ("ro.build.product") == "d2vzw"
Click to expand...
Click to collapse
This only works on Verizon SGS3 with stock ROM. Revert your build.prop back to stock if it is still modified from when you activated Google Wallet.
I dont have google wallet
Seanzle said:
I dont have google wallet
Click to expand...
Click to collapse
What update are you trying to apply? What are you currently running (ROM, recovery)? You may need to update your recovery. See the last FAQ question on this post:
Q: It's not working by flashing via recovery! I get something like this:
assert failed: getprop("ro.product.device") == "d2vzw" || getprop("ro.build.product") == "d2vzw"
E: error in /emmc/VRLHD.modem.zip
(status 7)
A: It's failing the assert. These check what device you have and older versions of clockworkmod didn't have the proper device in there. Update your recovery first. EZ Recovery can do this for you or you can grab something from here: http://goo.im/devs/invisiblek/i535/recoveries then try again
Click to expand...
Click to collapse
OTA still asking me to install update
I successfully installed the rooted unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip. However, my phone is still bugging me to install an "Important Update" I have been deferring it because I am worried that if I let it go, it will remove my root and prevent me from using Google Wallet.
Is it safe to allow the phone to install the update and I can re-apply root and Google wallet later?
If not, where did the update's files download to, so that I can delete them manually?
Thanks in advance
I have tried stock and CWD recovery on my GS3 and still getting failed update. Any ideas?
Besides being rooted for Google Wallet I haven't done anything else to the phone.
when using the stock root it comes up with "e:signature verification failed" on both files
ouray770 said:
I successfully installed the rooted unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip. However, my phone is still bugging me to install an "Important Update" I have been deferring it because I am worried that if I let it go, it will remove my root and prevent me from using Google Wallet.
Is it safe to allow the phone to install the update and I can re-apply root and Google wallet later?
If not, where did the update's files download to, so that I can delete them manually?
Thanks in advance
Click to expand...
Click to collapse
It is safe to allow the install. The update won't do anything because the updater binary will check the signature on your NFC libraries and prevent it from happening. After the update fails, SDM (Samsung's updater app) will behave as if the update completed successfully. Recommend you freeze SDM using Titanium Backup after letting the update fail.
(edit) You won't need to reroot or reinstall Google Wallet. Just wanted to make that clear. Also, since you're talking about applying the VRALG7 update, SDM will prompt you to install the next OTA update VRALHE (which will also fail) so after applying the modified VRALG7 update you should install the modified VRALHE OTA update and then let SDM try to install the official VRALHE OTA update. Then SDM will act normal.
solidage said:
I have tried stock and CWD recovery on my GS3 and still getting failed update. Any ideas?
Besides being rooted for Google Wallet I haven't done anything else to the phone.
when using the stock root it comes up with "e:signature verification failed" on both files
Click to expand...
Click to collapse
What do you mean by both files? What is the current software version on your phone?
Any modifications to your phone from stock may cause the updates to fail. I have only disabled a few signature checks related to Google Wallet (NFC libraries) and nothing else. If there are *any* other files on your system partition that are not stock, that may cause the signature verification to fail.
If you can include any other logging info, that would be helpful.
(edit) You *must* use a custom recovery to flash the modified OTA. Try using the latest version ClockworkMod recovery, install it using EZ Recovery.
Happen to have the OTA from VRALF1?
control1110 said:
Happen to have the OTA from VRALF1?
Click to expand...
Click to collapse
Do you mean VRALG1? If I have some time tonight I can see about it.
NFC Service keeps stopping and it's locking my phone
cj64 said:
It is safe to allow the install. The update won't do anything because the updater binary will check the signature on your NFC libraries and prevent it from happening. After the update fails, SDM (Samsung's updater app) will behave as if the update completed successfully. Recommend you freeze SDM using Titanium Backup after letting the update fail.
(edit) You won't need to reroot or reinstall Google Wallet. Just wanted to make that clear. Also, since you're talking about applying the VRALG7 update, SDM will prompt you to install the next OTA update VRALHE (which will also fail) so after applying the modified VRALG7 update you should install the modified VRALHE OTA update and then let SDM try to install the official VRALHE OTA update. Then SDM will act normal.
Click to expand...
Click to collapse
THANKS!! After a tiresome update of clockworkmod recovery (touch-6.0.1.2) via terminal emulator, I was able to flash both of the modified update zip files and I will approve the OTA install at noon today. If anything breaks after that, I will reply again.
---------- Post added at 12:15 PM ---------- Previous post was at 11:57 AM ----------
---------- Post added at 12:24 PM ---------- Previous post was at 12:15 PM ----------
I spoke to soon. Now I continually get "Unfortunately the NFC service has stopped" and it will not go away!
cj64 said:
Do you mean VRALG1? If I have some time tonight I can see about it.
Click to expand...
Click to collapse
Yes, Thank you
cj64 said:
What do you mean by both files? What is the current software version on your phone?
Any modifications to your phone from stock may cause the updates to fail. I have only disabled a few signature checks related to Google Wallet (NFC libraries) and nothing else. If there are *any* other files on your system partition that are not stock, that may cause the signature verification to fail.
If you can include any other logging info, that would be helpful.
(edit) You *must* use a custom recovery to flash the modified OTA. Try using the latest version ClockworkMod recovery, install it using EZ Recovery.
Click to expand...
Click to collapse
Baseband Version
I535VRLF2
Kernel Version
3.0.8
Android Version
4.0.4
Build
IMM76D.I535VRLF2
The only thing I have done to this phone was rooted it, then edited the build.prop for google wallet, then reverted back to the old build.prop (Google wallet was disabled)
When I attempt to install via EZ-REcovery and CWM I get the following error
with the file ending zmh.zip
installing update...
assert failed: getprop("ro.product.device") =="d2vzw
getprop("ro build.product") =="d2vzw
E; Error in /sdcard/FILENAME.zip
Status 7
Installation aborted
with the file ending QXM.zip
Assert failed file_getpropr ("/system/build.prop" ."ro.build.fingerprint") == "Verizon/d2vzw/d2vzw 4.0.4/imm76D/i53VRALG7.user/release-keys"
Error in /sdcard/FILENAME.zip
Status 7
ouray770 said:
THANKS!! After a tiresome update of clockworkmod recovery (touch-6.0.1.2) via terminal emulator, I was able to flash both of the modified update zip files and I will approve the OTA install at noon today. If anything breaks after that, I will reply again.
---------- Post added at 12:15 PM ---------- Previous post was at 11:57 AM ----------
---------- Post added at 12:24 PM ---------- Previous post was at 12:15 PM ----------
I spoke to soon. Now I continually get "Unfortunately the NFC service has stopped" and it will not go away!
Click to expand...
Click to collapse
Recommend you reflash the latest modified Google Wallet. There may be some mixed NFC libraries on your device (some Verizon, some Sprint). Let us know if that solves it.
solidage said:
Baseband Version
I535VRLF2
Kernel Version
3.0.8
Android Version
4.0.4
Build
IMM76D.I535VRLF2
The only thing I have done to this phone was rooted it, then edited the build.prop for google wallet, then reverted back to the old build.prop (Google wallet was disabled)
When I attempt to install via EZ-REcovery and CWM I get the following error
with the file ending zmh.zip
installing update...
assert failed: getprop("ro.product.device") =="d2vzw
getprop("ro build.product") =="d2vzw
E; Error in /sdcard/FILENAME.zip
Status 7
Installation aborted
with the file ending QXM.zip
Assert failed file_getpropr ("/system/build.prop" ."ro.build.fingerprint") == "Verizon/d2vzw/d2vzw 4.0.4/imm76D/i53VRALG7.user/release-keys"
Error in /sdcard/FILENAME.zip
Status 7
Click to expand...
Click to collapse
You cannot apply the 2nd update until you have successfully applied the 1st update. That is why the file ending QXM.zip, which I assume is unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip, fails. You aren't running VRALG7, yet. You are still on VRALF2.
Please try installing ROM Manager from the Google Play store and flashing the latest ClockworkMod Recovery (6.0.1.2) from there. Use that to apply the updates. I tested applying the modified OTA updates using that version of ClockworkMod Recovery.
cj64 said:
You cannot apply the 2nd update until you have successfully applied the 1st update. That is why the file ending QXM.zip, which I assume is unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip, fails. You aren't running VRALG7, yet. You are still on VRALF2.
Please try installing ROM Manager from the Google Play store and flashing the latest ClockworkMod Recovery (6.0.1.2) from there. Use that to apply the updates. I tested applying the modified OTA updates using that version of ClockworkMod Recovery.
Click to expand...
Click to collapse
just purchased and installed ROM Manager (required a $2 purchase to flash to the 6.0.1.2 recovery) will report back.
as a side note today I noticed my email application is totally missing (the stock one) The only thing I've done in the last 2 days is attempt to install this update. Any ideas how I can get that .apk back?
---------- Post added at 08:19 PM ---------- Previous post was at 07:39 PM ----------
No dice
updated to the latest CWM recovery
select the 1st zip file, and tried installing it (via Rom manager GUI and through recovery)
get the following
assert failed: apply_patch_check9"/system/SW_Configuration.xml", "2b7f (really really long string of numbers and letters), "a7f5d (really really long string again) Error in /sdcard/Download/FILENAME ending in 1ZHM.zip
Status 7
Installation aborted
hu? upon rebooting, I get the message Android is upgrading and it still is not updated.
solidage said:
just purchased and installed ROM Manager (required a $2 purchase to flash to the 6.0.1.2 recovery) will report back.
as a side note today I noticed my email application is totally missing (the stock one) The only thing I've done in the last 2 days is attempt to install this update. Any ideas how I can get that .apk back?
Click to expand...
Click to collapse
Not sure what would cause that app to disappear. Check your PMs. Didn't know it cost $2 just to flash the recovery, sorry.
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
1. Take a backup of your Current rom first
2.download any cm12 rom and place it in the root of the SD card
3. Boot in to twrp recovery and do factory reset
4. Flash CM12 rom
5. Flash donkey kernel..
6.reboot and check..
7. If not working, restore your backup
But this doesn't work for the Official Cyanogenmod Nightly.
modifan14 said:
But this doesn't work for the Official Cyanogenmod Nightly.
Click to expand...
Click to collapse
How long did you wait on the first boot? It can take like...10 minutes.
modifan14 said:
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
Click to expand...
Click to collapse
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Quentinga said:
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Click to expand...
Click to collapse
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
andogeek10 said:
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
Click to expand...
Click to collapse
No: my log
flash history
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
Opening update...
Installing update...
E: Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
Click to expand...
Click to collapse
cwm log
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
I : Update location : /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
Opening update...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 249856 blocks
blkdiscard failed: Invalid argument
writing 111672 blocks of new data
lseek64 failed: Invalid argument
E : Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
I : using /data/media for /sdcard/0/clockworkmod/ .last_install_path.
I : Cannot load volume /misc.
Return to menu with any key.
Click to expand...
Click to collapse
That's because of the updated partition table. I also had the same error on GPE 4.4.4. Try flashing vanir, it worked for me.
TWRP Recovery 3.0.2-X for Galaxy S5 LTE-A X3. Built from latest TWRP sources.
Builds uploaded after V5 are now labeled as 3.0.X-0, 3.0.X-1, 3.0.X-2...
Forgive me for embedding my id(kykint) into version label, I thought I needed to distinguish this from other developers' builds.
/* Requirements */
- Galaxy S5 broadband LTE-A (SM-G906S/K/L)
- Compatible with KK, LP, MM
/* Known issues */
Old versions (V1~V4)
- MTP might fail to work in TWRP, go to Mount option and turn off MTP feature
- Brightness control not working for kitkat users
Latest builds
- None yet.
/* Installation */
- Flash zip on custom recovery, if you already have one installed
- or flash tar through odin
- For MM users who have already flashed CallMESuper's TWRP, flash stock marshmallow firmware through odin first.
/* How to root marshmallow */
Download and flash latest SuperSU beta zip from Chainfire's thread.
/* Download */
MM : Latest builds (3.0.2-1)
MM(old) : Old version (V5) (kccat6 port)
KK & LP : Old versions (V1 ~ V4) (trlte port)
Thanks! Been using version 2 for a while. I can see on your site you also ported a new ROM :highfive:
Audioboxer said:
Thanks! Been using version 2 for a while. I can see on your site you also ported a new ROM :highfive:
Click to expand...
Click to collapse
Check out the NovaROM thread, G906 support has been added
what works for SM-G901F, Galaxy S5 4G Plus
andreMusers said:
what works for SM-G901F, Galaxy S5 4G Plus
Click to expand...
Click to collapse
This is not for G901F. You can use the port of TWRP v2.8.5.0 for G901F by sktjdgns1189.
kykint said:
This is not for G901F. You can use the port of TWRP v2.8.5.0 for G901F by sktjdgns1189.
Click to expand...
Click to collapse
where I can get the link TWRP v2.8.5.0 for G901F by sktjdgns1189.
thanks
andreMusers said:
where I can get the link TWRP v2.8.5.0 for G901F by sktjdgns1189.
thanks
Click to expand...
Click to collapse
From one of his threads. The server's dead at the moment.
Thx for the download. I've flashed V2 successfully on my G906L. Odin states "succeed". But when booting to recovery (home+vol up + power) for half a second the "dead android" shows up (the fail message) and stock recovery shows up. Anthing I missed?
Edit: Below the dead android I can read the message "no command"
Edit2: Have searched Google and found a solution in this post: http://forums.androidcentral.com/sa...covery-no-command-then-error.html#post4167479
1. Flash recovery through Odin, but untick "Auto Reboot"
2. Disconnect phone from USB and turn off (e.g. take battery out)
3. Next boot directly go to recovery by pressing home, vol down and power
4. Recovery shows up. Fron then on every time when booting into it. Enjoy
Updated for MM.
@kykint recovery v5 can not flash any rom . status 7 error , i flash rom on recovery old work ok . recovery v5 problem ?
kotobodj said:
@kykint recovery v5 can not flash any rom . status 7 error , i flash rom on recovery old work ok . recovery v5 problem ?
Click to expand...
Click to collapse
Which ROM?
kykint said:
Which ROM?
Click to expand...
Click to collapse
Rom port 901f . And deodex stock
laivu said:
Rom port 901f . And deodex stock
Click to expand...
Click to collapse
Can you give me the link?
https://drive.google.com/file/d/0B8_79V8DPPPdZzNfUUJHd1dva1E/view?usp=sharing port from stock 901f
And material 7 v1.1 port from g901f. Recovery of super id kaccat6 .
https://drive.google.com/uc?id=0B0EQlHntuOXCbXZsM1JZaVhWOWs&export=download
laivu said:
https://drive.google.com/file/d/0B8_79V8DPPPdZzNfUUJHd1dva1E/view?usp=sharing port from stock 901f
And material 7 v1.1 port from g901f. Recovery of super id kaccat6 .
https://drive.google.com/uc?id=0B0EQlHntuOXCbXZsM1JZaVhWOWs&export=download
Click to expand...
Click to collapse
Okay I'll check that out.
Thanks you
laivu said:
https://drive.google.com/file/d/0B8_79V8DPPPdZzNfUUJHd1dva1E/view?usp=sharing port from stock 901f
And material 7 v1.1 port from g901f. Recovery of super id kaccat6 .
https://drive.google.com/uc?id=0B0EQlHntuOXCbXZsM1JZaVhWOWs&export=download
Click to expand...
Click to collapse
Aren't those roms for the g901f specifically, and not the g906? AFAIK the g906 doesn't have any custom roms based on the new MM bootloader - perhaps mokee might when CallMESuper has the time to update it.
bud7dha said:
Aren't those roms for the g901f specifically, and not the g906? AFAIK the g906 doesn't have any custom roms based on the new MM bootloader - perhaps mokee might when CallMESuper has the time to update it.
Click to expand...
Click to collapse
This rom g901f port for g906skl. You cam flash via twrp by callmesuper. Not twrp by kykint.
laivu said:
This rom g901f port for g906skl. You cam flash via twrp by callmesuper. Not twrp by kykint.
Click to expand...
Click to collapse
This rom is not ported for the g906 and neither is @Tkkg1994's StockRom V2.0. Even with a successful flash, they won't work properly, if at all on our model. Status 7 TWRP error means the rom is not compatible with your device (i.e., failed assert). It doesn't mean TWRP can't flash a rom. The only way to know for sure is to flash a rom specific to the g906; if the flash still fails, then it could be a TWRP recovery specific problem. Another way is to change the first three lines of the updater script in the rom's META-INF folder to match our device, replacing kccat6 with lentislte.
The following excerpts are from Material7 V1.2 by @Golgotronx
Updater-script -->
assert(getprop("ro.product.device") == "kccat6" || getprop("ro.build.product") == "kccat6" || getprop("ro.product.name") == "kccat6" ||
getprop("ro.product.device") == "kccat6xx" || getprop("ro.build.product") == "kccat6xx" || getprop("ro.product.name") == "kccat6xx" ||
abort("This package is for "kccat6,kccat6xx" devices; this is a "" + getprop("ro.product.device") + "".") ;
assert(getprop("") == "" ||
Build.prop-->
ro.build.display.id=Material7 V1.2 by Golgotronx
ro.build.version.incremental=G901FXXU1CPE1
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-05-01
ro.build.version.base_os=
ro.build.date=Tue May 3 20:05:48 KST 2016
ro.build.date.utc=1462273548
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5606
ro.build.tags=release-keys
ro.build.flavor=kccat6xx-user
ro.product.model=SM-G935F
ro.product.brand=samsung
ro.product.name=kccat6xx
ro.product.device=kccat6
As you can see, this rom was cooked for a G901F. @DracoPiece asked if the g906 will get support and has yet to get a reply from the dev: http://forum.xda-developers.com/gal...18-05-2016-t3381302/post66950945#post66950945
i don't think so . i'm deodex stock firmware g906s use superr kitchen , recovery for kykint status 7 error when i flash zip stock deodex , older recovery ( philz,twrp 2.8 , twrp 3.0.2 of callmesuper ) working fine. but i don't understand some app force close ( sms,smartmanager,syscop)
Download the S251 update package from this link.
Rename the file to update.zip and move it to the root of your SD card (not internal storage). Boot into stock recovery and update.
If you have TWRP, it will not work. If you have root or magisk, it will not work. You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Do I have to uninstall magisk first ?
Sutcliffe9 said:
Do I have to uninstall magisk first ?
Click to expand...
Click to collapse
You can try that. If the update fails, you'll have to reflash the stock boot image as the update process might detect a modified boot image. Do you have the boot.img file for S244 ?
Thanks, I have the s244 boot image. I will give it a go tomorrow.
Thanks for uploading this.
Hm, update built on the 7th of November but only contains the 1st of November security updates. Google released further updates on the 5th and 6th of November, with the 6th November update fixing the very serious WPA2 'Krack' issues.
At least this update fixes the blueborne stuff.
Sorted ?
Sutcliffe9 said:
Sorted
Click to expand...
Click to collapse
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.
Murtie said:
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.
Click to expand...
Click to collapse
You only have one option. You need to re-install the full S244 ROM from this thread: https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
Follow the steps but DO NOT FLASH USERDATA or you will lose all your existing apps and settings. This will restore your system to stock configuration then you should be able to update.
It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Is there any chance of getting android oreo update bro
somenderjangra said:
Is there any chance of getting android oreo update bro
Click to expand...
Click to collapse
nope.
Sutcliffe9 said:
It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
I have doing this but the same error. installation failed
Maybe i have not the right image
Do you have the boot.img file?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Im using this stock rom>
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel
Where does this file come from? How can we be sure it is safe? Verified official?
So, any verdict on this new update for the people that did update to it?
I am on china ROM f 04. So far so good
nimishbj said:
I am on china ROM f 04. So far so good
Click to expand...
Click to collapse
What's your sot? Can you show the battery graph and apps used during those time?
in what region does the update pushed already? as now, global (france) not yet available.
Android 13 F.02 INDIA is still in Beta.
A13 F.03 INDIA is Official Release (Non-Beta)
Link : https://gauss-componentotacostmanua...23/01/11/5f681b91cb444bc0bbcdf53c3c9bd680.zip
Alifirdaus said:
in what region does the update pushed already? as now, global (france) not yet available.
Click to expand...
Click to collapse
India and China roms had it for a few days now.
Good news everyone! I've just received the update for my devices official realme ui 4 ending with f.02 for global rom. As usual, triggering the update using vpn connected to france/italy. If you still cannot get it, please clear cache and data for software update and try again while connected to vpn. cheers!
I received the official update here in Greece ui 4 ...... f.02, but after the update I get the orange state warning when powering on the phone. I checked another thread on how to fix it, but I can not get the phone to boot in edl mode as per the other thread instructions. Any help will be greatly appreciated.
Edit: I finally managed to boot in EDL mode and completed the process with success.
Alifirdaus said:
Good news everyone! I've just received the update for my devices official realme ui 4 ending with f.02 for global rom. As usual, triggering the update using vpn connected to france/italy. If you still cannot get it, please clear cache and data for software update and try again while connected to vpn. cheers!
Click to expand...
Click to collapse
hey all, I am on Global ROM (Russia) and still not having any updates yet anyone got an update on RUSSIA ROM yet. Please share how to upgrade.
THanks so much and have a nice day!
gotask said:
Android 13 F.02 INDIA is still in Beta.
A13 F.03 INDIA is Official Release (Non-Beta)
Link : https://gauss-componentotacostmanua...23/01/11/5f681b91cb444bc0bbcdf53c3c9bd680.zip
Click to expand...
Click to collapse
How flash this?
gefrappo96 said:
How flash this?
Click to expand...
Click to collapse
Use Latest TWRP : https://www.pling.com/p/1922292/
1st File
Unzip recovery.img then flash TWRP
fastboot flash recovery recovery.img
Then after flashing twrp - format data yes, then Install flash the zip file wait for sometime then after flash complete
reboot device
gotask said:
Use Latest TWRP : https://www.pling.com/p/1922292/
1st File
Unzip recovery.img then flash TWRP
fastboot flash recovery recovery.img
Then after flashing twrp - format data yes, then Install flash the zip file wait for sometime then after flash complete
reboot device
Click to expand...
Click to collapse
Link is F.03?
gefrappo96 said:
Link is F.03?
Click to expand...
Click to collapse
Yes Official
gotask said:
Yes Official
Click to expand...
Click to collapse
Error flash zip
gefrappo96 said:
Error flash zip
Click to expand...
Click to collapse
What error shown share screenshot .... and which version of phone did you purchase from where ?
Alifirdaus said:
Good news everyone! I've just received the update for my devices official realme ui 4 ending with f.02 for global rom. As usual, triggering the update using vpn connected to france/italy. If you still cannot get it, please clear cache and data for software update and try again while connected to vpn. cheers!
Click to expand...
Click to collapse
I used Germany Frankfurt and will update now.
I used a vpn set Germany Frankfurt and in 15 minutes it was updated.
Full OTA package RMX3370 F.03 for Europe
Spoiler: OTA info
"googlePatchInfo": "0",
"group": "RMX3370_11.F.03_3030_202301131653",
"id": "63e9900866c961010ecc2365",
"isNvDescription": false,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV44",
"osVersion": "ColorOS 13.0",
"otaTemplateId": "63e5b38266c961010ecc18b3",
"otaVersion": "RMX3370_11.F.03_3030_202301131653",
"paramFlag": 1,
"parent": "ota-template",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0",
"reminderType": 0,
"rid": "6eabe32d-99aa-48ef-978d-021d9fdf2a42",
"securityPatch": "2023-01-05",
"securityPatchVendor": "2023-01-05",
"silenceUpdate": 0,
"status": "published",
"timestampH5": "2023.02.06",
"versionCode": 3030,
"versionName": "RMX3370_11_F.03",
"versionTypeH5": "Official versions"
RMX3370_11.F.03_3030_202301131653
Stano36 said:
Full OTA package RMX3370 F.03 for Europe
Spoiler: OTA info
"googlePatchInfo": "0",
"group": "RMX3370_11.F.03_3030_202301131653",
"id": "63e9900866c961010ecc2365",
"isNvDescription": false,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV44",
"osVersion": "ColorOS 13.0",
"otaTemplateId": "63e5b38266c961010ecc18b3",
"otaVersion": "RMX3370_11.F.03_3030_202301131653",
"paramFlag": 1,
"parent": "ota-template",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0",
"reminderType": 0,
"rid": "6eabe32d-99aa-48ef-978d-021d9fdf2a42",
"securityPatch": "2023-01-05",
"securityPatchVendor": "2023-01-05",
"silenceUpdate": 0,
"status": "published",
"timestampH5": "2023.02.06",
"versionCode": 3030,
"versionName": "RMX3370_11_F.03",
"versionTypeH5": "Official versions"
RMX3370_11.F.03_3030_202301131653
Click to expand...
Click to collapse
i downloaded, and probed install from F02, but not function.
Also i started use the Vpn tool, and Ota update is already have to F03, with germany connect.
Stano36 said:
Full OTA package RMX3370 F.03 for Europe
Spoiler: OTA info
"googlePatchInfo": "0",
"group": "RMX3370_11.F.03_3030_202301131653",
"id": "63e9900866c961010ecc2365",
"isNvDescription": false,
"isRecruit": false,
"isSecret": false,
"noticeType": 0,
"nvId16": "NV44",
"osVersion": "ColorOS 13.0",
"otaTemplateId": "63e5b38266c961010ecc18b3",
"otaVersion": "RMX3370_11.F.03_3030_202301131653",
"paramFlag": 1,
"parent": "ota-template",
"realAndroidVersion": "Android 13",
"realOsVersion": "ColorOS 13.0",
"reminderType": 0,
"rid": "6eabe32d-99aa-48ef-978d-021d9fdf2a42",
"securityPatch": "2023-01-05",
"securityPatchVendor": "2023-01-05",
"silenceUpdate": 0,
"status": "published",
"timestampH5": "2023.02.06",
"versionCode": 3030,
"versionName": "RMX3370_11_F.03",
"versionTypeH5": "Official versions"
RMX3370_11.F.03_3030_202301131653
Click to expand...
Click to collapse
Do you have Global version full firmware zip ? Need it.