I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
MD5 is: e684728237328c1a59c8c53ab2308467
I've now extracted the firmware.zip and created two update.zips, one without boot (but stock recovery) and one without both boot and recovery images. Someone reported to me that flashing the boot.img could be problematic -- I do not know the particulars, just reporting what I heard. I have not flashed these files, so you're on your own. If there are reports of problems, I'll pull the files.
2.41.605.20 firmware update (no boot) md5: 13b3461cbe2e1f9a8098d83115f501c8
2.41 605.20 firmware update (no boot; no recovery) md5: 97c1df3e7cbc9583b9916b4e1768f245
hgoldner said:
I have uploaded the OTApkg from my Verizon 10 downloaded 7/6/17. I have not been able to run it on my 10 because of customization issues.
I have also changed the suffix of the filename to "zip" so it could be uploaded. With past OTA's I've been able to extract the contents, but not so with this one. You may want to rename it before manipulating it. The default name is "OTApkg"
You can download it here and I welcome someone else's better ability to parse the file contents.
(Last OTA I actually ended up flashing with htc_fastboot partition-by-partition in download mode.)
Click to expand...
Click to collapse
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
kc6wke said:
I renamed mine also and was able to extract the contents. I have rezipped the files (Files only, not flashable) here is anyone wants them. Strange, 2gb ota but contents are 103mb. I did not install tho, just ran the update to pull the updated system img.
Click to expand...
Click to collapse
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
hgoldner said:
NVM. Reread your post. Do you think the firmware would be flashable if renamed 2PS6IMG.zip?
Click to expand...
Click to collapse
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
kc6wke said:
I just tried it and it flashed. But remove the boot.img first. The. 20 boot.img won't work on. 18.
Click to expand...
Click to collapse
Thanks, , my file may have been corrupted. Going to upload a file I could open on my workstation instead and re-link.
Original upload was corrupted; I've uploaded corrected file and added md5.
Added two firmware only update files, one without boot and one without boot or recovery.
Verizon getting Oreo ota
mattie_49 said:
Verizon getting Oreo ota
Click to expand...
Click to collapse
Yup.
hgoldner said:
Yup.
Click to expand...
Click to collapse
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
mattie_49 said:
Can I now flash Maximum or Lee-Droid Oreo roms without having to do anything other than installing twrp first? That is correct isn't it?
Click to expand...
Click to collapse
I would go by the OP's in each of those ROM threads, but presumably you are now on Oreo firmware, so I don't see why not.
Maximus doesn't do vzw..
Related
I am in the process of upgrading to the 4.03.605.1 rom posted here: http://forum.xda-developers.com/showthread.php?t=1830859, but I am having issues with the firmware upgrade package. My computer says the zip is corrupted, and the phone will not read it. Has anyone else had issues, or have a resolution? I checked the md5sums and they match.
Thanks
mustangz5 said:
I am in the process of upgrading to the 4.03.605.1 rom posted here: http://forum.xda-developers.com/showthread.php?t=1830859, but I am having issues with the firmware upgrade package. My computer says the zip is corrupted, and the phone will not read it. Has anyone else had issues, or have a resolution? I checked the md5sums and they match.
Thanks
Click to expand...
Click to collapse
is it a zip inside of a zip? zipception?
synisterwolf said:
is it a zip inside of a zip? zipception?
Click to expand...
Click to collapse
I tried to check that, but I can't even open the initial zip. Windows throws an error of "error [file]; start of central directory not found; Zip file corrupt. Possible cause: file transfer error."
mustangz5 said:
I tried to check that, but I can't even open the initial zip. Windows throws an error of "error [file]; start of central directory not found; Zip file corrupt. Possible cause: file transfer error."
Click to expand...
Click to collapse
Sounds like a bad download. I got that too from android police. Might try it again.
Sent from my iPhone...
synisterwolf said:
Sounds like a bad download. I got that too from android police. Might try it again.
Sent from my iPhone...
Click to expand...
Click to collapse
Yea I tried to download it a few different times, and tried from other websites too (which just link back to the same files). Had to put a recovery back on my phone so I could use it again after hours of trying to find the solution.
Anyone else have any ideas?
mustangz5 said:
Yea I tried to download it a few different times, and tried from other websites too (which just link back to the same files). Had to put a recovery back on my phone so I could use it again after hours of trying to find the solution.
Anyone else have any ideas?
Click to expand...
Click to collapse
you can get the global ruu right here.....http://bit.ly/RaKEAr
Thank you! Does this file contain both the firmware and the OS update? I was able to download the OS update just fine on the other page, just not the firmware.
Appreciate the help!
Actually - that zip file contains the same error as the other link. Anyone know of a different location of a non-corrupted file?
mustangz5 said:
Actually - that zip file contains the same error as the other link. Anyone know of a different location of a non-corrupted file?
Click to expand...
Click to collapse
Try the update to the global RUU. Found one on AndroidPolice but can't post link here yet. Just google androidpolice global ruu
Android zip files need 7zip if you want to look inside it.
Also check that you aren't renaming it as ph98img.zip.zjp because windows hides the file type by default.
So this was a two part issue! #1) post above was right about winzip not being able to handle the file.
Second issue was that I did not have the bootloader re-locked, which is required for this kind of update. I came from the tbolt which didnt require locking & unlocking.
delete
Hey me again.
So I just got an OTA update notification, but since I'm on a custom recovery, I can't install it. Don't suppose anyone would go to the trouble to re-package it as a flashable zip file for TWRP/clockworkmod?
Thanks.
flash recovery on OTA pack
There isn't any recovery and the firmware.zip can't be extracted
I'll have access to a full stock Asia phone that's had the update applied tomorrow. As long as the recovery.log is still in cache I should be able to work out which files where updated and create a TWRP update zip file from it.(If its just stagefright libs being replaced it should be compatible across regional roms)
I can provide the ota from Poland play version
porozex said:
I can provide the ota from Poland play version
Click to expand...
Click to collapse
Have you installed the update? Last time i tried i couldn't do anyrhing with a ota_update zip. But with a twrp /system backup and hopefully a recovery.log file from an updated rom, i think I can work out which files were updated and create twrp compatible update.zip based on that. The asia ota_update was only 87Mb in size and trying to address the stagefright bug from what I've seen. Is that the same for you?
No, I can't install it. Mine was around 38mb
edit: ok i found a solution, if you have a backup of your rom (i got it after got installed twp for first time) open it with winzip or 7zip then navigate to sytem>bin>bebuggerd and copy it to the phone. then with a filemanager with root privileges replace the current one and give proper permissions. thats it
For those who are interested and are on stock non-rooted and didn't receive the (german) update by now, here is the logcat link i took :
( i was already on B04(bootstack/system (Australia)) but couldn't help to go back to B02 to have the link and share it - of course back on B04 :cyclops: )
( http://dl1.ztems.com:80/zxmdmp/down...es/HK/ZTE/ZTE A2017G/406489/fota_B04_B06MR.up )
or here the same uploaded zip file with a "little" bit faster download speed
https://www.androidfilehost.com/?fid=817550096634768949
Rename to .zip (or try the .up file) ( you may even rename it to update.zip ...)
you don't have to upzip it
Put into root SD (external) or try internal storage
...and update via settings ( when on B02)
ps : when your phone won't detect the zip, you could try to wipe cache in stock recovery and reboot again and try to update again into settings menu
or update in stock recovery either via ADB sideload or update from SD
Enjoy !
Thanks Bro was looking for this.
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Hamburgle4 said:
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Click to expand...
Click to collapse
Unpack the zip-file, but it in the root of your phone or in the root of external sd card.
jopomopo said:
Unpack the zip-file, but it in the root of your phone or in the root of external sd card.
Click to expand...
Click to collapse
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory? ?
Hamburgle4 said:
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory?
Click to expand...
Click to collapse
Just rename. You don't have to unzip anything.
Although I did the update with the UP file once in adb sideload (in stock recovery) when I was on B01.
This is for non rooted users. It's just the clean, German original update from ZTE. Just for those who didn't get it by now.
Hamburgle4 said:
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Click to expand...
Click to collapse
Yes you can, either adb sideload or via update sd, all in stock recovery.
Or via the normal way when your phone detects the SD update. I have no idea why your phone doesn't detect the OTA on your SD by the normal way via settings. It should but this thing happens often.
Hamburgle4 said:
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory? ?
Click to expand...
Click to collapse
ooops, sorry my bad...didn't read the whole thread...thought you had the whole zip...I had similar problem with the .up file so the easiest way to do the update was downloading the whole firmware zip...
jopomopo said:
ooops, sorry my bad...didn't read the whole thread...thought you had the whole zip...I had similar problem with the .up file so the easiest way to do the update was downloading the whole firmware zip...
Click to expand...
Click to collapse
You mean the " australian " one. AFAIK there isn't already posted a german region whole firmware zip. (could be wrong)
Although i believe there won't be much difference in the end result
raystef66 said:
You mean the " australian " one. AFAIK there isn't already posted a german region whole firmware zip. (could be wrong)
Although i believe there won't be much difference in the end result
Click to expand...
Click to collapse
Jep, you are not wrong...there's no German full version released yet...I've used Australian one, and so far so good...
Sorry for the noob question ..I am on v1.0 B11..can I upgrade straight to this firmware or do I need to upgrade step by step ?
Sent from my ZTE A2017G using XDA-Developers Legacy app
First to 7.0 and then to 7.1.1
Hussainally said:
Sorry for the noob question ..I am on v1.0 B11..can I upgrade straight to this firmware or do I need to upgrade step by step ?
Click to expand...
Click to collapse
You can upgrade straight using the Australian full V1.2.0B04 ROM. It's 2GB++ file size. Extract the update.zip and put into the root directory of your internal storage or SD card. Then open the system update and it should detect the new firmware.
My phone doesn't detect the update from internal neither from SD. I tried both files, and cleared cache. Says my firmware is up to date, I'll wait till it pops up officially for my region
ГАСООП said:
My phone doesn't detect the update from internal neither from SD. I tried both files, and cleared cache. Says my firmware is up to date, I'll wait till it pops up officially for my region
Click to expand...
Click to collapse
Try in recovery. Either via SD or via adb sideload update.zip (put zip in adb folder PC)
(Also try all these steps with .UP instead of .ZIP)
Or flash the whole Australian zip bootstack + system. I'm running on that one. Or flash the original full Australian zip.
Possibilities enough
I know...the A7 can be stubborn :silly:
I am on the German B04..I have terrible mobile signal ..does anyone have a solution to improve the signal .?that's the only thing pushing me to sell this phone ...I love everything else about this phone ...please help
Sent from my ZTE A2017G using XDA-Developers Legacy app
Hussainally said:
I am on the German B04..I have terrible mobile signal ..does anyone have a solution to improve the signal .?that's the only thing pushing me to sell this phone ...I love everything else about this phone ...please help
Click to expand...
Click to collapse
You should try factory reset first.
MrMD69 said:
You should try factory reset first.
Click to expand...
Click to collapse
Ok will do ...but anyways I heard B02 has better signal..can I just flash B02 over B04?
Sent from my ZTE A2017G using XDA-Developers Legacy app
Does anyone know weather widget work or NO on b04 Australian update??? Thanks
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
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.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse