Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot
Well, that's definitely new!
tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places át lower screen part, they changed the circld into square.
More impressions After testing.
CLT-L29C432B131 Camera
Click to expand...
Click to collapse
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???
Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine
halleyrokz said:
Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine
Click to expand...
Click to collapse
From FirmwareFinder:
This update optimizes system performance and stability.
Optimizes power consumption for longer usage.
Improves system performance and stability for smoother operations.
Optimizes the wallpaper display for a better experience.
Fixes an issue where the other party's voice was occasionally delayed when answering calls while using OK Google.
1. This update will not erase your personal data, but we recommend that you back up any important data before updating.
2. The system will restart after the update. This will take about 5 minutes.
3. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
tsiglas said:
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???
Click to expand...
Click to collapse
OK. Sure.
But it will take time.
I'm not a professional shooter, so basically I probably won't notice the differences too fast.
One thing I have observed is that the portrait selfie mode was improved, it's more natural.
Others I will test.
But again: with HuRupdater you can update easely.
(downloading 3 of 4 files from update packages: the choice is between clt-l09 and clt-l29, after that renaming and flash via twrp. See corresponding thread)
Interesting.. so it seems indeed that many of the under the hood changes are not always mentioned in the change log.
Yeah please keep us posted on the camera improvements and performance and power consumption.
tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot
Click to expand...
Click to collapse
I updated it to it yesterday but besides the zoom button form nothing changed the selfie camera still creey as before and the video recording also no stabilisation for 4k and no 60 f0s for 4k, huawei is doing nothing
tamaskurti said:
So far they have included camera improvements.
Click to expand...
Click to collapse
How about the front-camera, can you turn off beauty mode? i set it to 0 but still on almost the same.
I've just tried to update using the HuRUpdater method but wasn't able to boot afterwards. Tried flashing twice but it just wouldn't boot to system. I've restored the TWRP backup I made before flashing and got back into system, now settings says I'm on .131 but I can't be if I just restored a .128 backup, right?
What's everyone's update method? Did you place custom recovery in the folder too or flash without? Wipe cache/dalvik after? Boot to system first before flashing Magisk or just flash directly after HuRUpdater script?
Want to try again but just wanted to check if I've missed something? Thanks!
just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches
kaiowas82 said:
just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches
Click to expand...
Click to collapse
Reckon it would be safe to flash using the NoCheck Recovery method?
danifilth4king said:
Reckon it would be safe to flash using the NoCheck Recovery method?
Click to expand...
Click to collapse
i don't know mate, i used hurupdater, as i said before, and all went smooth...
kaiowas82 said:
i don't know mate, i used hurupdater, as i said before, and all went smooth...
Click to expand...
Click to collapse
Did you use official or unofficial TWRP?
You need to use unofficial twrp as only that one can decrypt storage (remove security settings first: no pin/ fingerprint).
danifilth4king said:
Did you use official or unofficial TWRP?
Click to expand...
Click to collapse
unofficial
kaiowas82 said:
unofficial
Click to expand...
Click to collapse
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/
danifilth4king said:
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/
Click to expand...
Click to collapse
I created a new folder with inside the hurupdater script and the three zips downloaded from firmware finder, no recovery img or else.
flashed the script, wiped cache and dalvik and rebooted straight to system.
rebooted to fastboot to reflash the praetoriano recovery, reboot to recovery to flash magisk and that's it.
I'm afraid i cannot help further
I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?
isko01 said:
I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?
Click to expand...
Click to collapse
The cn firmware was updated too to version B123.
Remember, they have different numbers. Ex. Their B123 version is newer than our B131.
Look at production numbers in Fw.
Related
I am not able to understand these white/blue spots across the images. Please see the attached images and zoom in to look in the highlighted areas. It's not dust for sure as I have cleaned the lens and the photos were shot in auto mode (no change in ISO etc). IS there an issue with Nougat beta camera or is my sensor damaged?:crying:
What variant you have (L09 or L04) and which firmware you're running (B1..)?!
I am sorry for hijacking this forum, but I have an Honor V8 variant (the big sized version) with EMUI 5.0. beta. There is no xda forum on this model, hence I posted here. I am not sure if the s/w is the issue as I tried it with other camera apps as well producing the same issue
try a 3rd party camera to see if it is still there, if so try reflash stock rom.
If 3rd party apps don't work, then look if there's an update for your phone
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
yes it is probably a hardware issue, but you will have to flash stock to completely rule out a software issue. back up data using twrp
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Its a 50 50 situation, some early buyers of honor 8 had the same issue, but after an OTA it's gone.
If it's a hardware issue, return it back if you have warranty.
A friend of mine had the same issue but it was fixed after the update.
Neil6684 said:
A friend of mine had the same issue but it was fixed after the update.
Click to expand...
Click to collapse
Do you mean those spots on zooming in? I have been through 2 beta-Nougat updates, but its not yet resolved. I will factory reset over this weekend and check.
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
linom said:
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
Click to expand...
Click to collapse
It's a software issue, don't worry.
If RAW images are fines, then it's just a problem of processing when taking a JPEG photo
An update should fix this
DarkGuyver said:
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Click to expand...
Click to collapse
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
It's better for you, and when you buy a device make sure it's officially supported in your country (like honor 8) .
All the best
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
I'd contact Honor directly and ask them about the problem. Maybe they will release a software patch for it. But I have never heard the Honor 8 had this problem.
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
linom said:
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
Click to expand...
Click to collapse
Unfortunately, we don't know the exact files (libs that are responsible for image processing)
linom said:
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Click to expand...
Click to collapse
You would have to contact Honor directly for instructions on how to restore Marshmallow back onto your device. They will also be able to provide you with a link to the Marshmallow firmware for your device.
Get it while it's hot :
http://en.miui.com/download-320.html
Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Flynhx said:
Anyone have tested this? Is there any improvements from V8.2.1.0 or still prefer the old V8.1.2.0? So, here i am waiting for feedback.
Click to expand...
Click to collapse
senseii said:
I'm on it since this morning, pretty much the same I'd say, the change-log has a few things like swipe to dismiss notifications on lockscreen and a few bugfixes.
Click to expand...
Click to collapse
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
Bet this rom weighs more than an average car....
I was using stock 8.2.1 Global Stable. After auto-updating to 8.2.4, had sound glitches, unlock lag and Telegram bugs I've never seen before. I don't recommend to migrate to this version from 8.2.1.
I haven't had any sound glitches or unlock lag (I don't use telegram).
As for battery life it's great, 2 days use, 6 hours SOT so far and I have 50% battery left (4G on all the time).
Flynhx said:
How is your experience with the temperature & battery life? Can you share some screenshots of your SOT? Did the bugs at V8.2.1.0 finally fixed in V8.2.4.0?
Sent from my Redmi 4 Prime using XDA-Developers Legacy app
Click to expand...
Click to collapse
5th day with the phone. i got it update it to 8.2.4, charged it, unlocked bootloader, installed twrp/root and i had about 10 hours sot during a 3 day period on 2g and a little 3g and wifi disable when screen is off. those 10 hours included a lot of restarts that consume energy a lot of copying things via wifi browsing messenging and a few calls. no problems so far hope i helped.
This update don't bring big changes. Don't understand why you afraid of update. All work's fine including battery life and performances.
Upd:
1. Sound issues and Telegram bugs - no more. One-time glitch?
2. Usual Xiaomi micro-lags when switching apps seem to disappear. So 8.2.4.0 feels way more smooth for me.
3. Battery life - no noticeable changes.
4. MiPicks app added along with annoying ads.
I wonder Why eu version not yet published ?
Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?
BadHappiness said:
Sorry for this silly question, how can i update to 8.2.4 if I have TWRP recovery? Can I just take OTA update or do I need to flash the zip file via TWRP?
Click to expand...
Click to collapse
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).
sas_sas said:
I wonder Why eu version not yet published ?
Click to expand...
Click to collapse
xiaomi.eu is based on the china rom, not the global. they won't release until there's an official release for the CN rom.
senseii said:
You'll have to flash via TWRP cause the OTA uses the built in Xiaomi recovery (which you dont have anymore since you installed TWRP).
Click to expand...
Click to collapse
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?
BadHappiness said:
Thanks for your reply. Another question, do I need wipe anything before flash this rom? And also do ineed to root it again after flash the rom?
Click to expand...
Click to collapse
Yeah you should wipe the cache and davlik cache at least before flashing the new rom. Full wipe would be best.
To get root you'll have to re-flash the super su zip file after you flash the rom.
Re' 8.2.4.0 global
Just did a clean full wipe and flashed epic zip again for another try, though I still have noticeable battery drain.
Thinking of going 8.2.4.(and then uninstalling a few apps n' make a few minor mods for better battery life)
I have twrp installed, read somewhere I can not get rom updates via OTA due to this. (As MIUI recovery is needed for update?) Is that true?
In which case does that mean when there is a new global rom update, and I flash zip in twrp(if that's the case) I would lose my settings and aps? (Guess I would) Or as it's newer/similar global update could I get my settings back from mi cloud or Titanium back up?
Tired of changing roms and then setting up all the apps.
Sorry if this a newbie type question.
Thanks for any info (=
Tried to delete my last post, without luck, found answer/s in other threads (=
The zip file is corrupt
Here is my stock rooted debloated B230 ROM.The rom is debloated to remove the Chinese apps along with a bunch of fixes and mods.
Features:
Magisk Pre Patched B230 boot image
Magisk Manager
Double tap to wake working
Added Video and Music from the International ROM
Updated Google Apps
Deodexed to shrink system size
Removed Touchplus
Added in a few themes
https://www.androidfilehost.com/?fid=1395089523397905233
For those of you with camera issues install this app and set it to permissive:
https://f-droid.org/repo/com.mrbimc.selinux_20171031.apk
ajsmsg78 said:
B227 for the GEM-703L was released on firmware finder. I actually flashed the update.zip in twrp and was able to flash it without an issue. Then I did a factory reset and can confirm I'm now on stock B227. I'm gonna play around with this.
Click to expand...
Click to collapse
Is B227 built on android 6 or 7? Thanks AJ.
mouse723 said:
Is B227 built on android 6 or 7? Thanks AJ.
Click to expand...
Click to collapse
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch but may have other changes as well.
ajsmsg78 said:
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch.
Click to expand...
Click to collapse
Hi, do (double tap to wake) function work on this B227 new rom ? thanks.
LH88 said:
Hi, do (double tap to wake) function work on this B227 new rom ? thanks.
Click to expand...
Click to collapse
Unfortunately, no, not even on the older boot.img. Since I updated to B227 even installing KangVIP Slim double tap to wake doesn't work anymore so I would not update until I can figure this out.
ajsmsg78 said:
It's still Android 6 unfortunately. Kernel security patch is July 2018 though. According to the changelogs it's just a security patch.
Click to expand...
Click to collapse
Is there any further changes beside security changes? Im on a b209 stock build, and im not sure if this gonna be as easy u told for me too or not, upgrading from b112 to 209 was a disaster for me, although now i like 209 much more than that 112.
My device is gem701>gem 703 b112> gem 703 b209
ajsmsg78 said:
Unfortunately, no, not even on the older boot.img. Since I updated to B227 even installing KangVIP Slim double tap to wake doesn't work anymore so I would not update until I can figure this out.
Click to expand...
Click to collapse
thanks.
safseyed said:
Is there any further changes beside security changes? Im on a b209 stock build, and im not sure if this gonna be as easy u told for me too or not, upgrading from b112 to 209 was a disaster for me, although now i like 209 much more than that 112.
My device is gem701>gem 703 b112> gem 703 b209
Click to expand...
Click to collapse
I dont think so. There was firmware, for example the radio that was updated when I flashed the update.zip. You can update to B212 if you want and stay on that.
Normally one can just flash systemless SuperSU or Magisk to patch the boot.img for root but when you do that to any boot.img on the X2 you get app freezes, freezes when charging etc. The only root that works properly is system root but the kernel and boot needs to be patched to allow system root or else it won't boot. I'm not that great with boot images so I've been using the B212 boot that was patched from the HRT Team (KangVIP). If they release a B227 KangVIP or a patched boot.img then I'll start using that boot.img in my next builds.
ajsmsg78 said:
I dont think so. There was firmware, for example the radio that was updated when I flashed the update.zip. You can update to B212 if you want and stay on that.
Normally one can just flash systemless SuperSU or Magisk to patch the boot.img for root but when you do that to any boot.img on the X2 you get app freezes, freezes when charging etc. The only root that works properly is system root but the kernel and boot needs to be patched to allow system root or else it won't boot. I'm not that great with boot images so I've been using the B212 boot that was patched from the HRT Team (KangVIP). If they release a B227 KangVIP or a patched boot.img then I'll start using that boot.img in my next builds.
Click to expand...
Click to collapse
Well thanks for info, but one thing remains here, im sure ive installed TWRP-ENG-6.0-BLACK-BLUE.img after flashing b209 stock, but just checked recovery and saw its twrp 3.2.1.0, are they same? And do u think i get into any trouble if i flash b227? Thanks in advance.
safseyed said:
Well thanks for info, but one thing remains here, im sure ive installed TWRP-ENG-6.0-BLACK-BLUE.img after flashing b209 stock, but just checked recovery and saw its twrp 3.2.1.0, are they same? And do u think i get into any trouble if i flash b227? Thanks in advance.
Click to expand...
Click to collapse
You want the latest twrp in my twrp thread, it's the black light blue version. I would update to B212 and stay there for now or just stay on B209 if you're happy with it.
ajsmsg78 said:
B227 for the GEM-703L was released on firmware finder. I somehow flashed the update.zip in twrp and was able to flash it without an issue. Then I did a factory reset and can confirm I'm now on stock B227. I'm gonna play around with this.
Click to expand...
Click to collapse
This is positive news, though I wish it was a full update.
Since I run TWRP I probably won't get Updater notification for it.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
ajsmsg78 said:
You want the latest twrp in my twrp thread, it's the black light blue version. I would update to B212 and stay there for now or just stay on B209 if you're happy with it.
Click to expand...
Click to collapse
Btw, i installed b227 through twrp and it's working fine, haven't reseted or wiped data yet, if anything comes up I'll have to do a clean wipe
safseyed said:
Btw, i installed b227 through twrp and it's working fine, haven't reseted or wiped data yet, if anything comes up I'll have to do a clean wipe
Click to expand...
Click to collapse
well, a little later i found out it has problem with google services including google play services and play store, i tried many things to fix them but they didnt, and since i use google services very much i decided to go back to b209, and then problems started, i got stuck and phone has bricked, trying to instal b112 so that i can get back to b209 by that way, i hope it works
safseyed said:
well, a little later i found out it has problem with google services including google play services and play store, i tried many things to fix them but they didnt, and since i use google services very much i decided to go back to b209, and then problems started, i got stuck and phone has bricked, trying to instal b112 so that i can get back to b209 by that way, i hope it works
Click to expand...
Click to collapse
I'll make a stock B227 rom with google apps if you want so you can just flash it in TWRP.
ajsmsg78 said:
I'll make a stock B227 rom with google apps if you want so you can just flash it in TWRP.
Click to expand...
Click to collapse
+1
Here you go. Stock B227 Rooted, Lightly Debloated with Google Apps. I left in the stock Chinese Music Player. Kernel is from B212 so root will work. EMUI version is 4.0.3. Double tap to wake does not work in B227. I enabled it but it doesn't work. Why Huawei keeps removing features like that is a mystery to me.
https://www.androidfilehost.com/?fid=3700668719832236050
ajsmsg78 said:
Here you go. Stock B227 Rooted, Lightly Debloated with Google Apps. I left in the stock Chinese Music Player. Kernel is from B212 so root will work. EMUI version is 4.0.3. Double tap to wake does not work in B227. I enabled it but it doesn't work. Why Huawei keeps removing features like that is a mystery to me.
https://www.androidfilehost.com/?fid=3700668719832236050
Click to expand...
Click to collapse
installed this through twrp flash, works fine, multi screen not working, i think hivoice is good to be removed, it doesnt show network type on top of anthena bars, cant tell if it's 2g,3g or 4g! google related apps are not working properly, that is cant sign in using any google account using google apps, phone seems to be slower than normal and maybe a little battery drain(not sure)
safseyed said:
installed this through twrp flash, works fine, multi screen not working, i think hivoice is good to be removed, it doesnt show network type on top of anthena bars, cant tell if it's 2g,3g or 4g! google related apps are not working properly, that is cant sign in using any google account using google apps, phone seems to be slower than normal and maybe a little battery drain(not sure)
Click to expand...
Click to collapse
Do a wipe and flash again, the Google apps are working fine for me. I will release another build tonight with working multi screen and all of the hivoice stuff removed and removal of the Chinese text on the lockscreen photos. I was tied last night and needed some sleep.
ajsmsg78 said:
Do a wipe and flash again, the Google apps are working fine for me. I will release another build tonight with working multi screen and all of the hivoice stuff removed and removal of the Chinese text on the lockscreen photos. I was tied last night and needed some sleep.
Click to expand...
Click to collapse
All of a sudden Google related apps started working! Without wiping or anything, however there is a problem with Gboard, when want to open its preference it crashes and comes out, can't add more languages to keyboard, and when I try to install it from play store it downloads and installs but at the end it doesn't install at all
safseyed said:
All of a sudden Google related apps started working! Without wiping or anything, however there is a problem with Gboard, when want to open its preference it crashes and comes out, can't add more languages to keyboard, and when I try to install it from play store it downloads and installs but at the end it doesn't install at all
Click to expand...
Click to collapse
When you first sign in you have to wait a minute to let Google play services update. Then it works fine. I'll include the newest play services.
some changelog. I have quite new versions. only bug and opitimze and update patches.
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
What about security patch level? January or February 2019?
Do you participate in Android One Beta Program?
yes, they belong to the beta program. updates February.
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
Can you give a ota dump?
maxweber1981 said:
yes, they belong to the beta program. updates February.
Click to expand...
Click to collapse
Did you by chance test the WiFi speed with and without Bluetooth enabled? How about the Bluetooth audio codecs?
hope all google camera apps' focus instability problem is solved. broken since pie arrived. (if someone is betatester and can report, please do so)
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
Could you provide screenshot showing baseband/modem version?
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Boot.img https://drive.google.com/file/d/1IAVSuYmOgzAw4G3HjNokjf-emIwk3xMD/view?usp=drivesdk
Patched boot https://drive.google.com/file/d/1t-G-TrEr3rYWnutSBDRIBy5RomaXapzP/view?usp=drivesdk
Images version
:laugh:
Any instructions how to update with Magisk installed? - anyone has already tried?
Is there a change log for this build?
Sent from my Phh-Treble vanilla using Tapatalk
maxweber1981 said:
yes, they belong to the beta program. updates February.
Click to expand...
Click to collapse
how to enroll beta program?
Friends give a link to the OTA-image 10.0.4.0
Is that issue fixed?
https://forum.xda-developers.com/mi-a2-lite/help/weird-wifi-issue-apps-updating-to-t3885216
What are the new features?
Thank you so much
Mattania said:
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Boot.img https://drive.google.com/file/d/1IAVSuYmOgzAw4G3HjNokjf-emIwk3xMD/view?usp=drivesdk
Patched boot https://drive.google.com/file/d/1t-G-TrEr3rYWnutSBDRIBy5RomaXapzP/view?usp=drivesdk
Click to expand...
Click to collapse
thanks for you boot patched
I'm not on the beta program and I just got the update tonight.
No change log or any message telling what was the update beside saying it was a security update.
The battery percent indicator has been removed from the accu-settings?
Please, run from it
I got that update on OTA (the 10.0.4 version), and now I have a crippled phone. Low brightness, poor battery life, troubles with WiFi networks above 2.4Ghz (now I miss my 5Ghz WiFi on my modem), and some apps doesn't even work fine. Also, finger scanner got slow, and I have troubles with mobile network. I'm afraid of finding more failures as I use it.
So, if someone is reading this and get the notification, please scrap it and don't install the updates unless you hate your phone.
ugn01 said:
I got that update on OTA (the 10.0.4 version), and now I have a crippled phone. Low brightness, poor battery life, troubles with WiFi networks above 2.4Ghz (now I miss my 5Ghz WiFi on my modem), and some apps doesn't even work fine. Also, finger scanner got slow, and I have troubles with mobile network. I'm afraid of finding more failures as I use it.
So, if someone is reading this and get the notification, please scrap it and don't install the updates unless you hate your phone.
Click to expand...
Click to collapse
You need to do two things: change slots and wipe dalvik.
Code:
fastboot set_active a
1. Change slots can be done with fastboot or twrp
2. Wipe dalvik can only be done with twrp that can decrypt your internal storage...
If you are really lucky, changing slots will be enough.
Background: Daisy has two slots. In every slot there are all the partitions, the phone needs to boot - so you have some kind of backup.
Only data is not double. Normally you are on slot a. When you get an update, it will be installed to slot b and after that it changes to b to boot the new partitions.
I changed the slots after updating to 10.0.3.0 and wondered, why my phone was again 10.0.2.0... So, if you are lucky, you can just change slots with fastboot.
Hi,
My Xiaomi 12 still hasn't gotten an new update and is stuck on MIUI 13.0.27.0( SLCEUXM) with security patch of oktober 2022.
I would like to get to the latest miui 14 and would like to know what is the best way to manually update this safely with a original ROM?
Should I do this incrementally start at MIUI 13.2.6.0 and then go to the next till I get to the latest or can I just update to the latest MIUI 14 directly?
Tnx
Gradually is the safest method.
Skipped the Beta stables.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Thank you for the quick response.
I downloaded the MIUI downloader app are those ROMS good to?
I need to choose for a recovery ROM and then I can install it with the updater app right? So starting with version MIUI 13.2.6.0 would be the safest?
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
NOSS8 said:
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
Click to expand...
Click to collapse
You mean this one right?
It says it's only around 80mb is that correct?
When it's for a update from Android 12 to Android 13.
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
So I tried to install the stable recovery ROM MIUI 13.2.6.0.TLCEUXM but it didn't work I keep getting this message "can't verify update can't flash this stable rom"
Then I tried a newer version recovery ROM MIUI 14.0.5.0.TLCEUXM but same message.
Also tried your suggestion to use the incremental update of the current ROM V13.0.27.0 but then I got the message "can't verify update can't downgrade ROM version"
Do you have any other ideas on how to fix this problem?
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
NOSS8 said:
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
Click to expand...
Click to collapse
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Jappie3 said:
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Click to expand...
Click to collapse
Nope, you can re-lock the bootloader after installing the stock rom.
No need with a Xiaomi Eu rom (certified play store, everything works).
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Jappie3 said:
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Click to expand...
Click to collapse
Nope,only solution unlock the bootloader.
Just to be sure I downloaded the 2 latest versions that I hadn't tried yet.
The recovery ROM of version MIUI 14.0.7.0.TLCEUXM and 14.0.8.0.TLCEUXM.
And they both seem to work
Since I'm still on Android 12 now and missed so many updates in-between these 2 latest versions. Would it be safe to install one of these?
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
NOSS8 said:
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
Click to expand...
Click to collapse
So it's not safe to just install one of these recovery versions manually with the updater?
Jappie3 said:
So it's not safe to just install one of these recovery versions manually with the updater?
Click to expand...
Click to collapse
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
NOSS8 said:
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
Click to expand...
Click to collapse
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Jappie3 said:
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Click to expand...
Click to collapse
Zero risk does not exist and this risk increases when you force the update by skipping versions.
NOSS8 said:
Zero risk does not exist and this risk increases when you force the update by skipping versions.
Click to expand...
Click to collapse
Oke, yeah I wanted to do it step by step till I got to the latest miui 14 and still don't get why the older versions don't work.
The only older version I could find that also worked was version V13.0.33.0.SLCEUXM but can't find much about that update.
Logical sequence