Database Info

[Q] updating to 4.4.4 errors (LTE xt1045)

I have an unlocked bootloader, and am rooted. I've flashed TWRP before previously to root and have since reverted back to stock recovery. I've been trying to update the firmware to 4.4.4 as I have class 10 microsds that I can't currently use. Unfortunately when I try to update via the OTA it shows
installing
Click to expand...
Click to collapse
until I get an error code of just
error!
Click to expand...
Click to collapse
.
I've looked, and haven't seen the 4.4.4 firmware online anywhere that I can download and push. Is there anything I'm missing or any workarounds that are known? Are there any ROMs that have these fixes integrated?
Thanks

kdbrown5 said:
I have an unlocked bootloader, and am rooted. I've flashed TWRP before previously to root and have since reverted back to stock recovery. I've been trying to update the firmware to 4.4.4 as I have class 10 microsds that I can't currently use. Unfortunately when I try to update via the OTA it shows until I get an error code of just .
I've looked, and haven't seen the 4.4.4 firmware online anywhere that I can download and push. Is there anything I'm missing or any workarounds that are known? Are there any ROMs that have these fixes integrated?
Thanks
Click to expand...
Click to collapse
Just choose the one you like more:good::
link1
link2

Thanks! It failed flashing with TWRP so I'm assuming I have to use fastboot to push it similar to http://forum.xda-developers.com/showthread.php?t=2542219
I'll be doing it tomorrow as I want to back up a few thing before this wipes my data. Do you know what the difference in those 2 files are? I was going to use the (link 1) RETAIL-CA-SS instead of the (link 2) AMX-PE-SS as it was a few days newer.
edit:
The ones you linked are cid 12 and cid 14. According to this, I would be wanting cid9 for USA
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619

Possible To Flash Oreo Rom Via TWRP Recovery?

I am currently on Android Nougat stock.
The bootloader has been unlocked and TWRP recovery has been installed.
I would like to update to Oreo but have been unable to do so.
This guide was followed [urlhttp://www.droid views.com/install-android-8-0-oreo-based-emui-8-0-huawei-mate-9/][/url] (but was unable to get past option 4) (I left a space after droid as the link is getting blocked, just put ********** together.)
''Double-click on the Replace_Recovery.bat file in the extracted HWOTA8 folder. This will install TWRP recovery on your device.''
I keep getting a failed notification when trying to do so. The handset was in fastboot mode but refuses to update recovery.
Am I able to update to Oreo with the old TWRP recovery & update it after? I am running the old Nougat version.
Option 7 I also got stuck on. '' Create a folder named HWOTA8 on your device’s internal storage.'' whilst connected via USB to the computer.
I am unable to view internal or external storage when the USB is connected to the computer. When viewing internal/external memory normally I can see items as normal in external SD card but the internal memory files all appear jibberish even in recovery.
What am I doing wrong? I have been unable to find any clear guides of how to update from Nougat to Oreo including flashing the rom, flashing recovery and root.
Thanks for those able to help.
PS. I'm a new Huawei Mate 9 owner and have only just received the device several hours ago which is why I'm rusty. Compared to my previous Sony Xperia XZ Premium it is much more complicated. Sony was far easier to flash recovery and flash roms via recovery.
I am having the MHA-L29 international version.

Device now bootloops after following the guide of flashing SuperSU in recovery. I did what was said and received ''error 9'' after flashing the files.
Now bootloop.
Good news at least recovery is working but unable to boot. How to I update to Oreo with updated recovery & root?

Otherwise is THIS guide safe to follow:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656

Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.

kanej2006 said:
Could not even get past option 4. ''Do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with c636 oeminfo: http://www.mediafire.com/?szws87sk7rrkqr6''
Permission denied error.
Click to expand...
Click to collapse
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.

ante0 said:
Unless you want to rebrand to a different cust, don't follow this.
Do you know what your current firmware build is?
MHA-LxxCxxxBxxx
Click to expand...
Click to collapse
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.

kanej2006 said:
Good thing I never went ahead with that!
I'm on international MHA-L29C185B182.
Thank goodness I was able to restore Nougat as I backed up with TWRP recovery.
However, what is the easiest way to upgrade to the latest Android Oreo 8? At the moment I'm on stock 7 Nougat but am rooted with TWRP recovery.
Click to expand...
Click to collapse
Check my post, I edited while you posted this.
Or you can use this one, it's basically the same anyway, only difference is that you use a .bat file: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Use the same steps as I wrote above for downloading the update files as this was not the way to do it when that guide was written.

^ It seems the model I have is not found? After several attempts it is not finding my model.

kanej2006 said:
^ It seems the model I have is not found? After several attempts it is not finding my model.
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.

ante0 said:
http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C185&firmware_page=0
Here are links you need:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v120294/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...94/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
Rename update_data_full_public.zip to update_data_public.zip and update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
There is a B371 too, but it was released before b370 so probably a test build.
That guide in OP seems to be a mixup. It uses the HWOTA8 files, which are for Oreo, so that's probably why it gave you errors.
Click to expand...
Click to collapse
Thank you so much ante0 for all the information, it was very helpful. I am now downloading the above three files. Once complete I will rename them as mentioned and flash hwota7_update.zip in TWRP recovery. Will let you know shortly the outcome!

Cheers ante0, finally got my phone fully updated to Android 8 Oreo following your guide. Thank you so much! If it was not for you this would not have been possible!
The other links I was looking at were outdated as you mentioned and the instructions you provided were better. I appreciate your time to help me.
Upon booting, my EMUI version is now 8.0 and Android Version 8.0.
I will now follow this link for getting root:
https://forum.xda-developers.com/mate-9/how-to/discussion-root-mate9-oreo-emui-8-0-how-t3712495

@ ante0, I was able to get recovery and root but had to once again unlock bootloader...

kanej2006 said:
@ ante0, I was able to get recovery and root but had to once again unlock bootloader...
Click to expand...
Click to collapse
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.

ante0 said:
Great. I would suggest Magisk but that's up to you to decide
Bootloader getting locked is normal when updating Nougat to Nougat and Nougat to Oreo. Oreo to Oreo is stays unlocked.
Click to expand...
Click to collapse
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:

Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
kanej2006 said:
I did not see any guide for Magisk, guess I missed it.
Anyway there are pros and cons for both, though I also prefer Magisk. Either way they both do the job, root access.
All is good now. I am very happy with the phone. Still not even been 24 hours since I received it yet already the bootloader has been unlocked, TWRP recovery and root. Nice :good:
Click to expand...
Click to collapse
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse

seti007 said:
Great and very helpful thread. thanks for everyone who's contributed to it. I'm trying to do the exact same thing coming from ROM Aur. Do you think I can use the same exact process is yours coming from a custom ROM? Did you have to do the boot loader unlock in order to Root? If there are no custom roms then perhaps the boot loader unlock is unnecessary? In order to install Magisk to root, what are the prerequisits? Do I need to reinstall TWRP? If so , is there a link to the correct version? Are there any other pointers that you can give me that you found out while doing this whole process? Thank you so much
---------- Post added at 01:33 AM ---------- Previous post was at 01:02 AM ----------
Thanks for the guide!! Very helpful. However, Before I can even start following it, I'm running into some issues. The challenge that I'm facing is that I'm currently on a custom ROM (ROM AUR) and I do not know what my firmware build is. The box only tells me what the model number is and it's the MHA-L29. how would I find my firmware build ? The phone was purchased at bestbuy in the US.
Thanks again
Click to expand...
Click to collapse
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.

ante0 said:
Bootloader getting locked is normal when updating Nougat to Nougat
Click to expand...
Click to collapse
The bootloader (i.e. fastboot) is always locked (btw, is there an easy way to unlock FB Lock ?), you probably mean the 'USER Lock'. And the 'USER UnLock' is damaged only if you flash some random oeminfo files (which is a very dumb decision anyway).
This mechanism is documented in the USENIX paper i have linked in the OEMINFO thread.
---------- Post added at 12:19 PM ---------- Previous post was at 12:00 PM ----------
kanej2006 said:
Sony was far easier to flash recovery and flash roms via recovery.
Click to expand...
Click to collapse
It may be "easier", but Mate 9 is probably one of the most unbrickable smartphones that i know, because it can be recovered even if you manage to destroy 'partition table+xloader+fastboot' (the really critical parts, other partitions can be recovered without opening the phone case).

kanej2006 said:
You can do the exact same process, however, I strongly suggest you follow the above guide from ante0. His guides are clear and upto date. Other guides were unclear and old not being upto date.
And yes, you must have an unlocked bootloader to flash a rom, however it is very easy to do. There are many guides which tell you how to do so. Simple fastboot commands when your phone is set to fastboot mode. You only need the unlock code via Huawei's website.
With regards to Magisk/SuperSU, yes, you must have a working recovery in order to flash either one. Without recovery you cannot get root access. I suggest you flash SuperSU as it is far easier than Magisk, a simple two step procedure!
What Android version are you on? Nougat or Oreo? Beware that when flashing recovery and root, it must be for the correct Android version. And of course if updating to Oreo, once again you will need to flash recovery and root made to run on Oreo to prevent issues and boot loops.
Do you not have the box that came with your device? I am guessing you have the international MHA-L29 version as I do, but you must be sure.
Click to expand...
Click to collapse
Yes I intend to follow the awesome guide from ante0 (thanks for that ante). I'm on Nougat currently. After following the above method, I guess I will have a fully factory locked phone? SO, I will have to first install recovery, then root. Correct? I do have the box but it only says the model number MHA-L29. Nothing on firmware but since its a US phone bought here, I'm fairly confident that its a MHA-L29C567B183. Although when i installed ROM AUR I used the version for L29C432 and it worked. Which one would you try if you were me? Will I brick the phone if the version is incorrect? If that happens, how do i return to oreo stock from there? Do you have any links for the right Recovery and root?
Thanks and sorry for so many questions.
UPDATE-- So have an update. I was able to install oreo using the method listed above. everything seems to be working fine. however I'm getting an error 255 message while creating a backup I'm using TWRP. Thinking that my data partition needed decrypting, I deleted it and rebooted the phone. Set it up and then went back into TWRP. I'm still getting the same backup error. any ideas? The route also installed and works fine . My concern now is that I would end up with I found that cannot be backed up with TWRP. BTW. I installed TWRP 3.2.1-0 from here https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967.
Thanks

^ 1 Thing hopefully you did not forget, before flashing the rom, you must ''wipe data'' from TWRP recovery otherwise you will get bootloop and the encryption issue. Did you wipe data from recovery prior to flashing? Encryption is removed/disabled when wiping data in recovery.
Glad you got somewhere at least. If it wasn't for the guide from Ante0, I'd still be bootlooping on Nougat.

ante0 said:
The guide in OP is outdated, and it only has the oreo beta builds.
Do you know what your current firmware build is?
MHA-LxxCxxx
(It should be printed on the box of your Mate 9)
Next go here http://pro-teammt.ru/firmware-database/ and enter your model and cust in the search box (Example, MHA-L29C432)
Official Oreo builds begin at B360, if you happen to be at C432 the latest is B364 (Ok, it's B365 but it seems to be a test build and was released before B364 so January patches.)
Click the 'update' link in the FullOTA-MF row, download update.zip.
Click on the 'file list' link in the FullOTA-MF row, copy link of update_data_full_public.zip and paste into a new browser tab, this downloads the zip.
Do the same with L29 or L09 hw data, depending on your version.
Next rename update_data_full_public.zip to update_data_public.zip, rename the L29/L09 hw data zip to update_all_hw.zip.
Place update.zip, update_all_hw.zip and update_data_public.zip in the HWOTA folder on your sdcard.
Download this zip: https://mega.nz/#!RaAQDLqY!pgBcA5tcy4ewvROUxei3af59hns4YtkeFPC5_WCyV6g (Note, this is only for Nougat to Nougat or Nougat to Oreo, does not work in Oreo as partitions changed and it flashes the NoCheck recovery to the correct partitions in Nougat. It will not flash correctly in Oreo)
extract and put hwota7_update.zip, MHA_RECOVERY2_NoCheck.img and MHA_RECOVERY_NoCheck.img in the HWOTA folder on your micro sd.
Put back mSD in phone and boot to TWRP, flash hwota7_update.zip and wait.
Phone should now reboot and start updating.
This is basically the HWOTA8 zip for updating Oreo or downgrading to Nougat, all props to @mankindtw.
All I did was change the partitions to flash so they match Nougat's partitions.
Click to expand...
Click to collapse
@ante0
can i use these commands to upgrade to O as well
the only difference in the folder should be the hwota8 and the update zips for O ?
L09C316
d if=/external_sd/HWOTA/MHA_RECOVERY_NoCheck.img of=/dev/block/sdd33
dd if=/external_sd/HWOTA/MHA_RECOVERY2_NoCheck.img of=/dev/block/sdd30
echo --update_package=/sdcard/HWOTA/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA/update_all_hw.zip >> /cache/recovery/command

Problems with updating to the newest OTA 1.24.709.8 TW version U11+

Hello there.
I unlocked my bootloader a long while ago, then flashed TWRP on my TW U11+. Now recently I have seen that there's an update and I get the popup from my updater.apk on my HTC U11+.
My phone is on 1.24.709.7 update. And it's I think most definitely the ASIA_TW version.
Mid - 2Q4D10000
Cid - HTC__621
So I try to update but of course fail because my recovery was TWRP so of course that it did not work. Then I hear that you need to have stock recovery, so what I do is I get stock recovery.img, go to download mode and flash it through the command "flashboot flash recovery recovery.img. I get the success command and I reboot and try download the OTA once again, then I try to update it. It does go to stock recovery but then it "updates" til 25% and then it's stuck. Then after like 10 seconds it just simply gives my this Red Triangle with an exclamation mark in the middle of it. So I press power button and vol down to get off that mode and that's it. It won't update to the newest OTA.
I flashed 1.24.709.7 recovery at first. It didn't work then I flashed 1.24.709.8 recovery but still no avail.
Can you guys please help me? I really don't know what I am doing wrong.
Thanks in advance

I am having the exact same problem. I wish I had the HTC__621 recovery, but I haven't been able to find the correct one.
Hopefully somebody will see this. Every link that looks like the right thing is dead.

Same problem
I had the same problem, too.
But I find a way to update to 1.24.709.8.
That is: I decide to flash the 1.24.709.8 version's RUU .
Hope this can help you.
U11+ All TW version's image and OTA :
//drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3

Thanks for the link.
However the problem that I'm experiencing is that whenever I flash either 1.24.709.7 or 1.24.709.8 RUU. It just won't flash over fastboot. So what I do is I put it on my SD card then put the file and rename it to like 2Q4DIMG.zip and go to recovery and still won't flash it correctly.
I'll try it again today to see what error code I get from it.

Did you unlocked or rooted your u11+?

Sorry for the late reply man.
My HTC u11plus is unlocked and I also have rooted my phone via magisk.

You can't update with official ota if unlocked, you need to relock and have the stock recovery. Relock will wipe your data I think

You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.

I have also had the exact same issue with updating the latest OTA update. I have TW model, it was unlocked and rooted with magisk. I relocked bootloader, stock boot img and still the update wouldn't install. I even tried flashing 1.24.709.7 RUU in downloader mode but failed remote: 22 RU_HEADER_ERROR.
Would love any ideas or help.
*UPDATE*
Finally was able to update to 1.24.709.8 OTA. I needed up unlocking the bootloader again, then downloaded the 1.24.709.7 full image from
drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3
Extracted the rar file and manually installed the boot, recovery and system images separately and rebooted. Downloaded the update and installed, everything worked sweet!!

xymopen said:
You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.
Click to expand...
Click to collapse
Thank you very much for this. I will try this tomorrow or something.
I will post my results here.

Btw is there any update for Emea region? They did one a month ago for TW models and since then no words about Europe and Middle East

Does anyone have a link to 1.24.401.7 9.0_CL1010171 ? I'm trying to find stock recovery that matches with stock rom and can't find it anywhere.
Magisk and TWRP installed at the moment.
I've got stock boot.img backed up before installing Magisk but there was no way to boot (without flashing) TWRP in order to backup stock recovery that came with U11+.
Cheers

Update Issues after rooting my U12+

Hello,
I have some issues to update my U12.
I bought the phone near the release (carrier free) and tried to root it. It worked, but I used the boot.img method (flashing rooted boot.img via adb) instead of waiting for TWRP. In addition I can´t found the right boot.img for my firmware number, so I had to use a different one.
After some days the first update message showed up. (Version numbers at the end)
Because of that I removed root through the Magisk App, but my phone don´t want to update. I think it´s because of the different boot.img.
In addition it seems that fastboot can´t find the device anymore, so I can´t root it again. (adb is working, only fastboot, but I´m not shure after all)
Now my question: Can I repair and update it by flashing update.zip from SD Card?
-Will it replace the wrong boot.img (it should flash the updatet version)
-Should I flash the current firmware at first to get back to original boot.img or can I directly flash the update?
-Can I root it again after update (because the update surely will reinstall crap apps)
-Will my changes (below) doing anything against the update?
My current firmware: 1.15.708.6
update: 1.21.708.3
Things I did with root:
-delete crap (bloatware and the *** screenshot sound)
-adblock app with hosts
-giving root to screen recorder app so it can record internal sound

If you deleted some system apps you will not able to take update. Be sure to bring stock system back to take update . The simplest way is to find right ruu. from here https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/htmlview
Beware that all stuff will be deleted from your phone after ruu

do you know your CID?

fabrizio b92 said:
do you know your CID?
Click to expand...
Click to collapse
Simple CID Getter says
HTC_622
Asia-HK-CHT

ClickDE said:
Simple CID Getter says
HTC_622
Asia-HK-CHT
Click to expand...
Click to collapse
Ok, we need to restore smartphone functioning, download Ruu corrispondind CID
from here----> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
-After download rename the file with 2Q5510000 and copy it on sda card
-Reboot your smartphone in downlado mode adn automatically detect the file,if ask use buttons to flash the file
-Once the file has been flashed, your phone will reboot into the stock ROM
-IMPORTANT: this methos erase all your data, so make a backup
---------- Post added at 09:54 ---------- Previous post was at 09:41 ----------
if you have a rooted smartphone you can't update the firmware trought Ota,never,maybe brick smartphone.
There are 2 ways:
- RUU method, like above
- Restore backup recovery with update firmware

(If you have a rooted smartphone you can't update the firmware trought Ota,never,maybe brick smartphone.
There are 2 ways:
- RUU method, like above
- Restore backup recovery with update firmware)
(As I wrote in my question, I removed root to update)
I think there is a misunderstand. I want to install all updates in one day, AFTER I repaired the firmware flashing RUU. And I want to wait till Android 9 is released, because I want to root it again after update.
(Android 9 Release)>flashing Ruu to repair>install all updates till Android 9>root

ClickDE said:
(As I wrote in my question, I removed root to update)
Click to expand...
Click to collapse
Did you have restore stock recovery and relock the bootloader?

fabrizio b92 said:
Did you have restore stock recovery and relock the bootloader?
Click to expand...
Click to collapse
-I have stock recovery, I only flashed the boot.img with root
-bootloader is still unlocked. In additon I can´t lock it, because my phone won't be recognized in fastboot mode (as I wrote in my question.)

Please forget what I´ve written before. Start again.
At the very beginning there was no TWRP for U12, so I used the boot.img method to root my phone. But I used the from .img.
My question: Is there anyone with a boot.img from 1.15.708.6 (can´t found it in the Google Spreadsheet, only from 1.25.708.3)
Could I use the other boot.img?
Will I be able to update after flashing the original img or will I have to relock the bootloader?
Or can I only relock the bootloader and update without the correct boot.img?
In addition I´ve downloaded the Ruu for my CID 622 (from the Google Spreadsheet). But its 1.25.708.3. Can I flash it from SD card even with this big version difference? And can I flash it without relock the bootloader?
Thats my last try to update, if this won´t work I won´t annoy you anymore.

[REQUEST] TWRP or Stock boot.img

I want to install the Magisk but not achieved yet because of TWRP is not available and the stock boot.img not found.
Now OTA is coming(1.02.709.7), so I tried to obtain boot.img from the OTA image by the following steps but didn't succeeded.
Download the OTA image by checking the system update on the device.
The image will be stored on /sdcard/Download/OTA_1.01.709.1-1.02.709.7.zip
Copy the OTA image to PC and extract the file "payload.bin".
Use the payload dumper(Thanks to vm03), dump the boot partition from payload.bin but failed with the following error.
Processing boot partition.Unsupported type = 9
* Type of 9 is IMGDIFF according to what I found (no further info).
* I modified "payload_dumper.py" to dump only the boot partition.
Could someone please share the stock boot.img or TWRP for this device?
or tell me another way to achieve this.
Thanks.

I'm looking for it, too. :crying:
Did you get the 1.03.709.1 version boot.img file?

I don't think OTAs contain the whole boot.img, only the binary diff of the new version.
so far nobody has found a boot.img ? the device is around for some months now...

Is there still nothing? Not even a boot.img?

I will post my stock boot.img, recovery.img, and SW version # once I get to my computer.
Should be able to extract it with ADB/commands.

I'm not able to get anything using ADB/fastboot and no root method is working for me. I wish I had an OTA file to work with so I could patch the boot.img and try that but OTAs have already been done on this phone.
The only thing I've managed to do is unlock the bootloader.

Here is a copy of the OTA zip I'm running on
https://drive.google.com/file/d/122ky9if8FqTKz0tvqVi_8-FkA-GjHX9A/view?usp=drivesdk
And here is the payload.bin from that OTA
payload.bin
drive.google.com
So far I haven't managed to get the boot.img and I have a long day tomorrow. Maybe you guys can come up with something?

Well I downloaded the automated script version of payload dumper located here:
How to extract payload.bin from OTA update or firmware
In a few rare cases, you may need to extract the payload.bin that is part of firmware and OTA update files from some OEMs to get the stock boot and system images. This helps when you are looking un…
nerdschalk.com
And that payload.bin seems to only contain abl.img. Nothing else which is unfortunate.

like i've written before, the OTA simply does not contain the whole boot.img - only the binary difference from the previous build.
with only the difference it is not possible to reconstruct a whole boot.img
the only options i see is wait for a RUU or the kernel source to be published

Another OTA came through 227MB, extracted and only thing in there is abl.img again.

is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img

Did you get the 1.00.468.1 version boot.img file?

I'll try to port twrp this week.
Just wait for the good news

4096abcd said:
I'll try to port twrp this week.
Just wait for the good news
Click to expand...
Click to collapse
please make one also for htc u20 5g if possibile

lostic-b said:
please make one also for htc u20 5g if possibile
Click to expand...
Click to collapse
Still there's no way to unlock the bootloader of U20