Did Anyone happen to save this OTA file? I've been saving all of them, but I happened to not save this last one, and now the server is gone. It's literally the only OTA file I don't have in my repository.
Or, maybe it's a geolock for US access.
The original link is: https://dl6.ztems.com/zxmdmp/downlo.../P996A01V1.1.0B32_to_P996A01V1.1.0B35_FOTA.up
Saldly I've only downloaded the files for the A2017G. Have you tried viewing the original html code on the page?
Victor13f said:
Saldly I've only downloaded the files for the A2017G. Have you tried viewing the original html code on the page?
Click to expand...
Click to collapse
Well, the OTA wasn't ever posted anywhere by ZTE. in the top post I have the actual link to the file -- I've captured and dl'ed all the OTA files for my MEGA repo. However for this last one, I saved the log but forgot to actually download the file. :crying:
Does anyone know where the A2017U goes to get OTA updates?
I know it's a long shot, but perhaps the address could be accessed through a browser, or maybe the Wayback Machine has a version with B35 on it.
I'm in a situation where I went back to B19 to get things straight for transitioning from a iPhone 6 to the Axon 7 to see if I could get the Verizon connection working. I got it up to B32 before I saw that B35 isn't available.
I was hoping that my problem was that I was trying to transition from a Galaxy S4 that didn't have VoLTE.
pauldow said:
Does anyone know where the A2017U goes to get OTA updates?
I know it's a long shot, but perhaps the address could be accessed through a browser, or maybe the Wayback Machine has a version with B35 on it.
I'm in a situation where I went back to B19 to get things straight for transitioning from a iPhone 6 to the Axon 7 to see if I could get the Verizon connection working. I got it up to B32 before I saw that B35 isn't available.
I was hoping that my problem was that I was trying to transition from a Galaxy S4 that didn't have VoLTE.
Click to expand...
Click to collapse
In the link in my signature, I have every OTA file the A2017U. Except as I said, I saved the update scripts to get the actual link, but I neglected to finally save the file. Unless someone saved it somewhere, it seems lost for good, and anyone using the EDL packages will max out stock at B32.
So I have a completely unmodified U model that I have taken all the way to B35 via OTA. Is there anything I might be able to do to help? I think the OTA's are generally stored in the /cache but I don't think I could access that partition without unlocking/rooting which would of course wipe everything.
So I found an old thread that said the OTA's are actually stored in /data. Still doesn't help as I cannot find a way to root without bootloader unlocking and wiping the device. If anyone has any suggestions let me know and I can try to pull/copy my /data partition and see if the OTA is still there.
Related
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
DrakenFX said:
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
Click to expand...
Click to collapse
Which is the patch date? G B09 has the December 1 patch, just wanted to know which one fixes this stuff
Can someone provide a B35 update zip? It's no issue for me to connect to Wi-Fi to install it, but I like to keep offline cached copies of files for recovery purposes, so that I can update even without Internet.
Thanks!
Edit: I have A2017U.
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Predatorhaze said:
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Click to expand...
Click to collapse
As soon as you make one?
Pretty sure it's available now. Let us know how the battery life is.
I know I asked before, but if someone can post a direct URL link to the B35 update file (whether it be a zip or something else) then it would be much appreciated. I know @DrakenFX released a system and bootstack zip, but I would rather use official files. I can't save an offline copy of the file since I'm not currently rooted, I suspect it is stored in the /cache partition. The file size is close to 700MB. I just want a copy for offline use. Maybe someone with root can capture a copy of the file after it has downloaded, but before the phone reboots to apply it. Or maybe the URL can be sniffed with WireShark or whatever. A B35 full OTA zip is better, but ZTE hasn't posted an SD card update download on the zteusa.com website yet.
Thanks!
I was able to grab the B35 update zip without rooting. I let the updater download the file, then quickly powered off the phone before it had a chance to reboot and install. Then I booted into EDL mode, and used @tennear's Axon7Tool to write TWRP. From TWRP I went to /data/data/com.zte.zdm/files, and grabbed a file called fota_update.zip. Then I reflashed the stock recovery with Axon7Tool, and installed the zip. All went fine. I suspect you can grab any OTA zip this way. Maybe I'll upload a copy of the file later.
If there's any interest in a B35 SL!M➀ aroma-version let me know
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
raystef66 said:
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
Click to expand...
Click to collapse
Yes. I downloaded those 'init' files way back last Spring & found them more effective (at least impression-wise) than the AKT stuff. His "Conservative" mod helps w/ battery w/o a noticeable performance hit.
Early on I found the A7 was not happy when some apps were removed & replaced, but functioned OK if they were kept frozen & then replaced. Fortunately there is enough storage & memory that inefficiency does not (so far) cause issues. Sort of like the legacy SubStratum which could (sort of) work as long as system apps were excluded.
I look forward to your "hobby". Thanks
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
redhou said:
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
Click to expand...
Click to collapse
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
davisml said:
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
Click to expand...
Click to collapse
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
amphi66 said:
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
Click to expand...
Click to collapse
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
redhou said:
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
Click to expand...
Click to collapse
It will download, but the install will simply fail as it checks the system files, but certainly you are free to do as you wish. Good Luck!
raystef66 said:
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
Click to expand...
Click to collapse
Uploading A2017(U)(N-B35)_AROMA_SL!M¹_DF!NR now Preparing a seperate thread on ROM section. Keeping you updated when ready :good:
EDIT : DONE ! LINK
hi, i am installing the new OTA update but it when my restarts TWRP asks for password to mount and doesn't allow me to install this new OTA update. I entered my phone password which said it decrypted the pkg but then it only opens the TWRP GUI. I tried to install the zip manually but it said it failed.
How can I let the phone install it without TWRP interfering?
Thanks a lot.
lachdanan said:
How can I let the phone install it without TWRP interfering?
Click to expand...
Click to collapse
You can't. Use stock recovery if you insist on OTA, or use DrakenFx's zips to flash from TWRP. The latter is much more convenient.
Well here we are once again. Another ota update and was wondering if anyone has downloaded and packaged this update for our rooted / twrp phones?
The new ota update number and date:
BND-L34 8.0.0.332(C567)FULL
06/12/2018
madgoogler said:
Well here we are once again. Another ota update and was wondering if anyone has downloaded and packaged this update for our rooted / twrp phones?
The new ota update number and date:
BND-L34 8.0.0.332(C567)FULL
06/12/2018
Click to expand...
Click to collapse
Firmware finder shows Bond-L34CC567CUSTC567D1B332 (8.0.0.332) , and in file list it list "Bond-L34C 8.0.0.332(C567CUSTC567D1)" but in the filelist.xml it shows "BND-L34-hw-usa" . I'm unsure if its the same device but BOND-L34 doesnt seem to exist other than on fccid.io .
hicloud links
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/update.zip
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/public/update_data_full_public.zip
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/BND-L34_hw_usa/update_full_BND-L34_hw_usa.zip
I'm downloading them now to see if its for the mate se, i can check against some of the partitions on my phone, i cant get the update off my phone because i messed up some of my partitions. Im alsu unsure how/which of these would be used to restore the phone to stock. I had seen some stuff on putting the files in a folder named dload, but my prior attempts to do that failed, the files i was using were for "BND-L34CC567B330 (8.0.0.330)" and im guessing it was failing because im on 8.0.0.332.
the file component_version.txt in VERSIONS.img lists "Version-BND-L34-000000 8.0.0.1(O.18051701)" , so it seems like its the correct file.
in case anyone stumbles on this trying to fix their phone i would avoid flashing the whole thing until there's better verification that its correct.
if you need a specific image download and extract the three files in my prior post and use "HuaweiUpdateExtractor" (uncheck verify header) to extract them from the UPDATE.APP
Let me know if any progress has been made on whether this firmware is correct and AOK.
THX
madgoogler said:
Let me know if any progress has been made on whether this firmware is correct and AOK.
THX
Click to expand...
Click to collapse
I flashed vendor, system and ramdisk from this then flash phh-treble and all seems well. the only issues i see seem to be from the treble rom. There is also a downgrade rom listed as "Bond-L34C567B130" in firmware finder, its description says "This HOTA will downgrade your system to N version."
files
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2769/g1647/v139837/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L34_hw_usa/update_full_BND-L34_hw_usa.zip
Putting it in simplest terms possible. What 3xactly is the treble rom and what does it do? I hear a bunch of stuff but it gets a bit overwhelming to sift through all the incoherent posts that have nothing to do with the thread itself. lol.l
madgoogler said:
Putting it in simplest terms possible. What 3xactly is the treble rom and what does it do? I hear a bunch of stuff but it gets a bit overwhelming to sift through all the incoherent posts that have nothing to do with the thread itself. lol.l
Click to expand...
Click to collapse
project treble is available on Oreo compatible devices, it splits the system partition into separate system(operating system) and vendor(drivers) partitions, it also separates the kernel to its own partition and splits or renames recovery. That means that a rom developer can make a single image that works with any phone. unfortunately its not quite so simple since manufacturers do weird stuff that breaks things. huawei for example generates some files in the data partition that are necessary for everything to work.
That explains why twrp and flashing changed in 8.0
My phone was broken through rigorous device testing at work. Took ZTE a very long time but they finally delivered my repaired phone in November. Been extremely busy and transfered my life to a replacement Moto G5 but now I want to go back to my trusted ZTE...
...except I can't update my device. What they sent back to me was a device with the last installed update from Jan 2017. Now that's OK if I can just go and update it, but I can't. Servers are dead, and I don't have the time to go and start rooting/unlocking/installing Roms. And I think because of how old the last update is, apps like Android Auto aren't working properly with my car.
Would be nice if the US gov't played nice and just allowed ZTE to at least keep their servers up and running, but I have no control of that. Right now I'm at the point where I'm deciding on buying a Oneplus 6 if I can't get this phone working properly. Android Auto is a #1 priority for me.
Is there a way to grab update Zips somewhere online and easily update from the updater tool? I did this before when I got my device to Android 7.1.1 ways back (I purchased my ZTE almost 2 years now).
Which one do you have the U, G and the Chinese version?
Really ? did you even searched ?
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Sn8K said:
Really ? did you even searched ?
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Well, he did say
mozillameister said:
I don't have the time to go and start rooting/unlocking/installing Roms.
Click to expand...
Click to collapse
If he has the G model then there's this thread.
Via MiFlash
EwertonR19 said:
Via MiFlash
Click to expand...
Click to collapse
Not without the B35 stock firmware which no one seems to have as ZTE never put it up on the support page before everything went down.
I still have a fully stock phone for now and I have been trying to find a way to root without wiping my device so I can try to pull the OTA from /data, but so far I haven't had any luck.
KH_Lionheart said:
Not without the B35 stock firmware which no one seems to have as ZTE never put it up on the support page before everything went down.
I still have a fully stock phone for now and I have been trying to find a way to root without wiping my device so I can try to pull the OTA from /data, but so far I haven't had any luck.
Click to expand...
Click to collapse
FYI, just EDL the B35 with @djkuz B35 stock rom.
Give the guy some proper credits
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
As i got my A2017G two day before, there was the v B02 installed on it! (from apr. 2017?)
Unfortunately, i can’t get a newer OTA update because all ZTE servers seems to be offline.
But I have found several v A2017G/B10 zip files in the internet. I have downloaded two of them and compared. Result=Equal
After putting some of the files onto my sd, the update was found and installed successful! Now i am on B10.
A little bit of work, but a good result!
I just picked up a refurbished Tab4 8 (TB-8504F). I get an error when attempting the system update. Says failed to parse build number. See attached pics.
Can't figure out what's wrong. The tablet doesn't seem rooted. I can't find any evidence that these build numbers are non-factory. Anyone have any ideas?
jonnythan said:
I just picked up a refurbished Tab4 8 (TB-8504F). I get an error when attempting the system update. Says failed to parse build number. See attached pics.
Can't figure out what's wrong. The tablet doesn't seem rooted. I can't find any evidence that these build numbers are non-factory. Anyone have any ideas?
Click to expand...
Click to collapse
It's not rooted now, but was prior to your purchase of the device. The system partition has been modified, thus you cannot take an OTA.
There is a solution that I've used in the discussion thread regarding TWRP and root for these devices. In short, you need to download the stock firmware from lenovo-forums.ru as well as a copy of MiFlash from the TWRP thread, place the device into emergency download mode, and then use MiFlash to install the firmware. I've done it to my 8504F and was able to take an OTA upon rebooting after install.
Thanks. I mucked it up good by trying to manually flash the system and boot images from an older version of Android, bricking the device entirely. Managed to figure out QFIL enough to flash the older firmware from the Russian site, then upgrade normally.
Thanks!
You're lucky. When I encountered the OTA issue I accidentally flashed another device's firmware in TWRP. I bricked it so badly that EDL mode didn't help; the tablet fortunately was still under warranty. I sent it to Lenovo for service and Lenovo took their sweet time fixing it: 45 days to get the tablet back.