Does anyone who get it see a difference?
Could you provide the output of
Code:
fastboot getvar all
So we see, if the bootloader got updated and I can provide TWRP and XPeria AOSP.
Then the custom rom development can start.
Stock Android 8.0 September
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA1.0_O_60
Bootloader got an update and until Sunday I will upload a new Sony AOSP 8.1 build.
If it is bootable, I will release a new TWRP build.
Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?
eelpout said:
Hmm, keep getting ”Could not install" from the India (IN) variant. Guess I'll try again tomorrow.
Anyone successfully install it and if so, with which region?
Click to expand...
Click to collapse
German H8266 on my H8296.
MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?
nolihowell said:
Hello do you think I can possibly flash H8216 firmware to my H8276 just as you flash H8226 to your H8296?
Click to expand...
Click to collapse
You should flash H8266, because the H8276 is dualsim, too.
H8216 would work fine, but the second sim is dead.
The external sdcard maybe, too.
MartinX3 said:
German H8266 on my H8296.
Click to expand...
Click to collapse
OTA? Or did you flash it?
Maybe it's time for me to switch. ?
eelpout said:
OTA? Or did you flash it?
Maybe it's time for me to switch. ?
Click to expand...
Click to collapse
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:
Does this update just bring security updates?
dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
And some small fixes and improvements.
MartinX3 said:
Xperifirm and its building new flasher
But it will be like a factory reset.
Buuut it will work like a charm. And you get your updates faster.
But aren't you from Canadia?
Maybe the Canadian software is optimized/calibrated for your mobile network technology. :silly:
Click to expand...
Click to collapse
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.
dibdin said:
Does this update just bring security updates?
Click to expand...
Click to collapse
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.
eelpout said:
nah, U.S. but I grew up in Minnesota, which is close to Canada.
IN doesn't have problems with update speed, it's within hours of DE, but this is the second time the OTA has continuously failed. Though other times it's been fine.
OK, I see you're cheating and not getting it OTA.
Flashing another region's firmware though shouldn't require a full reset, as long as one removes the user data sin file from the folder.
Click to expand...
Click to collapse
Since I switched to h8266 in April or May I install only OTA Delta updates.
MartinX3 said:
A new bootloader.
Which allows custom ROMs and twrp, which allows the DRM fix.
Click to expand...
Click to collapse
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?
eelpout said:
oh, hmmm. since it's a new bootloader, is it a risk to switch firmware regions?
Click to expand...
Click to collapse
Of course not.
It is an universal bootloader.
@MartinX3 Just flashed the *51 firmware and my BL version string is:
Code:
1310-7079_X_Boot_SDM845_LA1.0_O_60
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?
nasko_spasko said:
@MartinX3 Just flashed the *51 firmware and my BL version string is:
I'm trying to boot AOSP Oreo, I just built today, but no success so far.
Have you got better luck booting aosp?
Click to expand...
Click to collapse
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.
MartinX3 said:
Try my build in the twrp thread.
Someone told me, that he successfully booted the old aosp build.
So I made one with the newest sources.
A manual how to flash is there, too.
Maybe you need the OEM file from the last build.
Click to expand...
Click to collapse
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!
nasko_spasko said:
Ops! I apparently forgot to flash dtbo and vbmeta. Boots!!!
Click to expand...
Click to collapse
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?
MartinX3 said:
:laugh::silly:
Any errors, missing features?
How is the camera with the open camera app?
ADB? Usb? Touch? Sound?
The new 9.0 OEM image is compatible?
Click to expand...
Click to collapse
Well the 8.1 is not much of a usable one, i'll try the 9.0 after the build is complete, the touchscreen is not working as expected, it's picked up as a touchpad the UI is navigated with mouse, it seems that the graphics acceleration is not working (gralloc?), brightness is not adjustable. RIL works(sort of), calls work (mic produces robotic sound), Data works. ADB is not working and Developer Options menu crashes the settings app, Sleep not working, device gets quite hot over time(PM?).
Sound works. Camera is not accessible(just gray screen with the navbar at the bottom) It's fast as hell, though... That works SDM845 (rock)
Related
I was hoping someone could help me out with this......
I've been getting this irritating "Android System Update" (screenshot attached) week after week.
I'm rooted (unlocked bootloader), running stock 5.1.1
This update keeps showing up and when I go to install it, the phone reboots, then it goes it TWRP. I'm assuming this hasn't installed correctly because it keeps coming back.
Does anyone know how to get rid of this or install it correctly. It's becoming quite annoying when it pops up time after time.
Thank you-
Install the update manually or block OTAs.
nhizzat said:
Install the update manually or block OTAs.
Click to expand...
Click to collapse
How do I install manually?
That's what I'm trying to find out
http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.
jj14 said:
http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.
Click to expand...
Click to collapse
Thank you.
So I just need to find the security patch and manually install it?
Now where to find it, LOL
I'd start by reading the stickies at the top of the thread list... Good readng.
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
LMY47Z (screenshot attached)
I have Verizon.
I thought the builds were carrier specific.
This is what I found:
https://developers.google.com/android/nexus/images#mysid
MVLJR said:
This is what I found:
https://developers.google.com/android/nexus/images#mysid
Click to expand...
Click to collapse
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
MVLJR said:
So I just need to find the security patch and manually install it?
Click to expand...
Click to collapse
See the end of the first post on the link that I shared above
Didgeridoohan said:
I'd start by reading the stickies at the top of the thread list... Good readng.
Click to expand...
Click to collapse
IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
jj14 said:
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
See the end of the first post on the link that I shared above
Click to expand...
Click to collapse
Thank you all very much for your help.
I'll try to patch one of these updates this weekend when I have some time off.
I'm the gatekeeper for all that is Android OS in my family. Myself, my Mom and now my Dad all have Nexus 6' and I've rooted us all. So I install it on my phone first and then the same with theirs.
I was so happy I found a fix for the MLB At Bat app and their stupid blackout rules.
This is just great, been having the same issue and versions
This covered everything I had at the moment!
I applied the update tonight, sick of those damn OTA prompts.
This is where I got mine from, but still not sure if I chose the right one:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Installed the download from:
LVY48F (5.1.1 Project Fi bugfix update 20150910)
It says Project Fi only, but I have no idea what that is. I didn't see an option for LVY48I, so I went with LVY48F.
Did I do this right?
Want to make sure I didn't screw up my phone.
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"
Anyone?
MVLJR said:
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"
Click to expand...
Click to collapse
Latest factory image is LMY48M
Here is guide how to flash factory image. http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thank you!
I flashed the Pure Nexus ROM this past weekend and so far, so good. Loving some of the features not included in stock.
Here you can download stock files from the B20 and B27 firmwares for the A2017U (US variant), as well as TWRP backups. Included are:
TWRP system image (in its own folder)
unmodified byte-for-byte (DD) system image (system.img)
boot.img
recovery.img
aboot.img
bluetooth.bin
fbop.img
modem.bin
B20: https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw (now includes stock image of B20 provided by ZTE for bootloader-unlocked users)
B27: https://mega.nz/#F!6YsTVZqC!7THrXFGOhIH_1eCgCnxqbA
NOTE: if you're currently on B20_Boot, it's highly recommended that you go back to B20 before attempting any sort of update from B20 to B27! Evidence suggests you may end up bricked if you don't!
Thanks to @tenfar for his tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) and to @DrakenFX for the ADB commands and the how-to for restoring stock (http://forum.xda-developers.com/axon-7/how-to/guides-info-info-a2017u-bootloader-t3440254).
Good to know!
Sent from my Nexus 6P using Tapatalk
I don't recommend unlocking the bootloader at this time since it breaks OTA. Once @tenfar gets his app to work with b20 locked we should be able to keep root after OTA eventually. Of course non of that matters once custom ROMs start coming.
Awesome work! Now we have something to fall back on in case something goes wrong.
KyJelly69 said:
I don't recommend unlocking the bootloader at this time since it breaks OTA. Once @tenfar gets his app to work with b20 locked we should be able to keep root after OTA eventually. Of course non of that matters once custom ROMs start coming.
Click to expand...
Click to collapse
Agreed.
I will say that a part of me thinks ZTE will release Nougat for the Axon 7 sooner than later. I don't have any hard evidence to support the idea, but some of the comments the mods have made over on the ZTE forums make me feel like there will be Nougat before there's another Marshmallow update for the US model. And I think they're going to try to get Nougat out ASAP (perhaps before the 2016 Nexus devices are announced).
It's all speculation, though.
rczrider said:
Agreed.
I will say that a part of me thinks ZTE will release Nougat for the Axon 7 sooner than later. I don't have any hard evidence to support the idea, but some of the comments the mods have made over on the ZTE forums make me feel like there will be Nougat before there's another Marshmallow update for the US model. And I think they're going to try to get Nougat out ASAP (perhaps before the 2016 Nexus devices are announced).
It's all speculation, though.
Click to expand...
Click to collapse
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Sent from my ZTE A2017U using Tapatalk
osmosizzz said:
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Click to expand...
Click to collapse
Is there anyone who has already re-locked bootloader successfully?
osmosizzz said:
I feel the same way. I already unlocked my bootloader however. But I feel that, since I unlocked it without going through ZTE, I can lock it back and pull an Ota. If not, I'm sure nougat will be flushable through twrp some way, somehow
Click to expand...
Click to collapse
Probably. I know that with some phones, the upgrade from LP to MM required a new bootloader (security). I'd be surprised if the upgrade from MM to Nougat would require a new bootloader, though.
Thank you for the files. Is the A2017UV1.o.oB20 folder available anywhere else than MegaPoop?
sorry, but i dont have the idea... my query is, can i install this on my zte axon 7 chinese variant (a2017)?
benlenspace said:
sorry, but i dont have the idea... my query is, can i install this on my zte axon 7 chinese variant (a2017)?
Click to expand...
Click to collapse
Short answer : NOP ,
the Chinese variant have FULL FACTORY IMAGES so you really don't need any of this. (you guys are lucky in that dept.)
Theoretically, could someone update from B20 to B20_Boot, unlock the bootloader, and then reflash the B20 fastboot, boot, recovery, and system to go back to complete stock B20 with an unlocked bootloader? This might allow people to get back on the OTA path while still maintaining an unlocked bootloader.
DrakenFX said:
Short answer : NOP ,
the Chinese variant have FULL FACTORY IMAGES so you really don't need any of this. (you guys are lucky in that dept.)
Click to expand...
Click to collapse
thanks for the reply... i wanted to install the US (2017u) rom in my chinese variant zte axon 7 because i wanted to activate "my voice" in English... that's the mean point...
rczrider said:
My gray came yesterday and so I used @tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) to dump boot and recovery, then install TWRP and get a dump of system.
Click to expand...
Click to collapse
Dude you are my savior! Your system image worked on my Axon 7!! You saved my phone!
Can I pay you a beer or something? :highfive:
EDIT: WiFi is not working anymore
XblackdemonX said:
Dude you are my savior! Your system image worked on my Axon 7!! You saved my phone!
Can I pay you a beer or something? :highfive:
EDIT: WiFi is not working anymore
Click to expand...
Click to collapse
Do a Factory reset now that is sort of fresh install....
And check which update you are right now with the new system.?
DrakenFX said:
Do a Factory reset now that is sort of fresh install....
And check which update you are right now with the new system.?
Click to expand...
Click to collapse
Thank you but I did do a factory reset. I've read somewhere else that the WiFi issue is related to the modified boot.img
benlenspace said:
thanks for the reply... i wanted to install the US (2017u) rom in my chinese variant zte axon 7 because i wanted to activate "my voice" in English... that's the mean point...
Click to expand...
Click to collapse
What Language is your Default Language setting?
Cuz My Voice for what I can tell works base on Default Device Language Settings.
Meaning if your default is Chinese you need to change it to English.
Try mine from English to Spanish and works when I speak My Voice in spanish and I change it back to English.
XblackdemonX said:
Thank you but I did do a factory reset. I've read somewhere else that the WiFi issue is related to the modified boot.img
Click to expand...
Click to collapse
So you should try flashing OP boot.img and to a Factory reset after see if that works
DrakenFX said:
So you should try flashing OP boot.img and to a Factory reset after see if that works
Click to expand...
Click to collapse
I just tried that but it doesn't work. It gets stuck on the ZTE logo and doesn't move.
I've only managed to make to boot with the modified boot.img but then WiFi is dead :crying:
XblackdemonX said:
I just tried that but it doesn't work. It gets stuck on the ZTE logo and doesn't move.
I've only managed to make to boot with the modified boot.img but then WiFi is dead :crying:
Click to expand...
Click to collapse
OK, download this boot.img and try.....again,
https://www.androidfilehost.com/?fid=24671309938033033
DrakenFX said:
OK, download this boot.img and try.....again,
https://www.androidfilehost.com/?fid=24671309938033033
Click to expand...
Click to collapse
Same thing, stuck on the ZTE logo
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.
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
JJ5150 said:
Every Pie Rom I've installed with the February Update, kills my WIFI. It comes and goes, it's not stable. Check it guys, CHECK IT.
Click to expand...
Click to collapse
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Wisse said:
Strange, i'm running Ressurection Remix with no problems at all. Maybe you should check/reflash your radio?
Click to expand...
Click to collapse
Resurrection Remix is still UNOFFICIAL. Last version is 02/09. February OFFICIAL Security Update was Updated February 16-19, and all the PIE ROMS that are OFFICIALLY Updated with this update KILL THE WIFI.
Thanks tho.
I am using pixel experience and there isn't any problem I encountered
SAPTADIP MALAKAR said:
I am using pixel experience and there isn't any problem I encountered
Click to expand...
Click to collapse
May I ask what model number you have?
I'm running AEX 6.3 and my wifi is perfectly fine.
JJ5150 said:
May I ask what model number you have?
Click to expand...
Click to collapse
Hey , I am using Moto G5s plus and the model number is XT1804.
SAPTADIP MALAKAR said:
Hey , I am using Moto G5s plus and the model number is XT1804.
Click to expand...
Click to collapse
I'm on XT1806
I was presented with a workaround... Disable WIFI scanning in settings. Fixes Wifi drops. NO DICE. Totally unstable wifi.
No problem with me too.. using pixel experience on xt1804
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Juancasa14 said:
I'm using havoc os in my XT1806 and everything is working great, also most people don't have your problem, you should restore your stock ROM backup and try to clean flash any pie ROM, this is not the devs fault.
Click to expand...
Click to collapse
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Juancasa14 said:
Hi ! Don't be afraid, if you follow every step correctly you shouldn't have any problems, if you already unlocked your bootloader you should flash the latest version of TWRP if you want to root your phone, you can't use gcam unless you do it because you need to enable cam2api by adding a specific line to the build.prop.
If you decide to root it, just flash the treble version of TWRP and then flash the latest version of magisk, then you'll be able to modify your build.prop !
Ask me if you need any help
Click to expand...
Click to collapse
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
prophetgamer said:
Hi, i have a XT1806 too, I want to have the gcam, I just unlocked the bootloader, but I'm afraid to root it and flash a rom, how did you do it, thanks
Click to expand...
Click to collapse
prophetgamer said:
hello again, I tried to make a backup of the system image but it always says backup failed, I already made the wipe data to decrypt, but it did not work
Click to expand...
Click to collapse
You don't need to backup the system image, just backup system, data and boot, and also persist and efs just in case you lose your IMEI. Are you using treble TRWP?
If your phone has locked bootloader, you can get OTA update of ColorOS with December security patch.
Download size is 146MB.
For non-mainland China residents VPN service is needed for initial update detection. When the update is detected, no VPN needed for downloading.
As VPN service you can use Android app Panda VPN free, in which after installation select any Mainland China VPN server and choose free option (you will have to watch one video Ad and then you have 1 hour time usage).
Edit: Link to the full package in ozip file (2.33 gb)
https://download.c.realme.com/osupdate/RMX1991_11_OTA_0140_all_RfH5a5t2Kegi.ozip
well im using panda vpn and its connected but the phone do not detect any updates!!!
JUst downloading A 14 after using VPN by Panda.
Hope it works without any issue.
P.D. downloading 252 -Mb, not 146 Mb (maybe cause jumping from 12 to 14 instead 0f 13 to 14)
Despite using panda vpn...due to high ping the phone cannot detect the new software update... could you kindly provide us with the A14 update firmware link
Working
Try using "China-Shenzhen-1"
Sadib0168 said:
Despite using panda vpn...due to high ping the phone cannot detect the new software update... could you kindly provide us with the A14 update firmware link
Click to expand...
Click to collapse
verbatino said:
Working
Click to expand...
Click to collapse
That's great
Big Boy said:
well im using panda vpn and its connected but the phone do not detect any updates!!!
Click to expand...
Click to collapse
Use Shenzhen-2
verbatino said:
Try using "China-Shenzhen-1"
Click to expand...
Click to collapse
Thanks a lot bro... it's working now
verbatino said:
JUst downloading A 14 after using VPN by Panda.
Hope it works without any issue.
P.D. downloading 252 -Mb, not 146 Mb (maybe cause jumping from 12 to 14 instead 0f 13 to 14)
Click to expand...
Click to collapse
From A13 to A14 - 146 mb
From A12 to A14 - 252 mb
royayon01 said:
Use Shenzhen-2
Click to expand...
Click to collapse
thanks man. that did the job
What about fingerprint sensor for unlocked bootloader with A14?
kkffiirr said:
What about fingerprint sensor for unlocked bootloader with A14?
Click to expand...
Click to collapse
Working
Yeh, the full package in OZIP file has become available
yakovpol said:
Yeh, the full package in OZIP file has become available
Click to expand...
Click to collapse
Please do a root tutorial
royayon01 said:
Working
Click to expand...
Click to collapse
How did you get your fp to work? I flashed the a14 and reflashed magisk but still not working. I was on A12 rooted.
Wow, sounds like the conspiracy theory was right after all...
xterminater07 said:
How did you get your fp to work? I flashed the a14 and reflashed magisk but still not working. I was on A12 rooted.
Click to expand...
Click to collapse
The thing is not in the system/boot or other partitions that are updated, but in the change that happens during unlocking bootloader. So you need to lock and then unlock bootloader when your system is A.13 or newer.
Please be extremely accurate and cautious preparing the phone for the locking process: you have to have 100% stock contents of all partitions. Otherwise you will get a brick. See *Back to Stock howto*
yakovpol said:
The thing is not in the system/boot or other partitions that are updated, but in the change that happens during unlocking bootloader. So you need to lock and then unlock bootloader when your system is A.13 or newer.
Please be extremely accurate and cautious preparing the phone for the locking process: you have to have 100% stock contents of all partitions. Otherwise you will get a brick. See *Back to Stock howto*
Click to expand...
Click to collapse
So you are saying I have to go back to stock completely with a lock bootloader? The unlock bl?
xterminater07 said:
So you are saying I have to go back to stock completely with a lock bootloader? The unlock bl?
Click to expand...
Click to collapse
Right