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
Related
I'm using nightly 123. The program seems to work just like it's suppose to, no errors, but after I run the program I use Show me my IMEI and it still doesn't show that I have an IMEI no. I'm using ADB wireless to update the EMEI. The program runs and and reboots my nook afterwards.
I don't know what else to do, and i can't post in the developer's thread yet so I thought I'd ask here. Hope someone can tell me what I'm doing wrong. Thx
Well I still can't post in the right forum, does anyone have any ideas what I'm doing wrong? Thx
Sorry... didn't see this thread....
If you are using in-place... as it seem you are by the reboot... check to see if you have a /framework/framework.jar.bak present... you might also look at /rom and see if a file called imei is created there...
I'd say you have to have the framework.jar.bak file or you'd get the error that it had issues updating your device.
Since you are on CM7... go to phone app and dial *#06# and see what it tells you for IMEI.
Lastly... you can update the rom zip file... and flash the rom "-IMEI.zip" file.
Sorry... but this is the first report I've seen of it not working... and it may be the app you're using to show it... thus try the phone app thing.
Did not workforce me either. Using the dialer to check returns no number. I do have a framework.jar.Bak though. I'd really like this to work so that I could use the xda app with out it fcing. What file were u saying to flash DD? Thanks.
If you are using in-place... as it seem you are by the reboot... check to see if you have a /framework/framework.jar.bak present... you might also look at /rom and see if a file called imei is created there...
I'd say you have to have the framework.jar.bak file or you'd get the error that it had issues updating your device.
Since you are on CM7... go to phone app and dial *#06# and see what it tells you for IMEI.
Lastly... you can update the rom zip file... and flash the rom "-IMEI.zip" file.
Sorry... but this is the first report I've seen of it not working... and it may be the app you're using to show it... thus try the phone app thing.
__________________
Always remember...
1. I have the framework.jar.bak file
2. In the /Rom folder there isn't an imei file, but there is one in the /rom/devconf folder
3. When I dial the command in the phone app it comes back with a box that says imei then an OK button. There is no number if thats what you wanted to know.
4. I'm not exactly sure on the steps to update the rom zip file.
Thanks alot for answering my post.
OK... and I did mean the bak file should be in /rom/devconf... sorry bout that... was responding from work and in a hurry....
To update the rom... just tell it no to in place... and then yes to updating a ROM zip file...
After it finishes patching the zip file... flash the ROM "-IMEI.zip" and any OC kernel you're using.
I'll look into what's going on... it could be the newer rom update is missing symlinks and busybox is not working correctly... researching the cause.
DizzyDen said:
OK... and I did mean the bak file should be in /rom/devconf... sorry bout that... was responding from work and in a hurry....
To update the rom... just tell it no to in place... and then yes to updating a ROM zip file...
After it finishes patching the zip file... flash the ROM "-IMEI.zip" and any OC kernel you're using.
I'll look into what's going on... it could be the newer rom update is missing symlinks and busybox is not working correctly... researching the cause.
Click to expand...
Click to collapse
Will try it After work. I'm assuming it prompts u for the path to a zipped rom, and then creates one with imei added in the name. Then flash like n e other rom. Thanx.
Thx for the quick reply's. I updated the rom.zip file like you said. I think I'll wait to try it to see if you can figure out how to get the in-place update to work. I just updated the recent nightly and hate to start over again . If I have to I will though. Thx alot for your help.
newellj79 said:
Will try it After work. I'm assuming it prompts u for the path to a zipped rom, and then creates one with imei added in the name. Then flash like n e other rom. Thanx.
Click to expand...
Click to collapse
If it finds zip files in current directory... it will attempt to locate the newest (by filename) and prompts you if it is the correct one... if you click no... it opens a windows open dialog to browse to the zip file you want to update... the "-IEMI.zip will be placed in the same folder as the rom.zip.
lemdaddy said:
Thx for the quick reply's. I updated the rom.zip file like you said. I think I'll wait to try it to see if you can figure out how to get the in-place update to work. I just updated the recent nightly and hate to start over again . If I have to I will though. Thx alot for your help.
Click to expand...
Click to collapse
If you flash the update... you don't have to start over... it retains your data... just like any other update. You just have to make sure you install the OC kernel also... it is the same process as updating any nightly... the only difference is you run the IMEI generator on it prior to flashing it so you will have the patched framework.jar as soon as you flash it.
I just flashed the file your program created and I still have no imei no. when running the phone app or with the program Show me my Imie. I don't know if I'm doing something wrong or not, but everything seemed to work as it was suppose to except getting an Imei no. Thx.
lemdaddy said:
I just flashed the file your program created and I still have no imei no. when running the phone app or with the program Show me my Imie. I don't know if I'm doing something wrong or not, but everything seemed to work as it was suppose to except getting an Imei no. Thx.
Click to expand...
Click to collapse
hmmmm.... trying to see what the issue could be.... if you flashed the "-IEMI.zip" file the patched framework.jar file should be the one it installed... so it SHOULD work just fine.
Try running fix permissions and try in-place again... it could be that your permissions are preventing /system/framework/framework.jar being overwritten.
You can open the "-IMEI.zip" file in a zip file manager (winzip, 7zip, winrar) and see if the /system/framework/framework.jar file has a different date than the rest of the files.
In the rom zip file your program made the date of the framework jar was modified to today's date. I ran rom manager and fix permissions and rebooted then ran in place from your program. I still don't get a number with either phone or show me my emei. I also don't get any errors while running your program.
lemdaddy said:
In the rom zip file your program made the date of the framework jar was modified to today's date. I ran rom manager and fix permissions and rebooted then ran in place from your program, all appears to be good, no errors.
I still don't get a number with either phone or show me my emei.
Click to expand...
Click to collapse
This is just crazy... if the zip had the framework.jar file with today's date... it should be the one installed.. and it should have the imei in it...
Do me a favor... extract framework.jar from your zip file... email it to me at [email protected] so I can look into it and ensure the edit to the file went as planned.... or wait and I'll give the option to not delete the TelephonyManager.smali so you can look at the file and ensure the edit took place.
try this...
adb shell ls -l /system/framework
See what the date and time on that file is.
Ok i sent the framework.jar file, thx alot for your help.
lemdaddy said:
Ok i sent the framework.jar file, thx alot for your help.
Click to expand...
Click to collapse
NP... I got the file... for some reason the patch seems to not be in the file... this is the framework.jar file from the -IMEI.zip file... right?
When you run the program... does it give you a pop up with your S/N, MAC and IMEI ?
yes it is from the updated emei.zip rom file. Yes it does show the numbers when i run your program after it pulls the file from my nook
lemdaddy said:
yes it is from the updated emei.zip rom file. Yes it does show the numbers when i run your program after it pulls the file from my nook
Click to expand...
Click to collapse
OK... check your pm... also if you will adb pull /rom/imei and email that... I will create a framework.jar for you until I can track down what is going on.
Phone call would probably be easiest to track down the issue... Gave you number in pm... or you can pm me your's if you'd rather me make the call.
I got it working by using the flash method. I'm finally able to use tthe xda app!
Sent from my NookColor using XDA App
I wish mine would have. Dizzy is looking into why mine still won't work. I'm glad yours is working. I appreciate all your help Dizzy
Lemdaddy... if we get a chance to make contact tomorrow... sat... I want to try a couple of things so we figure out why the smali isn't working on your computer...
Keep getting the following message for every ROM I attempt to install:
-- Install /sdcard/download...
Finding update package...
Opening update package...
E: Can't open /tmp/sideload/package.zip
(bad)
Please anyone, whats my resolution to this matter. Thanks in advance!
HackDPlanet said:
Keep getting the following message for every ROM I attempt to install:
-- Install /sdcard/download...
Finding update package...
Opening update package...
E: Can't open /tmp/sideload/package.zip
(bad)
Please anyone, whats my resolution to this matter. Thanks in advance!
Click to expand...
Click to collapse
What version of TWRP are you on?
My only other thought would be that the roms aren't downloading correctly for some reason or another, check the size of the file downloaded to the actual size its supposed to be.
Im using the latest version of TWRP. I flashed the following .img:
recovery-twrp-shooter-1.0.2.img
HackDPlanet said:
Im using the latest version of TWRP. I flashed the following .img:
recovery-twrp-shooter-1.0.2.img
Click to expand...
Click to collapse
My guess is a bad download then, possibly you aren't getting the whole file when you download it?
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
HackDPlanet said:
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
Click to expand...
Click to collapse
With the size of the roms for the 3D I would highly recommend always just doing it on your computer. I almost guarantee that is your issue, not 100% sure but not just a shot in the dark.
HackDPlanet said:
I'm redownloading see if thats the fix. I initially downloaded directly to phone. I am downloading to computer now and will drop into SD card and see what happens from there. Cross your fingers!!!!!
Click to expand...
Click to collapse
NO GO!?!?! I wiped and attempted again and nothing. SAME ERROR MESSAGE. Quick question: The background image when choosing to zip to flash, is it a box with question marks? Just wondering maybe something is wrong with my tmrp.
I dont get it and dont know what to do. Should I push the root .zip again to see what happens, if anything?
Please HELP! SOS SOS SOS SOS SOS
All XDA gurus, I call for your powers! I have read the in and outs of the EVO 3D pages and have not found one single person running into the same issue.
HackDPlanet said:
NO GO!?!?! I wiped and attempted again and nothing. SAME ERROR MESSAGE. Quick question: The background image when choosing to zip to flash, is it a box with question marks? Just wondering maybe something is wrong with my tmrp.
I dont get it and dont know what to do. Should I push the root .zip again to see what happens, if anything?
Please HELP! SOS SOS SOS SOS SOS
All XDA gurus, I call for your powers! I have read the in and outs of the EVO 3D pages and have not found one single person running into the same issue.
Click to expand...
Click to collapse
Try running the PC86IMG.zip from your bootloader instead of pushing the img file for TWRP. My only guess is that for some reason or another it is something to do with the recovery.
Could you provide me some directions really quick, detailed? Just want to make sure i get this right. Ya dig lol. Man I am so discouraged right now. Im missing my Hero lol. Ouch no, i didnt just say that. nevermind
I have the following directions:
Install as a Flashable Zip? [RECOMMENDED]
1.Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
2.Place in the root of the sdcard
3.Power off phone (make sure you turn off hot boot or pull the battery when it's off)
4.Power on the phone holding power and volume down
5.Follow the prompts to flash it
6.Delete .zip (PG86IMG.zip) after booting
7.Enjoy
I have read over and over that you will be "prompted" to flash as update or whatever, but I never get this option. I basically just load into hboot. Am I missing a step here or what?
HackDPlanet said:
Could you provide me some directions really quick, detailed? Just want to make sure i get this right. Ya dig lol. Man I am so discouraged right now. Im missing my Hero lol. Ouch no, i didnt just say that. nevermind
Click to expand...
Click to collapse
Alright, I am just gonna copy the how to from the TeamWin thread but this should be alot easier than doing the push of the .img file.
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG86IMG.zip) after booting
Enjoy
Click to expand...
Click to collapse
Here is the zip: http://api.viglink.com/api/click?fo...er-1.0.2.zip&jsonp=vglnk_jsonp_13125241678211
Just read what you posted before I posted that. If you are not being prompted for an update then the file isn't renamed properly. You don't need to add .zip when you rename it because it is already a zip file.
Ok, I made sure the file name was correct. When loading, it slowed up on that .zip but never prompted me to do anything?
Oh and still getting the same message when trying to install ROM. It was different this time around with the slowing up when booting like it did something but it never prompted me to do any action. I really dont know man, I am clueless.
HackDPlanet said:
Oh and still getting the same message when trying to install ROM. It was different this time around with the slowing up when booting like it did something but it never prompted me to do any action. I really dont know man, I am clueless.
Click to expand...
Click to collapse
Hmmm so you did update the recovery or still not able to?
Second guessing myself now, root of the SDcard is just anywhere in the SDcard not within a folder, correct? Just want to make sure, trying to over all my bases. Jeeeze, I did not have this type of trouble with my Hero. I am feeling like a Noob but this is challenging me.
It did not prompt me to update the recovery. It simply slowed down during the .zip verification process when it was booting and than it kept going. Nothing more, no prompt for my action to update.
HackDPlanet said:
It did not prompt me to update the recovery. It simply slowed down during the .zip verification process when it was booting and than it kept going. Nothing more, no prompt for my action to update.
Click to expand...
Click to collapse
The file just needs to be placed on the SD plain and simple no folders etc.
I still think this is a naming issue because it should prompt you to press the volume up to update. Rename the file to just PC86IMG and see if that works.
Oh and the renaming part is case sensitive.
Ok, I read what it said "wrong zipped image" when the process slowwed down during the boot up
And I named it only "PC86IMG". and than when i look at the file through AstoZip than the it shows as "PC86IMG.zip" The ending (.zip) automatically is added.
Hey guys,
been a lurker for long...
anyway, I downloaded VERTREMA ROM cz I love the ICS theme... so I rooted my SGS2 using CF-ROOT guide here
Checked it using Root Check Basic tool, and it says i have root access... so my sgs2 is rooted
so.... i tried to install this ROM using CWM app... i tried using update, chose the file, rebooted but didnt work... it says something E: can't open .....zip
What did I do wrong?
BTW, i placed the ROM inside /download/ folder (not in external SD)
Thanks,
t_mo_t said:
Hey guys,
been a lurker for long...
anyway, I downloaded VERTREMA ROM cz I love the ICS theme... so I rooted my SGS2 using CF-ROOT guide here
Checked it using Root Check Basic tool, and it says i have root access... so my sgs2 is rooted
so.... i tried to install this ROM using CWM app... i tried using update, chose the file, rebooted but didnt work... it says something E: can't open .....zip
What did I do wrong?
BTW, i placed the ROM inside /download/ folder (not in external SD)
Thanks,
Click to expand...
Click to collapse
Did you download the entire package ? it may happen if the download got interrupted mid way ......... in that case you'd have a zip file of a lesser size which can't be opened ....... try extracting the zip if you get an error you've got to redownload the package....
also ensure that the package is not read only (just incase)
digi_fort said:
Did you download the entire package ? it may happen if the download got interrupted mid way ......... in that case you'd have a zip file of a lesser size which can't be opened ....... try extracting the zip if you get an error you've got to redownload the package....
also ensure that the package is not read only (just incase)
Click to expand...
Click to collapse
ok... package is not read-only... it's -rw... so it's good....
how do i check the md5 checksum in multiupload?
i m downloading the latest version now... hope it wont get disconnected...
Find an app like MD5Summer (Windoze) to check the MD5 sum once you've downloaded the package.
Also, you can use pretty much any archive program (7Zip, IZArc, WinRar) to test the archive once you've finished downloading it.
If it comes up with fail for *any* file, don't flash that package/download it again. You might have to try downloading it from a different PC/internet connection like I did a while back when I was having probs downloading roms from home without them being corrupt.
t_mo_t said:
ok... package is not read-only... it's -rw... so it's good....
how do i check the md5 checksum in multiupload?
i m downloading the latest version now... hope it wont get disconnected...
Click to expand...
Click to collapse
MistahBungle said:
Find an app like MD5Summer (Windoze) to check the MD5 sum once you've downloaded the package.
Also, you can use pretty much any archive program (7Zip, IZArc, WinRar) to test the archive once you've finished downloading it.
If it comes up with fail for *any* file, don't flash that package/download it again. You might have to try downloading it from a different PC/internet connection like I did a while back when I was having probs downloading roms from home without them being corrupt.
Click to expand...
Click to collapse
no no... i mean before i downloaded the package.... is there a md5 checker tool so that i can compare wit the one that i downloaded?
ok i will try to download using another pc..
You have to finish downloading the rom/package before you can check the MD5 sum as there's nothing to check if you haven't downloaded it (obviously)
t_mo_t said:
no no... i mean before i downloaded the package.... is there a md5 checker tool so that i can compare wit the one that i downloaded?
ok i will try to download using another pc..
Click to expand...
Click to collapse
MistahBungle said:
You have to finish downloading the rom/package before you can check the MD5 sum as there's nothing to check if you haven't downloaded it (obviously)
Click to expand...
Click to collapse
yes i know... what i meant was,... is there like a website that tells me the md5 cs in multiupload, so i can compare to the one that i had just finished downloading...
anyway.... thanks to the above poster.. i deleted it from my phone and then transferred the file again... and now it works.... weird,... i transferred first to my microsd, then to phone... i guess that method doesnt work... better to transfer it directly to phone...
thanks y'all!!! been a great help... very nice community here
The MD5 checksum is usually listed next to the link where you download the archive wherever you're downloading it from. Honestly, it's not that important. The most important thing is you get the entire file. And if you "test" the archive in 7Zip/IZArc/WinRar & it comes up all files OK you should be fine.
I've never had a problem flashing a rom/kernel where the test in IZArc has indicated all files contained within are OK/the archive isn't corrupt.
t_mo_t said:
yes i know... what i meant was,... is there like a website that tells me the md5 cs in multiupload, so i can compare to the one that i had just finished downloading...
anyway.... thanks to the above poster.. i deleted it from my phone and then transferred the file again... and now it works.... weird,... i transferred first to my microsd, then to phone... i guess that method doesnt work... better to transfer it directly to phone...
thanks y'all!!! been a great help... very nice community here
Click to expand...
Click to collapse
MistahBungle said:
The MD5 checksum is usually listed next to the link where you download the archive wherever you're downloading it from. Honestly, it's not that important. The most important thing is you get the entire file. And if you "test" the archive in 7Zip/IZArc/WinRar & it comes up all files OK you should be fine.
I've never had a problem flashing a rom/kernel where the test in IZArc has indicated all files contained within are OK/the archive isn't corrupt.
Click to expand...
Click to collapse
ic.... oh well.. thanks anyway .... ohh 1 last question.. so if i want to revert to the stock rom, i just do the same thing but with the stock rom i can download from samfirmware?
Why not download the stock rom from here ? I wouldn't know about files from Samfirmware as I've never downloaded anything from there.
If you want to go back to stock, download the rom from Intratech's thread, flash it in Odin, done. Again, test the archive integrity in IZarc or similar to make sure it's OK (given you seemed to have had some problems downloading an archive that wasn't whole or corrupted).
t_mo_t said:
ic.... oh well.. thanks anyway .... ohh 1 last question.. so if i want to revert to the stock rom, i just do the same thing but with the stock rom i can download from samfirmware?
Click to expand...
Click to collapse
kewl! thanks!!!
MistahBungle said:
Why not download the stock rom from here ? I wouldn't know about files from Samfirmware as I've never downloaded anything from there.
If you want to go back to stock, download the rom from Intratech's thread, flash it in Odin, done. Again, test the archive integrity in IZarc or similar to make sure it's OK (given you seemed to have had some problems downloading an archive that wasn't whole or corrupted).
Click to expand...
Click to collapse
Or you could use Mobile Odin and keep your root intact even when stock
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..
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