Hi..I recently installed Gcam on Mi A2 (6/128)..and flashed the 10.0.3 boot image...however not able to Install the Feb 2019 security update. Can you please advice how I can keep Gcam and still get the Feb security update? I don't want my phone rooted...
S Advance User said:
Hi..I recently installed Gcam on Mi A2 (6/128)..and flashed the 10.0.3 boot image...however not able to Install the Feb 2019 security update. Can you please advice how I can keep Gcam and still get the Feb security update? I don't want my phone rooted...
Click to expand...
Click to collapse
Hi, did you flashed the stock boot after unninstalling magisk?
jaycedam said:
Hi, did you flashed the stock boot after unninstalling magisk?
Click to expand...
Click to collapse
Yes, i did a complete Magisk uninstall before flashing stock boot.
S Advance User said:
Yes, i did a complete Magisk uninstall before flashing stock boot.
Click to expand...
Click to collapse
But are you getting an error during the update or do you just want to keep gcam? As far as I know, updates often broke the camera2, but the patched boot of the feb update is already on this sub
jaycedam said:
But are you getting an error during the update or do you just want to keep gcam? As far as I know, updates often broke the camera2, but the patched boot of the feb update is already on this sub
Click to expand...
Click to collapse
I get an error during the update. I want to update my phone and still use Gcam. I don't want to use the patched boot since it will root my phone, which I don't want.
S Advance User said:
Hi..I recently installed Gcam on Mi A2 (6/128)..and flashed the 10.0.3 boot image...however not able to Install the Feb 2019 security update. Can you please advice how I can keep Gcam and still get the Feb security update? I don't want my phone rooted...
Click to expand...
Click to collapse
Can someone please help me with a solution? Much appreciated..
I also had got this situation. Please try fastboot flash.
S Advance User said:
Can someone please help me with a solution? Much appreciated..
Click to expand...
Click to collapse
Were u on January update, then u flashed patchboot, now flash boot, 10.3 is for January update only if you were on any other patch use patchboot and boot accordingly and your problem will be fixed
honey ghumaan01 said:
Were u on January update, then u flashed patchboot, now flash boot, 10.3 is for January update only if you were on any other patch use patchboot and boot accordingly and your problem will be fixed
Click to expand...
Click to collapse
I tried the exact same method..but not helping
S Advance User said:
I tried the exact same method..but not helping
Click to expand...
Click to collapse
Flash rom again using mi flash tool and then to enable camera 2 api use boot command not the flash command
Related
Anybody had the November update yet. :laugh:
And anyone with unlocked bootloader have Pie october update ?
Keep the jokes coming
Almost got it, but it went too quickly.
For sure, I'll get it next time
I am getting 80 hours of screen on time. It's powered by nuclear reactor and it's a secret project of Juho Sarvikos.
k3dar7 said:
And anyone with unlocked bootloader have Pie october update ?
Click to expand...
Click to collapse
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
Thanx for tip! I do repack myself, before i try find 0001 on */*prop* in booted system(and not found), not try find in boot.img(where this really is)
TomThePhysicist said:
I have installed the Pie october update with a unlocked bootloader.
To get rid of the sideload error I have repacked the Pie september boot.img to change the 0001 into 00WW. I can't post link for the moment but if anyone is interested by the repacked boot.img pm me.
Click to expand...
Click to collapse
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"
k3dar7 said:
i have repacked Pie september boot.img, in adb sideload is gone 0001 error, but still not finish, show "Error applying update: 20 (ErrorCode:: kDownloadStateInitializationError)"
first i try change 0001 to 00WW in default.prop and prop.default, second also in adbd and recovery binary...
repack using "Android_boot_image_editor"
Click to expand...
Click to collapse
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.
I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.
TomThePhysicist said:
You need to have an unrooted system in order to make the update.
I think the error 20 is caused by a difference between the sha256 sum of your system and the expected one from the installer.
I have reinstalled the Pie september update prior to the october one and everything worked fine.
Click to expand...
Click to collapse
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error
k3dar7 said:
i know unrooted, i have complety uninstall magisk from magisk manager...
What you mean "reinstall" ? if i try sideload pie september then show same error, if try after change slot then show timestamp error
Click to expand...
Click to collapse
If you have the september update installed on the active slot you will normally always get a timestamp error when trying to sideload it again.
To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update).
To sum up:
Flash an anterior boot image (to the september Pie update) with fastboot and reboot to recovery (I always flash both slots).
Sideload the september Pie update and reboot to bootloader.
Flash a repacked September boot image with 0001 changed into 00WW in default.prop and prop.default (pm me if you need a working boot image) and reboot to recovery.
Sideload the october pie update and reboot to system.
TomThePhysicist said:
[...]To get rid of the timestamp error, simply flash an anterior boot image with fastboot (I have used a boot image from the last Pie public beta update)[...]
Click to expand...
Click to collapse
thanks, this do a trick, now i have Pie October installed
k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.
divvykev said:
So, if this is true then a thread which started out as a bit of a joke has actually been more useful that HMD support?
Having a Nokia phone really doesn't stop amazing me.
Click to expand...
Click to collapse
yes, is true
anyway, really thanks for your jokes thread i before some day from despair try contact HMD support... try tips as update without 4g enabled, update without sim inserted, update in safe mode, ended with tips wait for november update, maybe be full ota
k3dar7 said:
thanks, this do a trick, now i have Pie October installed
Click to expand...
Click to collapse
You're welcome, I'm glad I could help.
shailendra1993 said:
I have already got Android 9.1 with great new features:
1. Nokia camera has become better than Pixel 3, my friend wants my Nokia 7 Plus in exchange for his Pixel the new camera even features X-ray mode where you can see what's behind a wall, it uses Wifi and Radio signals to see what's behind a wall.
2. It works so flawlessly that even Fortnite is supported on this new build
3. Bootloader comes unlocked by default now, it's so open that now you will need to file a petition to close it.
Click to expand...
Click to collapse
Ha ha,this is funny,you made my day
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?
Got the March 2020 OTA bit it fails to install I was rooted with magisk tried a factory reset with Razer images with no luck any ideas?
Did you lock the bootloader?
flash this in stock recovery
https://android.googleapis.com/pack.../09c48ba6cb9415820640cf217855b5463a1e0cd5.zip
(you need sdcard for that and move that zip there)
RKBD said:
flash this
Click to expand...
Click to collapse
What's that file? It can't be the update at 1.5GB?!
chris5s said:
What's that file? It can't be the update at 1.5GB?!
Click to expand...
Click to collapse
it's full ota to smr3 to not make any problems
RKBD said:
it's full ota to smr3 to not make any problems
Click to expand...
Click to collapse
The update is only listed at 99MB? Your file is 1.4GB. I'm not sure exactly what we would be flashing with this file.
I installed the zip https://android.googleapis.com/pack.../09c48ba6cb9415820640cf217855b5463a1e0cd5.zip in recovery. it took a minute or two. step 1/2 just wait a little bit. you will lose twrp recovery and root. but im now updated to march 2020 security update. im ok with that. Im not that concerned with the whole root thing. just letting you guys know It Works
im still on sep 2019 update
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
It's a patch.. it's not useless...
Baron60 said:
It's a patch.. it's not useless...
Click to expand...
Click to collapse
Yes patch as in security patch with some fixes. I understand that. Prolly i stick with mar update since i can't update to april patch. Thanks.
I've tried updating/installing using a vpn. Still no success. Don't know what's wrong...
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Then you can analysis the log
K9998 said:
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
Then you can analysis the log
Click to expand...
Click to collapse
Thanks. I will give it a try.
kxnzxmori said:
Thanks. I will give it a try.
Click to expand...
Click to collapse
No worries,
The typical message you will get if any of three partitions has been modified:
Code:
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
I have a Locked bootloader & I'm having the same problem. Please advise something.
I have the same problem. . i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Are you using android 13 (OneUI 5)
Samarimama said:
Are you using android 13 (OneUI 5)
Click to expand...
Click to collapse
One ui 5.1
kawsar4547 said:
My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Click to expand...
Click to collapse
Oh God.
I'm sorry to read that you updated from binary, going back will be a bit impossible. through odin no longer.
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
I didn't know binary was gonna update
kawsar4547 said:
I didn't know binary was gonna update
Click to expand...
Click to collapse
MMMMMMM..
Every time that OTA sends an update, the software version comes out and therefore the binary.
if you download a system to flash via odin, you force the binary.
I even warned right here about that topic.
but unfortunately, nothing can be done at the moment.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
3mel said:
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
Click to expand...
Click to collapse
It only remains to wait for Samsung to send an update that fixes that.
wait for a developer to send solutions via root.
I recommend you to use Kernel Bandido.
I don't know if it is compatible with binary 5.