Related
Hi everyone,
Las week the OTA update appeared in my phone. I tried to use the google-automatic procedure, but as I have my Nexus 5 rooted, the install was aborted as soon as the device was restarted.
I read the helpdesk thread, trying to update the device manually, but I can't be able to.
I have the 4.4 to 4.4.2 .zip file inside the downloads folder, I restart the device to recovery mode (I've installed TWRP), and after writing the decrypt password and mount the volume, When I try to apply the zip file
"/system/app/EmailGoogle.apk" has unexpected co
E: Error executing update binary in zip '/sdcar
Error flashing zip '/sdcard/Download/b3d1f30762
Updating partition details..
Note that the senteces is cut due to the lenght of the screen.
Before flashing, I go to mount option, and mount all the folder (system, firmware, sdcard)
Any ideas?
Now I'm thinking that when I rooted the device, I used ES File Explorer to delete some apps directly from /sys/apps, maybe is that the error, that some GApps has been removed from the device.
Thank you!
Yes Google has nicely written in app checks. If these apps are not present on check the update is aborted
Sent from my Nexus 5 using Tapatalk
So I have to reinstall the GApps package, and try to apply de update?
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Ben36 said:
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Link not valid, but thank you, I will install GApps
Zepius said:
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Click to expand...
Click to collapse
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Deiwor said:
Link not valid, but thank you, I will install GApps
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Click to expand...
Click to collapse
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
jd1639 said:
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
Click to expand...
Click to collapse
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Deiwor said:
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Click to expand...
Click to collapse
Flashing the system and boot images isn't starting from scratch... you can keep your userdata as long as you aren't using a custom ROM. Flashing those just gives you back a clean stock OS without any of your mods. No need to start from scratch. Should only take a couple minutes.
Also, your mods are the reason it failed in the first place, not because you were rooted. Rooting itself does not prevent OTA updates.
I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.
What exactly does fail?
There should be an error message when you try to flash the OTA.
Look at the screen and report back, the boot.img you flashed to get root on your phone shouldn't have any impact on the update procedure.
CassandraN said:
I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.
Click to expand...
Click to collapse
I am in the exact same situation i unrooted and uninstalled xposed and it fails shortly after the progress bar appears i tried twice and same in gonna flash the boot.img and recovery.img out of the factory img later and try again.
Same here I removed root update downloads then install fails It don't tell you why it failed.
Sent from my XT1032 using XDA Premium 4 mobile app
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I spoke to Motorola and she said I may not be able to update if my bootloader is unlocked
Sent from my XT1032 using XDA Premium 4 mobile app
+1 Phone downloads the update. Restarts and gives "error". Phone is unlocked and rooted.
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it
deadpunk said:
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it
Click to expand...
Click to collapse
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.
Skinpipe said:
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.
Click to expand...
Click to collapse
I had to use method 2 to root too, and mine is also failing to update... :/ keep us informed!
xTx
darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.
darkeingel said:
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.
Click to expand...
Click to collapse
boot.img is the kernel, you only need to flash back a stock kernel if you have flashed a custom one earlier.
The superboot method does not alter the kernel, it just does some magic one-time boot that roots the phone (ie alters files in /system). You still have the original kernel in place. superboot just flashes superSU. superSU is the app itself plus certain /system file addtions and alterations.
To remove root all the /system files that rooting updates must be set back to how they were, the updater does a checksum on the files and if they differ from what they should be then the update fails.
superSU for example modifies /system/etc/install-recovery.sh as well as adding new files to /system. So /system/etc/install-recovery.sh would need to be put back to how it was.
Depending on which files the superboot method uses will depend on which files need altering back.
In general you are going to want to flash back stock /system as thats easiest (or maybe you did a nandroid and can restore /system from that).
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Thats good. So SuperSU basically cleans itself up and reverts all /system files it changed back to their original values. Easier than restoring a stock /system.
CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Unroot using the supersu app if that's what you mean you cant do
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...
Skinpipe said:
Unroot using the supersu app if that's what you mean you cant do
Click to expand...
Click to collapse
Yes you can, superSU has an 'unroot' option. On another thread Im sure someone had issues with it as it left some junk lying behind, but for the poster in this thread it seems to have worked fine.
---------- Post added at 01:15 PM ---------- Previous post was at 01:10 PM ----------
deadpunk said:
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...
Click to expand...
Click to collapse
if you restore entirely back to stock, ie stock recovery as well, then waiting for the OTA to download the 'offical' way may be better. This will then update not just Android but your stock recovery as well. Im unsure if installing from the sdcard updates the radios (ie mobile radios) or not. If not then again installing the officiall way may be better.
If someone on here knows if the mobile radios get updated I'd like to know. I see many /modem files in the update.zip. Its these Im interested in whether they get flashed or not when using the sdcard method.
rooted 4.4.2 now working:
followed the guide http://forum.xda-developers.com/showthread.php?t=2563599&highlight=mismatched to install CWM recovery
downloaded the latest SuperSU from http://download.chainfire.eu/376/SuperSU/ , copied to root of the sdcard and installed using CWM
titanium backup (free version) worked a charm, only thing it seems it didn't backup was my live wallpaper choice! bit of a pain to have to click "install" and "done" on each app (all 181 of them!) but much quicker than reinstalling and setting them up again from the Play store
now to have a play with my new kitkat!
xTx
EDIT: incidentally, where does it show what bootloader is being used? can't see anything in phone settings or fastboot...
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing
-sandro- said:
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing
Click to expand...
Click to collapse
Are you just disabling superSU or are you actually choosing the option to unroot, ie the option in superSU that says:
Full unroot
Cleanup for permanent unroot
If you do this is should remove root and put all /system files back as they were (ie the ones it altered during root).
Also I assume you have not modifed any system apps yourself, eg installed newer versions etc or removed any? If you have then again the update wont work. The update checks lots of files to ensure they have not been modified before it does the update.
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!
I have HTC one a9 with build number 1.58.709.1. Rooted and unlocked bootload and have twrp. Never flash any roms.
I want to remove every thing that prevent ota to be installed.
I think twrp will cause problem for ota. So how can I remove it an have stock recovery?
The ruu is not available for x.xxx.709.x in web. But I find ota matching my build number. Is that help?
ghasemi.hussein said:
I have HTC one a9 with build number 1.58.709.1. Rooted and unlocked bootload and have twrp. Never flash any roms.
I want to remove every thing that prevent ota to be installed.
I think twrp will cause problem for ota. So how can I remove it an have stock recovery?
The ruu is not available for x.xxx.709.x in web. But I find ota matching my build number. Is that help?
Click to expand...
Click to collapse
Yes, you can extract the recovery.img using this tool.
CSnowRules said:
Yes, you can extract the recovery.img using this tool.
Click to expand...
Click to collapse
Thanks.
I will do that. Then what should I do with it? Flash it?
And I remember that after installing twrp I had format my internal storage to make it decrypted. How can I undo that?
ghasemi.hussein said:
Thanks.
I will do that. Then what should I do with it? Flash it?
And I remember that after installing twrp I had format my internal storage to make it decrypted. How can I undo that?
Click to expand...
Click to collapse
Yes, you can flash the extracted recovery image via recovery.
For encryption, if you do the OTA update and let it reboot stock, it will automatically encrypt your data. Obviously, first boot might take a long time. If you interrupt it, you will lose your data.
CSnowRules said:
Yes, you can flash the extracted recovery image via recovery.
For encryption, if you do the OTA update and let it reboot stock, it will automatically encrypt your data. Obviously, first boot might take a long time. If you interrupt it, you will lose your data.
Click to expand...
Click to collapse
After restoring stock recovery, I need to unroot and lock boot loader for getting ota?
ghasemi.hussein said:
After restoring stock recovery, I need to unroot and lock boot loader for getting ota?
Click to expand...
Click to collapse
To manually install an OTA, definitely not. All you need is the stock recovery, a COMPLETELY untouched system (never mounted r/w), and the correct ota.zip.
CSnowRules said:
To manually install an OTA, definitely not. All you need is the stock recovery, a COMPLETELY untouched system (never mounted r/w), and the correct ota.zip.
Click to expand...
Click to collapse
Is there a way to check if system modified or not?
I read before that some ota are patches asn some of them are complete os. They said only when you want to install patches you need untouched system partition.
The next ota will be android 7. So it format every partitions and modified system cannot make any problem.
Is it correct?
No, the Nougat OTA (for US unlocked at least) patched the existing system partition.
The easiest way to check is to attempt to install the OTA with the stock recovery. It will tell you.
If I were you, I'd flash stock recovery and system from your current RUU, then OTA update.
Another option is to just install the RUU. That will revert your phone to completely stock, wipe your data, and allow you to start fresh.
CSnowRules said:
No, the Nougat OTA (for US unlocked at least) patched the existing system partition.
The easiest way to check is to attempt to install the OTA with the stock recovery. It will tell you.
If I were you, I'd flash stock recovery and system from your current RUU, then OTA update.
Another option is to just install the RUU. That will revert your phone to completely stock, wipe your data, and allow you to start fresh.
Click to expand...
Click to collapse
That's the problem. There is no ruu available for my build number (1.58.709.1.). I just find an ota with this bluid number. The ota did not contain a system.img.
ghasemi.hussein said:
That's the problem. There is no ruu available for my build number (1.58.709.1.). I just find an ota with this bluid number. The ota did not contain a system.img.
Click to expand...
Click to collapse
Did you flash the stock recovery and attempt to install the OTA?
If so, what is the result?
CSnowRules said:
Did you flash the stock recovery and attempt to install the OTA?
If so, what is the result?
Click to expand...
Click to collapse
Yes. I flash stock recovery. then I try to side load the ota to phone. Adb did not recognize device in boot loader or recovery. I don't know why. I use 15 sec Adb installer. It said it installs drivers.
Update: I notice that in bootloader on top of screen there is writing: "software status: official".
Does that mean system partition is untouched?
If your stock recovery has a menu, you can copy the OTA.zip to your phone or sdcard and install from there.
It said system partition has mounted r/w.
What can I do now? There is no ruu with my build number in web. I think s-off is my only way to get android 7? Or maybe htc publish ruu for all regions this time?
If I found system partition backup of my build number in web, is restoring it help?
update:if previous ota (1.56.709.70) has system image in it can i flash that sysem.img?
and do i have to install twrp again to be able to flash system.img?
ghasemi.hussein said:
It said system partition has mounted r/w.
What can I do now? There is no ruu with my build number in web. I think s-off is my only way to get android 7? Or maybe htc publish ruu for all regions this time?
If I found system partition backup of my build number in web, is restoring it help?
update:if previous ota (1.56.709.70) has system image in it can i flash that sysem.img?
and do i have to install twrp again to be able to flash system.img?
Click to expand...
Click to collapse
System backups found online can be unreliable for OTA updates. Here's what I suggest:
Install TWRP to your phone, and backup your current boot and system to an external sd. Be sure that the 1.58.709.1 ota.zip is located on your external sd as well.
Extract the system image from 1.56.709.70 RUU, place it on your external sd card as well, and flash it in TWRP.
Reboot to stock recovery and install the 1.58.709.1 ota. It should verify the 1.56.709.70 system and patch it.
That should complete successfully. When it reboots, it will take a long time since it will encrypt data by default.
You will then be 1.58.709.1 stock and be able to take OTA updates.
If something doesn't complete successfully, stop and post the log here.
CSnowRules said:
System backups found online can be unreliable for OTA updates. Here's what I suggest:
Install TWRP to your phone, and backup your current boot and system to an external sd. Be sure that the 1.58.709.1 ota.zip is located on your external sd as well.
Extract the system image from 1.56.709.70 RUU, place it on your external sd card as well, and flash it in TWRP.
Reboot to stock recovery and install the 1.58.709.1 ota. It should verify the 1.56.709.70 system and patch it.
That should complete successfully. When it reboots, it will take a long time since it will encrypt data by default.
You will then be 1.58.709.1 stock and be able to take OTA updates.
If something doesn't complete successfully, stop and post the log here.
Click to expand...
Click to collapse
Unfortunately the latest ruu for Taiwan is 1.27.709.x for android 6.0.0. I download 1.56.709.70 ota. It doesn't contain system image too. 1.56 was first update if android 6.0.1 and 1.27 was latest build of android 6.0. I think system image of 1.27 is same as 1.5x updates.
I want to try your way in 1.27.
Ok, that MIGHT work with system images only. 1.2x boot and recovery images will not boot on 1.5x firmware.
CSnowRules said:
Ok, that MIGHT work with system images only. 1.2x boot and recovery images will not boot on 1.5x firmware.
Click to expand...
Click to collapse
this is what i do step by step:
1. flash twrp
2. backup system and boot partition
3. flash system image from 1.27
4. flash stock recovery
5. try to install 1.56 ota. unsuccessful. see image 1.
6. try to install 1.58 ota. unsuccessful. see image 2.
7. boot to system. it got stuck in bootloop.
8. install twrp and restore system and boot backup.
9. boot to system and it booted successfully.
what else can i do?
ghasemi.hussein said:
this is what i do step by step:
1. flash twrp
2. backup system and boot partition
3. flash system image from 1.27
4. flash stock recovery
5. try to install 1.56 ota. unsuccessful. see image 1.
6. try to install 1.58 ota. unsuccessful. see image 2.
7. boot to system. it got stuck in bootloop.
8. install twrp and restore system and boot backup.
9. boot to system and it booted successfully.
what else can i do?
Click to expand...
Click to collapse
Did you swipe to allow system to be mounted r/w in TWRP? If you did, that could be the problem.
If not, you can attempt to use the system backups that you can download. You may have the same result, though.
Have you tried using HTC sync manager from download mode? Sometimes that will RUU your phone. Your data would be wiped though.
CSnowRules said:
Did you swipe to allow system to be mounted r/w in TWRP? If you did, that could be the problem.
If not, you can attempt to use the system backups that you can download. You may have the same result, though.
Have you tried using HTC sync manager from download mode? Sometimes that will RUU your phone. Your data would be wiped though.
Click to expand...
Click to collapse
Yes. I allow twrp to mount system as r/w because without this twrp cannot flash system.img.
I don't understand last paragraph. Will you please explain more?
ghasemi.hussein said:
Yes. I allow twrp to mount system as r/w because without this twrp cannot flash system.img.
I don't understand last paragraph. Will you please explain more?
Click to expand...
Click to collapse
TWRP can flash the image without mounting system r/w. That is most likely what is breaking your OTA. Once the system is mounted r/w, it breaks dm-verity, even if you make no modifications.
You should start over and not allow system to be mounted r/w.
HTC sync manager can RUU most modern devices if you connect them in download mode with the software open.
It can be downloaded from HTC's website. I normally wouldn't recommend it since it usually interferes with fastboot and adb if it is installed.
Hi
My Honor 6x is rooted with magikmask bootloader unlock and TWRP.
Actualy build BLN-L21C432B151 I want to update to BLN-L21C432B360 but I don't know how to do
Can some one help me please
do you ever received update from updater app
The OTA say's me to update if that's your question
then update dude .. after update your root will be removed , root again
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Deecy said:
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Click to expand...
Click to collapse
some times the bootloadet will lock after big updates so better to backup your data and then relock again and flash twrp
Deecy said:
Ok. Want to be sure when I was looking on internet some people said it's imposible to update with a bootloader unlock
I'll update and root again Thank's
just one other think if I update will I need to re unlock bootloader and TWRP ?
Click to expand...
Click to collapse
Did you manage to update your system? I tried everything, always getting an error that the update can't get verified.
I have a rooted, unlocked twrp system on android 7.0 EUMI 5.0 (BLN-L21,Honor 6x)
already tried to flash stock recovery, remove magisk(root), busybox but I still can't update the system.
I would really appreciate the help.
Try dload method with latest furmware
narshi shukla said:
Try dload method with latest furmware
Click to expand...
Click to collapse
That will also work.
citizenserious said:
Did you manage to update your system? I tried everything, always getting an error that the update can't get verified.
I have a rooted, unlocked twrp system on android 7.0 EUMI 5.0 (BLN-L21,Honor 6x)
already tried to flash stock recovery, remove magisk(root), busybox but I still can't update the system.
I would really appreciate the help.
Click to expand...
Click to collapse
You can do via dload only. Earlier i uswd to update just by flashing the stock recovery but recently on 6X this messed up badly may be volte and hence update failed and then it gave me to download the full firmware with prompt as your data partition is messed up amd needs to be fixed and after downloading the fill OTA update, got success. But then proceeded with debranding the next night
shashank1320 said:
You can do via dload only. Earlier i uswd to update just by flashing the stock recovery but recently on 6X this messed up badly may be volte and hence update failed and then it gave me to download the full firmware with prompt as your data partition is messed up amd needs to be fixed and after downloading the fill OTA update, got success. But then proceeded with debranding the next night
Click to expand...
Click to collapse
Hey brother, i tried many times to update from B360 to B365 (not full package, only 547MB) reflashing stock B360 recovery, but i always receive errors while recovery is verifying the package. I tried even dload method with .zip archives but i always achieve a failure and it is just boooooring :silly: You know other methods to try? Like adb or terminal emulator commands to update, or else... I cannot figure out how to correctly update my device. I have both B365 packages, FULL or partial OTA update downloaded. Thanks in advance
RedSkull23 said:
Hey brother, i tried many times to update from B360 to B365 (not full package, only 547MB) reflashing stock B360 recovery, but i always receive errors while recovery is verifying the package. I tried even dload method with .zip archives but i always achieve a failure and it is just boooooring :silly: You know other methods to try? Like adb or terminal emulator commands to update, or else... I cannot figure out how to correctly update my device. I have both B365 packages, FULL or partial OTA update downloaded. Thanks in advance
Click to expand...
Click to collapse
Cant believe you are facing issues now who helps every new user.
Nope bro. I still recommend to use dload only to flash full firmware. It should be full firmware and not the 547 MB.
Just to be in stock and use one of the app today, I relocked bootloader but then got the prompt as my data partition is damaged and need format. I allowed and then it was only erecovery and bootloader.
Then i unlocked and it went straight to twrp. And from there reboot to system works fine. I have the files and once really needed i will dload but problem with stock is that it doesn't have in-built call recording.
Edit-What is exact firmware BLN-L21CXYZB365?
shashank1320 said:
Nope bro. I still recommend to use dload only to flash full firmware. It should be full firmware and not the 547 MB.
Just to be in stock and use one of the app today, I relocked bootloader but then got the prompt as my data partition is damaged and need format. I allowed and then it was only erecovery and bootloader.
Then i unlocked and it went straight to twrp. And from there reboot to system works fine. I have the files and once really needed i will dload but problem with stock is that it doesn't have in-built call recording.
Edit-What is exact firmware BLN-L21CXYZB365?
Click to expand...
Click to collapse
Well let's say that looks like it's my turn now; Huawei mechanisms are much complicated sometimes, a little detail can let you puzzle an hour like and maybe it's only a joke. My previous device was a Samsung, so except common Android related functions EMUI is a new world for me. Only full firmware will work so, ok. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"? I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
However if you need call recording function (me too), there's a working method posted by an user in this thread https://forum.xda-developers.com/honor-6x/themes/callrecord-t3650864 that enables official call recording function from EMUI, check it. I followed this months ago on my BLN-L21, who had no call record at all by default in my firmware, and it flawlessly worked. I recommend it to you.
RedSkull23 said:
. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"?
I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
However if you need call recording function (me too), there's a working method posted by an user in this thread https://forum.xda-developers.com/honor-6x/themes/callrecord-t3650864 that enables official call recording function from EMUI, check it. I followed this months ago on my BLN-L21, who had no call record at all by default in my firmware, and it flawlessly worked. I recommend it to you.
Click to expand...
Click to collapse
I was using Tez app from play store but it didnt work may be because i am rooted with unlocked bootloader and need to bypass the safety check.
For call recording, I am already usimg a zip since debranding and works fine. I have Posted in 5C repository. But we need to be rooted for this with custom recovery.
If you are rooted then can take twrp backup and restore apps if on stock and non rooted then hisuite.
As far as i have tested on my 5c, dload won't wipe data but still i would recommend to have full backup brother.
---------- Post added at 11:31 AM ---------- Previous post was at 11:16 AM ----------
RedSkull23 said:
Only full firmware will work so, ok. Do i have to reinstall every app, or modify again my whole settings menu if i update using the full firmware package, i suppose..? What do you mean with "use one of the app today"? I didn't relocked bootloader because i thought that stock recovery could be enough. Overall, the risk to encounter an error like yours would be a bore, generally. Which files are you referring to, update files? My full build number is BLN-L21C432B360, I'm trying to update to B365.
.
Click to expand...
Click to collapse
BLN-L21C432B365 full firmware-
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v93141/f1/full/update.zip
shashank1320 said:
As far as i have tested on my 5c, dload won't wipe data but still i would recommend to have full backup brother.
---------- Post added at 11:31 AM ---------- Previous post was at 11:16 AM ----------
BLN-L21C432B365 full firmware-
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v93141/f1/full/update.zip
Click to expand...
Click to collapse
Surely I'll take a backup pal, i already got burned time ago and now i never do something without doing a nandroid backup bfore Thanks for the link, but i already have the FULL package downloaded OTA stored on my PC, so as suggested even by another user today I'll try again dload method but with full package other than partial one, it shouldn't erase my data and even if it should, I'll have a system image.
Only one thing now; in the folder where OTA was saved on my phone, as habit i found 3 packages; update.zip, update_data_public.zip and update_BLN-L21_hw_eu.zip. In this case, in dload folder on my phone i have to extract all the zips or only the main update.zip and leave the other two zipped?
RedSkull23 said:
Surely I'll take a backup pal, i already got burned time ago and now i never doing something without a nandroid backup bfore Thanks for the link, but i already have the FULL package downloaded OTA stored on my PC, so as suggested even by another user today I'll try again dload method but with full package other than partial one, it shouldn't erase my data and even if it should, I'll have a system image.
Only one thing now; in the folder where OTA was saved on my phone, as habit i found 3 packages; update.zip, update_data_public.zip and update_BLN-L21_hw_eu.zip. In this case, in dload folder on my phone i have to extract all the zips or only the main update.zip and leave the other two zipped?
Click to expand...
Click to collapse
Extract and use only main update.zip, put all files in dload and it will do.
Have backup but I just tested and flashed full B340 again on my phone and no data loss.
shashank1320 said:
Extract and use only main update.zip, put all files in dload and it will do.
Have backup but I just tested and flashed full B340 again on my phone and no data loss.
Click to expand...
Click to collapse
Thanks for the tip brother!
So this evening i tried to use only the extracted files from the main update.zip in dload folder; then, via ProjectMenu, i choose software upgrade and loaded the update after reflashing stock recovery for B360, that i took from your repository thread, since that time ago i didn't made a copy of my stock recovery before flashing TWRP. What i obtained was a soft-brick, i really don't know why on earth because usually it just fails at 5% while verifying the package and stop, it reboots to system... so i flashed again TWRP from fastboot and now i'm restoring my backup made today.
Crap, Huawei just CAN'T make things like updating OTA such difficult! I uninstalled Magisk before doing that, but i think that it fails because i miss a clean stock boot.img. Anyway WTF all these steps for an OTA is foolish.
I provided a guide how I managed to update my rooted device and keep all my stuff, settings and apps and reroot.
Just take a look here:
https://forum.xda-developers.com/ho...rootet-h6x-t3684758/post74102863#post74102863
I already did two successful updates with this method.
If there is a question just ask in that forum.
RedSkull23 said:
So this evening i tried to use only the extracted files from the main update.zip in dload folder; then, via ProjectMenu, i choose software upgrade and loaded the update after reflashing stock recovery for B360, that i took from your repository thread, since that time ago i didn't made a copy of my stock recovery before flashing TWRP. What i obtained was a soft-brick, i really don't know why on earth because usually it just fails at 5% while verifying the package and stop, it reboots to system... so i flashed again TWRP from fastboot and now i'm restoring my backup made today.
Crap, Huawei just CAN'T make things like updating OTA such difficult! I uninstalled Magisk before doing that, but i think that it fails because i miss a clean stock boot.img. Anyway WTF all these steps for an OTA is foolish.
Click to expand...
Click to collapse
Sorry to hear you that bro.
I myself flashed the same firmware yesterday to test this without backup (hisuite backup taken on 7th). I did via dload the same firmware and it was successful without any data loss, but yeah, I lost root, call recording feature that I flashed 20 days back.
I was planning to return to full stock because I know OTA will mess up if received on this state.
Not sure what went wrong buddy with your case. If it is due to any of the file in repository, I apologise for it.