Database Develop

[Q] Sort Me out on 4.4.3 update

The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.

pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.

That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?

OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks

@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.

So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.

pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm

[Q] Stock Kernel

Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you

Linkalex1 said:
Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you
Click to expand...
Click to collapse
I believe someone has posted the stock boot.img somewhere(I can't seem to find it). You can also take the boot.img from the Stock Rom here

I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you

Linkalex1 said:
I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you
Click to expand...
Click to collapse
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.

csoulr666 said:
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.
Click to expand...
Click to collapse
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?

TomTomGo! said:
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?
Click to expand...
Click to collapse
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.

csoulr666 said:
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.
Click to expand...
Click to collapse
I've tried what you did. Seemed to update Bootloader, Recovery and Radio.
Then I rebooted, again got the update notification and tried to install it.
Bit still the same error, software update still fails.

Couple of questions about rooting

Hi there, I am currently running B383 on my P9, and really want to root it. However when I do, will I still be able to get future updates to the software? Do I need to unroot and lock bootloader first?
Also when the bootloader is unlocked, a message is displayed at boot about your phone being unsecured and non-trustworthy, is it possible to remove this message? (I used to have a moto g with an unlocked bootloader, and I flashed some file to remove the warning).
Thanks

I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.

..

benjamen50 said:
I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.
Click to expand...
Click to collapse
Thanks for the quality answer, I have no doubts anymore!

New B390 OTA update

For VIE-AL10 the new firmware update B390 is out. However, currently I am on B356, rooted and TWRP installed. However, when I do the OTA update it restarts into TWRP (because stock recovery is gone). I can't find a download to stock recovery for B356. How else can I installed this OTA update? I've tried dload folder way but with no avail. Any help would be appreciated.

you wont be able to install stock ota whilst you are rooted with twrp. You are going to have to go back to stock and with no root to do the ota, use this tool its worked for me in the past.
https://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999
PLEASE READ ALL THE THREAD BEFORE USE
if you do have questions ask in that thread

So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?

go into twrp
advance -> files manager -> /dev/block/platform/hi_mci.0/by-name/
copy recovery2 to SDcard (or other place)
rename copied recovery2 to recovery
recopy the file to /dev/block/platform/hi_mci.0/by-name/
reboot

Deviatorz said:
So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?
Click to expand...
Click to collapse
It should show updates, set your region to china in hicare after a reboot check it. If still nothing then post in the thread that I left a link for

Sorry for late reply. It started to show the update after a week. Not sure if the other methods worked but it showed up. I have a feeling it's because huawei decided to pull the firmware temporarily.

ME176C LOLLIPOP UPDATE !FIXED!

Greetings,
in a last month or so, im trying to revive this tablet, mostly because of the dual boot posibilities, but that can be done only with lollipop uefi bios.
My device is currently running 4.4 .201 OTA and im unable to update to 5.0 with whatever step i do.
First of all, i hard bricked my first device of this model myself completely, so i decided to replace my motherboard, somehow i lost the side buttons aswell, so i did order a "non-working" device from e-bay. I made it working by just flashing the .182 firmware.
I wasnt able to apply OTAs to the device, always got Status 7 Error in recovery, i did fix that by using a modified update script that i had to apply to every single OTA i flashed.
Finally got to 201, now its time to go to Lollipop.
I tried
- flashing LP firmware through temporary recovery (CWM/TWRP)
- flashing every single firmware thats available - .17; .24; .33; .36 - every single one with the KK "prefix"
- flashing every single firmware with the official firmware update method aswell (putting the update file to root of internal/sd memory and applying it within the tablets system
- flashing the official OTA updates that arrived as dlpkgfile
- flashing the firmware with the command file (putting renamed firmware to update.zip, to /data/ + command file to /cache/recovery/
- flashing service firmware with Intel Phone Flash Tool (KK/LP)
- reseting data/factory reset before and after the update, with cache included
- restoring both backups of KK/LP
- flashing boot.img extracted from the ROM after applying the update
Maybe im missing something, but in every single case, the update went through (some maybe had error in TWRP, but were fine in CWM/stock), but the system doesnt upgrade itself.
The update completes, then after a system reboot the device just goes to the ASUS logo (first one), gets stuck for roughly 30 seconds and bootloops. The droidboot/bootloader is not changing after update.
Any ideas on how to proceed now? I believe i tried every single method of updating, could not suceed unfortunately.
Thanks!

FIXED
The original system update process (putting update file in the root of sdcard,blablabla) always ended up on like 70% and rebooted, with no bootloader upgrade.
So the system didnt boot up, had to revert back to kitkat.
I found OTA Verifier app, that verifies the update script and selects the error in it.
I saw, its saying my device model number is K013_1, but thats not true! For some reason i had 2 build.props in my system files, so i rooted, deleted build.prop_K013_1 (or some name like this) and kept the original one.
! The update itself didnt give any kind of error, it went through without saying anything, thats why i didnt think the updater script would be the problem!
I believe, just deleting the first 2 lines in the update script would help aswell.
After that, i applied the update and waited for it to finish, at 70% once again it rebooted, but this time it started upgrading the bootloader. Lollipop installation finished and im finally at 5.0