B170 update arrived

[clsA]

Any idea how the phone installs this OTA zip file?

Is the updater-script failing because of assert statements for cust and system?

Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?

Thanks for your efforts on this and answering my questions.

Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before?

No, but Flashify use to work on the Honor 5x

The phone has it's own internal update tool that can only be started by the downloading of the update it's self
Firmware finder also has a function that will start the updater, but only if it downloads the update from Huawei's servers

This device is a cross between how AT&T does updates and how Huawei does them (it's a mess)

using the Huawei Update extractor you can pull all the files from the Update.app but your still missing the patched system and cust directories
Just flashing the update.app is pretty useless seeing it leaves you without wifi and does nothing to patch the system and cust

this only leave's one option flash the files in the update.app and a system.img and cust.img pulled from a already updated device
This is how all the B1xx_ full_update.zips work

So in a nutshell we need a phone with a locked bootloader to take the update to b170 / then unlock the bootloader (which wipes the device)
Boot TWRP and backup
boot.img
cust.img
firmware.img
recovery.img
system.img
and share them with us

 

[Paisley Pirate]

I was worried that might be the case - gotta "sacrifice a virgin" each time to get the rest of us updated.
Have I mentioned that I hate sloppy code? (looking squarely at you, Huawei and ATT)

Thanks for the effort!

 

[divineBliss]

If anyone here has a Huawei Ascent XT with B160 that they know has cust and system which maybe came with the phone or got updated OTA (but not using any ROM from here, could they please make a TWRP backup of their virgin cust and system partition images and post them somewhere where they can be downloaded. Please include the .md5 file too. The phone would have to be bootloader unlocked (but not necessarily rooted - I believe ) so TWRP could be used to get the cust and system images.

I'd just like to rule out that the B160-to-B170 update zip is not failing because we maybe don't have virgin B160 cust and system images (due to debloating or any other user mods). Thanks!

Of course the B170 virgin images like @clsA requested would be most desirable too.

 

[madvane20]

ill see what i can do guys i havent been on here much be busy with rl stuff but i will see and report back

 

[clsA]

If anyone here has a Huawei Ascent XT with B160 that they know has cust and system which maybe came with the phone or got updated OTA (but not using any ROM from here, could they please make a TWRP backup of their virgin cust and system partition images and post them somewhere where they can be downloaded. Please include the .md5 file too. The phone would have to be bootloader unlocked (but not necessarily rooted - I believe ) so TWRP could be used to get the cust and system images.

I'd just like to rule out that the B160-to-B170 update zip is not failing because we maybe don't have virgin B160 cust and system images (due to debloating or any other user mods). Thanks!

Of course the B170 virgin images like @clsA requested would be most desirable too.

all my tests were done on a clean install of B160_Full which includes Stock unaltered System.img and Cust.img , Boot.img and Stock Recovery
the phone was as stock as you can get it (aside from relocking the bootloader which can't be done)

No other backups for B160 are needed we have had these for quite some time
https://www.androidfilehost.com/?w=files&flid=170788

 

[divineBliss]

Where did that B160_Full come from? Can you guarantee that the cust.img and system.img weren't modified in any way from the original B160 stock files? Because I know I can go rename folders (and maybe delete files) in cust and system and the phone will still work - even though bytes were significantly changed from the original stock cust and/or system images. I'm trying to eliminate cust and system modification from being the cause of the assert failure when trying to install the B170-OTAupdate zip file - unless you can explain that.

So I'm still requesting another virgin B160 cust and system image from an independent source for that reason ..... it will make me feel much better to eliminate that as a possible reason for failure/cause of the assert failure .

all my tests were done on a clean install of B160_Full which includes Stock unaltered System.img and Cust.img , Boot.img and Stock Recovery
the phone was as stock as you can get it (aside from relocking the bootloader which can't be done)

No other backups for B160 are needed we have had these for quite some time
https://www.androidfilehost.com/?w=files&flid=170788

 

[madvane20]

wont matter cause we tried with b150 b140 etc no go think its just bootloader

 

[clsA]

Where did that B160_Full come from? Can you guarantee that the cust.img and system.img weren't modified in any way from the original B160 stock files? Because I know I can go rename folders (and maybe delete files) in cust and system and the phone will still work - even though bytes were significantly changed from the original stock cust and/or system images. I'm trying to eliminate cust and system modification from being the cause of the assert failure when trying to install the B170-OTAupdate zip file - unless you can explain that.

So I'm still requesting another virgin B160 cust and system image from an independent source for that reason ..... it will make me feel much better to eliminate that as a possible reason for failure/cause of the assert failure .

The b160 system and cust.img came from @cyclops13
The phone was untouched before taking the update and then bootloader unlocked and Booted TWRP So we could get the files exactly as your requesting them.

found it here >> https://forum.xda-developers.com/showpost.php?p=71809395&postcount=1671

 

[clsA]

I have some progress
FlashFire was able to patch the System
it went through all the steps up to flashing the update.app and then failed

Removing unneeded files...
Removing empty directorys...
Patching system files... (this took a long time)
Unpacking new files...
write radio image...
error : oemsbl version write error!
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip: update package from zip failed

 

[divineBliss]

That's awesome . Did it patch cust and system? Does the phone still boot up? Does WiFi not work now as in the past when firmware and cust / system are from different versions?

Phone Settings showing B170 after above steps or what?

I've been afraid to try Flashfire due to the Huawei incompatibility warning. Have you used Flashfire to flash other zips on the Ascend XT successfully?

Thanks

I have some progress
FlashFire was able to patch the System
it went through all the steps up to flashing the update.app and then failed

Removing unneeded files...
Removing empty directorys...
Patching system files... (this took a long time)
Unpacking new files...
write radio image...
error : oemsbl version write error!
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip: update package from zip failed

 

[clsA]

That's awesome . Did it patch cust and system? Does the phone still boot up? Does WiFi not work now as in the past when firmware and cust / system are from different versions?

Theirs no real way to know what gets patched. But unfortunately the phone does not boot after the patching is complete.
SuperSU also can't patch the boot.img (something about ramdisk fails). Flashing only the update.app results in the normal firmware mismatch and no Wifi.

Phone Settings showing B170 after above steps or what?

No only the kernel shows the update to June 2

I've been afraid to try Flashfire due to the Huawei incompatibility warning. Have you used Flashfire to flash other zips on the Ascend XT successfully?

Thanks

I know about the warning but took a chance... the phone's not bricked, but it also won't boot
forcing you to go into fastboot and boot TWRP to reflash B160_Full.

I also tried using Firmware finder, but had no luck.

 

[SuperBrolySSJ]

I'm on the B170 Firmware. Im guessing none of the roms for the ascend XT work on the b170 firmware?

By the way: anyone needing a B170 backup, let me know. I have one

 

[madvane20]

can u make a backup with twrp and upload it then i will update my rom

 

[SuperBrolySSJ]

can u make a backup with twrp and upload it then i will update my rom

Are you sure it's going to work? Don't want to brick your xt

 

[madvane20]

Are you sure it's going to work? Don't want to brick your xt

yea private message me it i know i wont brick my phone xd

 

[Paisley Pirate]

Just for S'n'G I tried running the update app - got 170 running, but with the same ol' no wifi bug going on. took 5 reboots before it finally took off... even so - no wifi...

So, back to 160 I went - stable again.

SuperBrolySSJ - that would be really cool if you can get the backup of the complete 170 running. Thanks in advance!

 

[divineBliss]

@SuperBrolySSJ,
If you can make a full TWRP backup and upload it somewhere shareable, I'd really appreciate that.

I'm on the B170 Firmware. Im guessing none of the roms for the ascend XT work on the b170 firmware?

By the way: anyone needing a B170 backup, let me know. I have one

---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------

"got 170 running" - how . If you had no WiFi, then you didn't really have B170 completely installed.

Just for S'n'G I tried running the update app - got 170 running, but with the same ol' no wifi bug going on. took 5 reboots before it finally took off... even so - no wifi...

So, back to 160 I went - stable again.

SuperBrolySSJ - that would be really cool if you can get the backup of the complete 170 running. Thanks in advance!

---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------

"got 170 running" - how . If you had no WiFi, then you didn't really have B170 completely installed.

Just for S'n'G I tried running the update app - got 170 running, but with the same ol' no wifi bug going on. took 5 reboots before it finally took off... even so - no wifi...

So, back to 160 I went - stable again.

SuperBrolySSJ - that would be really cool if you can get the backup of the complete 170 running. Thanks in advance!

 

[Paisley Pirate]

@SuperBrolySSJ,
If you can make a full TWRP backup and upload it somewhere shareable, I'd really appreciate that.



---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------

"got 170 running" - how . If you had no WiFi, then you didn't really have B170 completely installed.



---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------

"got 170 running" - how . If you had no WiFi, then you didn't really have B170 completely installed.

Troll semantics ?

Maybe "limping" would be a better description... [emoji12]

Sent from my H1611 using Tapatalk

 

[divineBliss]

Okay, so how did you get it to limp B170 ? It's all a learning experience.

Troll semantics ?

Maybe "limping" would be a better description... [emoji12]

Sent from my H1611 using Tapatalk

 

[Paisley Pirate]

Okay, so how did you get it to limp B170 ? It's all a learning experience.

Same method as clsa did so far as I can tell. Used supersu and flashed the update app. Since mine has done odd things since it was new with regards to taking updates, I was hoping for something different.

Don't have anything much to add, just confirmation that partial updating appears to be a no go.



Sent from my H1611 using Tapatalk