Database Users

New July images posted

Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O

dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.

I went with MOB30M last time and it worked fine, so I'm going with MOB30O.

@dahawthorne added the links on the first post for you..

Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.

Sir , is there any difference between MMB30K and MOB30O versions?

marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that

Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111

What was the difference between the last 2 images? That was released without explanation as well!

I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.

Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.

ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.

The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.

ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.

Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.

dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.

dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.

before i download the entire package can anyone tell me if there is a new modem in july update?

H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app

adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.

Honor 6 PLUS - NEW UPDATE!!

Hello everyone, today for the Honor 6 Plus is a new OTA is the C432B571 some people have jumped him via OTA and others not so you can download the update I put and upgrade to the latest version which is the PE-TL10C432B571.
Instructions: download, unzip and copy the folder dload update.app in SD.
LINK http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v55895/f1/full/update.zip

Awesome..!! This is just like the B190 OTA update for Honor 7.
So they are updating the Lollipop version for their devices too, this is the first approach like this I have seen.

This is an update improving mm is passed from the B560, B571 this new update

Does this work on honor 6 too?

Dynos said:
Does this work on honor 6 too?
Click to expand...
Click to collapse
No, it's for the plus

Damn, any word on when h6 gets this?

I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance

fefferico said:
I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance
Click to expand...
Click to collapse
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.

zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Thanks a lot mate!
With the link you provided I was able to successfully upgrade my H6+
Anyway I'm still official, no root, no unlocked bootloader.... strange considering that I lost my MotoG1 warranty after a week
Thanks again

I have downloaded the zip (didn't extract it) and i have created /dload file in internal memory and put that zip inside it, then i have open updater and select that zip and my 6+ enter in installing mode, but it stuck at 99% and it doesn't continue, someone knows whats wrong with it ?

You should have extracted it.
Extract the zip file unitl you have an update.app and put this into your dload folder. Then try updating again with force update method. If this doesn´t work

zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance

ofczi said:
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance
Click to expand...
Click to collapse
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.

May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!

Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge

assemaskar said:
Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge
Click to expand...
Click to collapse
No, only it works in PE-TL10C432

zinko_pt said:
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.
Click to expand...
Click to collapse
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.

ofczi said:
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.
Click to expand...
Click to collapse
From my experience, encrypted phones don´t go along with automatic turn on/off and updates.

oh.joan said:
May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!
Click to expand...
Click to collapse
If you're already on MM, it's just bug fixes and optimizations

Hi
my device run on PE-TL10C185B510, does this update work and what new features it will add?

[Updata]WW-4.21.40.223(andriod M)

ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip

Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks

fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.

Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.

VoLte support?? in this new update....

I felt like this was happening today! came in and here it is. Updating right now.
Thanks

any update for this update of asus zenfone 2

optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.

i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.

Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same

All sensors working with this version in my brazilian zenfone 2 z00a.

Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.

I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit

audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.

audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642

timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks

crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough

Failed to Update (OTA, SD-Card ant ADB)

Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno

Recovery stock and SD card seem to be the most reliable method.
Did you check the md5 of the zip? Also update.zip to put on root of the SD card should be the final zip, not the zip that contains another zip.
Also when booting in Android, I assume your SD is recognized, isn't it?
If so, instead of going to recovery then update from SD card, you can try to update from inside Android, from Phone settings, then Update item.
The phone should indicate the current version and the version to be updated to. Then follow the phone indication to update.

Nope, i dont checked MD5. But shouldn't be the problen. I tried many different update files, always same error.
Yes, after booting the SD card is connected and i could use it. Just the recovery mode cant mount the card.
Also the updater recognize my update. But he just boot in the recovery mode and try to update -> Same error: "couldn't mount /sdcard"
Edit 1:
But i can check the MD5 files if necessary. I just need the "correct" MD5 value to compare.

Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.

t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Also, bricked means totally unusable, so no it isn't bricked lol

dnlilas said:
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
Click to expand...
Click to collapse
Its a 64 GB card Should i try a <= 32 GB card? Could be I have some lying around. Just to be sure its not a special case.
I will test it tomorrow if i found one

Choose an username... said:
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Also, bricked means totally unusable, so no it isn't bricked lol
Click to expand...
Click to collapse
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!

t4ggno said:
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
Click to expand...
Click to collapse
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.

First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.

Choose an username... said:
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
Click to expand...
Click to collapse
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I tried the package A2017G-MM-B11 and A2017G-N-B01 from the link I posted, also i tried the oficiell patch files from the axon website (B10 and Nougat)
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
I have a A2017G (that information i found on the back of my phone).
My phone overview tells me:
Modelnumber: ZTE A201G
Build-Number: ZTE A2017GV1.0.0B08
Android-Version: 6.0.1
Security-Patch: 1. December 2016
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?

Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.

karlkarloff said:
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
Click to expand...
Click to collapse
I tried it, but doesn't work :/
The update stops at 33% with the error message "Package Mismatch".

t4ggno said:
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Click to expand...
Click to collapse
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10

Choose an username... said:
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Click to expand...
Click to collapse
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.

t4ggno said:
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
Click to expand...
Click to collapse
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip

Choose an username... said:
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Click to expand...
Click to collapse
Thanks! That worked very well. I did a factory reset and moved the update file directly to the root of my internal storage. After that the updater detected my update and I could install the Patch B011. After that i was able to update to Nougat trough OTA. No errors, every worked fine.

otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
it seems that I got this one with modified rom. is there anyway to get it back to the official chinese rom?

Fire TV 3 (needle/stark): TWRP

Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.

Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.

Confirmed, it works on the cube (stark) as well...

That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.

Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.

Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.

Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.

2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?

Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.

2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...

Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.

How may I get the "su". It said, I don't have permision.

eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.

2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?

eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.

This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.

eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work

Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.

moving it to the right place.

anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?