[Q] Problem in installing battery update with custom recovery. - YU Yureka Q&A, Help & Troubleshooting

I have installed cwm recovery in my yureka.
But now when i am trying to install battery update via system or .zip file, its showing error in the installation process.
Please help...

AnkitBhateja said:
I have installed cwm recovery in my yureka.
But now when i am trying to install battery update via system or .zip file, its showing error in the installation process.
Please help...
Click to expand...
Click to collapse
first install stock recovery and flash update
all OP said that to flash CM update you should be on stock recovery.

Those who have rooted their devices before cannot install 122mb manual update or 128mb ota update. Either flash stock lollipop and then flash the update via ota or manually or install 643Mb zip file directly to your present os.

ashish_zarekar said:
first install stock recovery and flash update
all OP said that to flash CM update you should be on stock recovery.
Click to expand...
Click to collapse
now i hav installed stock recovery by using "Flashify app. - for rooted users".
and then tried to install the update by flahing zip. file in the stock recovery....but again its showing error!!

Flash 643 MB zip file.

Related

[Q] where areDownloaded files stored

I am trying to find the ota update for my note 3 after downloading to install after downing it reboots to recovery I have TWRP need to find file to install from TWRP
gtuck1002 said:
I am trying to find the ota update for my note 3 after downloading to install after downing it reboots to recovery I have TWRP need to find file to install from TWRP
Click to expand...
Click to collapse
I believe that downloaded ota update must be flashed through stock recovery. What i suggest
Flash back stock recovery
Download your ota
And let it finish install
Flash back your twrp.

[Q] Unable to install TWRP Recovery after CM12 YNG1TAS1K0 update

Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...
I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.
Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)
remove battery after install recovery before restarting phone

updating rooted phone

Hi all,
I am using XT1643 indian version. I have successfully rooted it using TWRP recovery. However, I haven't changed the rom. Today, it is showing OTA update of security fixes. Should I update it or is there any particular method for updating or should I ignore the update.
Thanks.
ankit.hinsu said:
Hi all,
I am using XT1643 indian version. I have successfully rooted it using TWRP recovery. However, I haven't changed the rom. Today, it is showing OTA update of security fixes. Should I update it or is there any particular method for updating or should I ignore the update.
Thanks.
Click to expand...
Click to collapse
flash stock recovery and then update
FlashFire
or Just use Flashfire A handy Application for updating rooted phone. but remember one thing always keep backup and stock rom file to your pc if something goes wrong you can easily re flash your stock rom.
Both options doesn't work.
With FlashFire, it is impossible to find the update file, and with stock recovery, its gives an error when updating
If FlashFire doesn't work, you should first unroot your device, uninstall xposed if you already installed it, also remember to use stock kernal after that.. flash stock recovery than update via ota. Let us update what happen
Edit :- I tried my self
1. unistalled xposed
2. un rooted
3. wiped all data, dalvik cache, and other stuf..exclude system
4. rebooted
5. flashed stock recovery
6. reboot again
7. download ota
8. device reboot again in stock recovery
9. And failed to update
10. So we cant update our phone unless new updated stock images available...

ZE520kl OTA upgrade doesn't work

Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.

UPDATE.ZIP is corrupt

This morning i received the android 10 ota update on my k20(davinciin). I have twrp and magisk installed and since ota updates fail with twrp installed I simply unrooted my device which replaced twrp with stock recovery. On installing the OTA it says installation failed 'update.zip is corrupt'. Need help.
Why didn't you install through twrp? Just download ROM and install
yaro666 said:
Why didn't you install through twrp? Just download ROM and install
Click to expand...
Click to collapse
Can I do that without wiping my data?

Categories

Resources