Doesn't seem to be EMUI 4.1, but it is an update nonetheless. Other phones have it worse.
- Dual SIM: (B604) - OTA and FULL
- Single SIM: (B605) - OTA and FULL
CHANGELOG:
This update improves system security with Google security patches.
[Optimizations]
Improved device security with Google security patches.
[Update notes]
1. This update will not erase your personal data, but we recommend that you back up any important data before updating.
2. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
Click to expand...
Click to collapse
You can always find new updates with Huawei Firmware Finder, or on this page.
INSTALLATION:
OTA: You need to have stock recovery. you will extract the UPDATE.APP from the .zip and put that in a folder called "dload" in your phone's SD card. Now you can either:
Dial *#*#2846579#*#* in the stock phone app, and go Software Upgrade > SDcard upgrade or
Shutdown the phone, and then hold POWER, and both the VOL buttons until the EMUI update starts
FULL:
You can flash the update.zip in TWRP. It will show a small error but it's fine.
You can also extract the partitions boot, cust, system with Huawei Update Extractor (usage instructions in the forum) and flash with fastboot through an unlocked bootloader (HOW DO I DO THAT?)
If you have stock recovery you can extract the UPDATE.APP from the .zip and put that in a folder called "dload" in your phone's SD card. Now you can either:
Dial *#*#2846579#*#* in the stock phone app, and go Software Upgrade > SDcard upgrade or
Shutdown the phone, and then hold POWER, and both the VOL buttons until the EMUI update starts
NOTES:
By the way, you can try this method to get better ROMs on this phone. You can find ROMs for these devices that Huawei gives better updates to, and flash them with TWRP, but they may have stuff that doesn't work. E.g. CAM phones don't have NFC so you won't get NFC support with their ROM.
Isn't the ALE-L21C432 that is needed ?
Igl0 said:
Isn't the ALE-L21C432 that is needed ?
Click to expand...
Click to collapse
It's a typo. Anyhow the c432 refers to europe region i think. if your phone is not carrier locked you can install whatever region you want, not with the official method though, only fastboot or TWRP
I just hop in here to remind everyone that this ROM won't pass Safety Net at this time. You'll have to wait until it is releases officially. And that will be on the beginning of the next month.
Also: This is a leaked build, so it may not be final. Which means that this build may not include all security updates for August. Tbh I'm starting to think that this is all just fake news. The security patch from Google wasn't releases yet, it never is this early. Maybe Huawei is just making their customers think they got a supported device, but actually they are just changing one line in build.prop.
Vinnipinni said:
I just hop in here to remind everyone that this ROM won't pass Safety Net at this time. You'll have to wait until it is releases officially. And that will be on the beginning of the next month.
Also: This is a leaked build, so it may not be final. Which means that this build may not include all security updates for August. Tbh I'm starting to think that this is all just fake news. The security patch from Google wasn't releases yet, it never is this early. Maybe Huawei is just making their customers think they got a supported device, but actually they are just changing one line in build.prop.
Click to expand...
Click to collapse
That's not allowed... Google can release early security it patches only for some phones, and happily, it seems that our old p8 lite is with them.
@JpegXguy can you please give me the boot.img of b604? I would appreciate!
D1stRU3T0R said:
That's not allowed... Google can release early security it patches only for some phones, and happily, it seems that our old p8 lite is with them.
@JpegXguy can you please give me the boot.img of b604? I would appreciate!
Click to expand...
Click to collapse
Google releases universal security patches, but NOT this early. If it is releases already, you should be able to find it on the internet.
D1stRU3T0R said:
That's not allowed... Google can release early security it patches only for some phones, and happily, it seems that our old p8 lite is with them.
@JpegXguy can you please give me the boot.img of b604? I would appreciate!
Click to expand...
Click to collapse
The boot image is in the attached zip. I tried a ROM from the CAM-L21 phone, which gets EMUI 4.1 updates plus secutity patches. It's a good ROM but themes don't apply at all for some reason. Other than that it's fast and the small improvements of 4.1 are welcome
Vinnipinni said:
Tbh I'm starting to think that this is all just fake news. The security patch from Google wasn't releases yet, it never is this early. Maybe Huawei is just making their customers think they got a supported device, but actually they are just changing one line in build.prop.
Click to expand...
Click to collapse
Surely that's illegal right? And the OTA is like 120+ MB, I doubt it's just a line change
JpegXguy said:
Surely that's illegal right?
Click to expand...
Click to collapse
I think it is. But it wouldn't be the first time huawei doesn't stick to rules and laws. I just can't imagine that Google would release the security patch of August this early. There is still to much time until the month end and it gets released officially. There is still a lot of time for more exploits and whatever to show up. I don't think Google would do this.
Edit: I just did a little search, there was nothing on the internet. The latest is from July.
Vinnipinni said:
I think it is. But it wouldn't be the first time huawei doesn't stick to rules and laws. I just can't imagine that Google would release the security patch of August this early. There is still to much time until the month end and it gets released officially. There is still a lot of time for more exploits and whatever to show up. I don't think Google would do this.
Edit: I just did a little search, there was nothing on the internet. The latest is from July.
Click to expand...
Click to collapse
Same, i questioned Huawei about this, didn't gaved a clear response... And when ibguestioned again, they can't even respond xd but what illegal they did in the past?
D1stRU3T0R said:
Same, i questioned Huawei about this, didn't gaved a clear response... And when ibguestioned again, they can't even respond xd but what illegal they did in the past?
Click to expand...
Click to collapse
On the bright side, next RROS update might be stable enough for daily use
Hello there, I want to flash this ROM on P8 Lite, I m rooted & TWRP recovery 3.0.2.0 is installed. Currently I m on BalongC52B311. Is it ok to go ahead or may I be end up in Bootloop/Bricked. So plz respond.
Thanks
Khugiani said:
Hello there, I want to flash this ROM on P8 Lite, I m rooted & TWRP recovery 3.0.2.0 is installed. Currently I m on BalongC52B311. Is it ok to go ahead or may I be end up in Bootloop/Bricked. So plz respond.
Thanks
Click to expand...
Click to collapse
First of all, update TWRP. You can flash the full update.zip in TWRP, maybe you need factory reset though. try first without
Related
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.
http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.
lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.
stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.
anybody updated? Any improvement (battery or ram) or bug?
changelog:
This update improves system security with Google security patches. [Optimizations] Improved device security with Google security patches. [Update notes] 1. This update will not erase your personal data, but we recommend that you back up any important data before updating. 2. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
raniero1 said:
anybody updated? Any improvement (battery or ram) or bug?
changelog:
This update improves system security with Google security patches. [Optimizations] Improved device security with Google security patches. [Update notes] 1. This update will not erase your personal data, but we recommend that you back up any important data before updating. 2. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
Click to expand...
Click to collapse
Tried updating today but still getting errors while flashing the first update.zip file.
jonezie said:
Tried updating today but still getting errors while flashing the first update.zip file.
Click to expand...
Click to collapse
I got the same problem
Same problem trying to upgrade... ?
There's a problem with the "update.zip" file. Some files are missing. You can see this error when flashing with TWRP Recovery.
Huawei is not responsible to FIX ANYTHING! Unofficial firmwares, test firmwares, beta firmwares, call it like you want, downloaded from their servers, without their knowledge?!? What do you want exactly?
Only people from Huawei knows why these files are uploaded at all, who must use them and for what to use them! Maybe there is a reason to be like that, so someone not to BROKE his phone!
When there is an update you will see it in Setting or Hicare app! Nowhere else! Period!
Just checked firmware finder and seems like they removed it.
amonev said:
Huawei is not responsible to FIX ANYTHING! Unofficial firmwares, test firmwares, beta firmwares, call it like you want, downloaded from their servers, without their knowledge?!? What do you want exactly?
Only people from Huawei knows why these files are uploaded at all, who must use them and for what to use them! Maybe there is a reason to be like that, so someone not to BROKE his phone!
When there is an update you will see it in Setting or Hicare app! Nowhere else! Period!
Click to expand...
Click to collapse
The files are just update files on their servers, nothing to be so worried about, mate. No need to get your knickers in a knot.
Wait for the Full-Update PV file if you want to be able to flash it with success using the TWRP recovery (B383-B386). I got B383 working as the PV file which contained both the full update with two files.
Here you can find a list of all Huawei firmware for the ALE-L21.
Huawei is so far staying true to updating the phone, at least with security patches. I respect that.
Official links for download:
Dual SIM: FULL or OTA
and
Single SIM: FULL or OTA
How to install:
Official method
- Put the UPDATE.APP from the .zip in "dload" folder in root of SD card
- Make backup (won't be needed normally)
- Install stock recovery (you can extract the recovery image of this build with Huawei Update Extractor and use fastboot to flash it)
- Wipe data/factory reset
- Hold POWER, VOLUME UP and VOLUME DOWN at the same time. The update process will start.
Alternatively, you can dial *#*#2846579#*#* and select: Software Upgrade > SD card Upgrade > confirm the installation
(Also you can flash the attached zip to get "Local Update" option back in the upgrade area of settings.
Apparently you also can flash the FULL zip in TWRP.
Changelog:
This update improves system security with Google security patches. [Optimizations] Improved device security with Google security patches. [Update notes] 1. This update will not erase your personal data, but we recommend that you back up any important data before updating. 2. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
Click to expand...
Click to collapse
Abandoned phone, sadly :/ no more real updates incoming, ffs
D1stRU3T0R said:
Abandoned phone, sadly :/ no more real updates incoming, ffs
Click to expand...
Click to collapse
They are still delivering important security updates. That's better than some other manufacturers. Don't expect them to update the phone to a new version, they don't profit from it anymore and it's costly work. At least there's some custom development for this device, though we might never get stable Nougat. We can only hope and support the developers, help with logs etc
JpegXguy said:
They are still delivering important security updates. That's better than some other manufacturers. Don't expect them to update the phone to a new version, they don't profit from it anymore and it's costly work. At least there's some custom development for this device, though we might never get stable Nougat. We can only hope and support the developers, help with logs etc
Click to expand...
Click to collapse
They could release now sources... Like honor did.
European or Russian version?
D1stRU3T0R said:
They could release now sources... Like honor did.
Click to expand...
Click to collapse
Indeed, they could be friendlier towards developers
Giuseppe300715 said:
European or Russian version?
Click to expand...
Click to collapse
C432 is European region
single sim?
Goktuz said:
single sim?
Click to expand...
Click to collapse
Would be B603 but I don't see it in the firmware list. You can convert your phone to dual SIM though (search xda)
Goktuz said:
single sim?
Click to expand...
Click to collapse
The only existing version is compatible with emui sim and b601
Just saying, you won't pass Safety net until 1st of July. I'd recommend to stay at B600 until then.
Vinnipinni said:
Just saying, you won't pass Safety net until 1st of July. I'd recommend to stay at B600 until then.
Click to expand...
Click to collapse
Not necessarily. Previous update was relased around 17 or 18th of May and I had certification in less than a week
JpegXguy said:
Here you can find a list of all Huawei firmware.
Huawei is so far staying true to updating the phone, at least with security patches. I respect that.
Official links for download: FULL OR OTA
Click to expand...
Click to collapse
So... How do we install it ? Trought TWRP ?
Igl0 said:
So... How do we install it ? Trought TWRP ?
Click to expand...
Click to collapse
What I did (I think you can flash the partitions themselves with fastboot though)
- Put the UPDATE.APP in "dload" folder in root of SD card
- Make backup (won't be needed normally)
- Install stock recovery (you can extract the recovery image of B602 with Huawei Update Extractor and use fastboot to flash it)
- Wipe data/factory reset
- Hold POWER, VOLUME UP and VOLUME DOWN at the same time. The update process will start.
Now, it has to be noted that like the comment above said, SafetyNet won't pass for some time (haven't tested it) but I don't use apps that check for it so I'm fine.
Igl0 said:
So... How do we install it ? Trought TWRP ?
Click to expand...
Click to collapse
Thats possible and probably the fastest way.
Vinnipinni said:
Thats possible and probably the fastest way.
Click to expand...
Click to collapse
You need stock recovery. Don't do official updates with a custom recovery.
JpegXguy said:
You need stock recovery. Don't do official updates with a custom recovery.
Click to expand...
Click to collapse
I always do them in TWRP. Huawei included an update script to flash their updates.
Vinnipinni said:
I always do them in TWRP. Huawei included an update script to flash their updates.
Click to expand...
Click to collapse
Never heard of that. You got any links? If it works that's interesting
JpegXguy said:
Never heard of that. You got any links? If it works that's interesting
Click to expand...
Click to collapse
Just flash any update file through TWRP. I bet that B602 will work.
Vinnipinni said:
I always do them in TWRP. Huawei included an update script to flash their updates.
Click to expand...
Click to collapse
This. I always update with update.zip through TWRP and no problem at all.
On firmware finder is a new EMUI update available, check:
https://pro-teammt.ru/en/online-firmware-database-ru/?firmware_model=WAS-&firmware_page=0
It's available for many variations of the device, however not for was-lx1a c432, which is the device I have at hand atm...
Of course Huawei support doesn't know anything!
Has someone with a fitting variation of the p10 lite received the update already by normal OTA?
I could flash another cust (c55) via HWOTA and everything was fine, except it showed the build as 8.0.0.46 (1HAM) instead of 8.0.0.393...
Hence I reverted via HiSuite to Nougat and updated all the way to 8.0.0.390 from 2019, where it stops for lx1a with cust c432 - which surprises me as I thought that the free EU version (dual/4GB) certainly had it's own build up and running, however no, doesn't look like it...
It should be possible to manually flash the updated partitions via fastboot individually or again use HWOTA again and ignore the wrong build number as THIS most likely will be the very last update for this 3+ years old device anyway.!
Not sure if anyone is still listening here anymore, didn't see any recent conversations here in 4 to 6 weeks I'm playing with this device :cyclops: which is of course kinda normal for aged phones like this one
Edit:
As suggested in this thread:
https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946
My lx1a is in fact a l21a (c432) and firmware is already available, I'll check it out now, however it's still weird as firmware finder usually suggests the right firmware by searching for lx1a, never before I had to look up l21a...
Gonna report about success later on!
Edit2: when initializing the update via dailer it says the update is incompatibile, even though I setup the dload folder according to the guidelines (zip not update.app) and have the correct package L21A_EU - never gonna understand the way Huawei thinks with this...
Forced update doesn't work for same incompatibility reasons!
Edit3: just tried using update.app files instead of zips but no chance, still errors out.
Also tried firmware finder erecovery DNS method but this gives me a "none authorized update", like using the l21a package on the lx1a isn't supposed to work... I'm running out of ideas!
Last Edit:
Nothing worked so I unlocked the Bootloader to use HWOTA8 to update to package (full) L21AC432B394 and it perfectly worked...
Now finally I'm on 8.0.0.394 c432 with July 2020 security patch and little added functionality, kernel was compiled on 15th of July 2020 - 3+ years and a update has been released, that's actually a big surprise considering it's Huawei and a low level device!
Greetings Sam
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
roxkiller said:
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
Click to expand...
Click to collapse
It didn't change anything obvious, same UI, same experience - Huawei today (assistant app) was added, however no one is forced to use it BUT the most important feature in this update for me is the the 1+ year of security patches, remember it's March 19 to July 20 - I mean it's still Oreo but at least up to date on a security level, system, vendor, kernel, pretty much all parts where updated and improved, it even feels little faster but this could also be because of the factory reset I did to flash the update (unlocked and locked the device in order to use HWOTA8)...
If you want details install firmware finder, search for WAS-L and check out the changelog of 8.0.0.394, maybe the link above provides a changelog, don't remember... There is a pretty long changelog, technically this is not only a security update but a functionality update, I just don't remember all aspects of it!
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Why you so eager that you can't wait a few days?
It's available now.
it has been up for about 5 hours
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
Layoffs, poor employee morale, and Google moving away from innovation and a move to deplete resources from projects/divisions that are not returning enough profit.
If you've ever had to deal with Google customer "service" for any technical issues before, you already know why. Sometimes you get lucky and find a unicorn of a tech to help, but it's usually an infuriating mess dealing with them.
But, to be honest, I'd rather have a delayed update than a rushed and buggy update. Quality control is important.
kevinireland11 said:
How is Google so slow now at releasing things? They only have a few phones to update, my Samsung's are always start of each month without fail lol
Click to expand...
Click to collapse
After all we are all just humans ... they sure have their reasons
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
No problems here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
Rooted, Kirisakura Kernel, Apr. update. All good here.
JimSmith94 said:
I usually wait to see posts from people that installed the update with or without problems but I haven't found any for the April update. Has anyone had any issues with installing the April update or using 33.0.3 of platform tools?
Click to expand...
Click to collapse
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it???
The mobile phone system is running normally.
Click to expand...
Click to collapse
Assuming you're rooted, that message is normal and can be ignored.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored.
Click to expand...
Click to collapse
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
JimSmith94 said:
Assuming you're rooted, that message is normal and can be ignored I am root and magisk on my device..
Click to expand...
Click to collapse
Lughnasadh said:
The red eio corruption message isn't normal, but it can be ignored. You may be thinking of the "Your bootloader is unlocked....." message.
It usually takes an update to get rid of that message. Flashing back to an earlier month and then updating again should get rid of the message. You can also just ignore it until the next update.
Sometimes flashing an old boot image (your phone likely won't boot) and then flashing a newer boot image gets rid of that message as well.
Click to expand...
Click to collapse
I refresh init_boot.img or prompt this message.
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
ozyk100 said:
Can someone please explain to me....
On official site for factory images there is only one factory image for april update as far as I can see.
(TQ2A.230405.003.E1, Apr 2023)
Does the E1 on the end means that it's for specific carrier?
If it is, does it matter for us that have unlocked phones?
Click to expand...
Click to collapse
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
simplepinoi177 said:
No, the E1 does not mean that -- in the past, the ending of the version number can indicate something like that, but if there is no other monthly version, it's safe to say that is not the case. Linked below is a post on how the version numbers are determined and/or how to read them...
When there is no carrier specific version of firmware updates, it means the factory firmware image is applicable to all. If there is any specific version, it is identical in most ways, it just has special data/setup/applications(not apps or programs) that usually help the device's radio connect to the carrier's network optimally -- and from what I've read somewhere, all subsequent updates have said modifications included in them anyways. But if you're not certain, always flashing the "global" version is a safe bet; at worst, you're just not implementing the optimal "code" for the device's radio to the carriers network is all.
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for that explanation, I'll read up on it from the provided link.
LHui said:
update or using 34.0.0 of platform tools is a failure Switch back to 33.0.3 successfully :13 (TQ2A.230405.003.E1), but the system boots and prompts Your device is corrupt. It can’t be trusted and may not work properly. How can I solve it??? Please help me, thanks.
The mobile phone system is running normally.
Click to expand...
Click to collapse
I had the same issue, but everything works normally without any issues. I regularly flash custom roms and factory images, so if you still want to fix this issue, restore a factory image using the Android flash tool.
Any info on whether the fingerprint scanner is being fixed or at east bettered with this?