Develop Bugs

Defy XT for RW Update Image

I have dumped the Motorola Defy XT update recently released by Republic Wireless for those who wish to work to make a rom for the device. I have no idea of the format, I know it's not a ZIP.
Link is attached below by nogoodusername, thanks, since I am a new member and cannot post links.

-Link removed-
Sent from my MB526 using xda premium

nogoodusername said:
PM me the link
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Sent PM, thanks.

GeckoPower said:
Sent PM, thanks.
Click to expand...
Click to collapse
Link added

Update looks like ota zip package, because when i added .zip to file extenction & opened it with winrar, I see meta-inf folder & in right size is writen ,,signed by Moto-SignApk. When i oppened renamed file i get error that zip is corruped, so i don't how we'll able to use that file without moto-signing keys..

turffe said:
Update looks like ota zip package, because when i added .zip to file extenction & opened it with winrar, I see meta-inf folder & in right size is writen ,,signed by Moto-SignApk. When i oppened renamed file i get error that zip is corruped, so i don't how we'll able to use that file without moto-signing keys..
Click to expand...
Click to collapse
Archive: defyxt_rw_update_1_65K_1027.zip
signed by Moto-SignApk
warning [defyxt_rw_update_1_65K_1027.zip]: 166614 extra bytes at beginning or within zipfile
(attempting to process anyway)
error [defyxt_rw_update_1_65K_1027.zip]: start of central directory not found;
zipfile corrupt.
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
The way I got the ZIP was by connecting my phone to my computer's custom wifi network and captured all packets that came from the phone and to the phone through my computer using wireshark. I then found the end of the file download where wireshark has reassembled the "TCP Segments" and exported that to a file deleting the HTTP header which ends at \r\n\r\n. I did not delete the NULL byte after the new line. Looking at what segments were assembled individually, it is not including the TCP header information, it's just including the payload.
All of that being said... I do not know rather or not wireshark assembled it correctly. I am willing to provide my pcap file after I obscure things identifying my device.

If you got an ota then it is stored in /cache and you can just copy it.
It will stay as long as /cache isn't wiped
Sent from my MB526 using xda premium

nogoodusername said:
If you got an ota then it is stored in /cache and you can just copy it.
It will stay as long as /cache isn't wiped
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I'll get it from my sister's phone and compare with the one I extracted.

I also plan on adding the original /System/ and the new update /System/ untouched by root.

Here is the update. https://mega.co.nz/#!ecEhVRQA!E-uvfkaMvjV67vMO1lKMKywqV3ohMPiuNWTWJ8WHGi0
Here is the update capture file https://mega.co.nz/#!eVlxDQJY!VGBjl2BiGAIiVp3eVmV85T6VayAj0xD9F9kjC0kpbOA
Here is the original system folder. https://mega.co.nz/#!SFElnaYS!ZehMhQ8lDaBt037xoBlxPT70ozoJ9_9rXd0Fo9_MtOI
As soon as my sister gets home, I'm going to update her phone... Get the update zip from her phone's cache as mentioned above, and then dump the system folder after the update.

GeckoPower said:
As soon as my sister gets home, I'm going to update her phone... Get the update zip from her phone's cache as mentioned above, and then dump the system folder after the update.
Click to expand...
Click to collapse
This is how you should do it
Download the update
Decline the update/reboot
Goto /cache and copy the zip to sd or PC
Then do the update.
Sent from my MB526 using xda premium

GeckoPower said:
Here is the update. https://mega.co.nz/#!ecEhVRQA!E-uvfkaMvjV67vMO1lKMKywqV3ohMPiuNWTWJ8WHGi0
Here is the update capture file https://mega.co.nz/#!eVlxDQJY!VGBjl2BiGAIiVp3eVmV85T6VayAj0xD9F9kjC0kpbOA
Here is the original system folder. https://mega.co.nz/#!SFElnaYS!ZehMhQ8lDaBt037xoBlxPT70ozoJ9_9rXd0Fo9_MtOI
As soon as my sister gets home, I'm going to update her phone... Get the update zip from her phone's cache as mentioned above, and then dump the system folder after the update.
Click to expand...
Click to collapse
See this is what I'm trying to do. Thanks for this btw!
Okay so im trying to rescue my phone from bootloop because of root. Im Not sure if this will work but hey im trying.
When i install this from recovery this is what i get
--Install /sdcard--
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
The update package may be not correct or corrupted!
Please reboot to OS and try again or ask for technical support.
Click to expand...
Click to collapse
Now i am a total N00B now. I have been nearly 2 years android less and i forgot everything. SOO.... I now the bootloader or what ever needs a verified, signed update package to install/flash right? wouldnt the update package already be signed by RW?

im stuck in a boot loop too.. updated rooted now bootlooping... did you save your phone??

GeckoPower said:
Here is the update. https://mega.co.nz/#!ecEhVRQA!E-uvfkaMvjV67vMO1lKMKywqV3ohMPiuNWTWJ8WHGi0
Here is the update capture file https://mega.co.nz/#!eVlxDQJY!VGBjl2BiGAIiVp3eVmV85T6VayAj0xD9F9kjC0kpbOA
Here is the original system folder. https://mega.co.nz/#!SFElnaYS!ZehMhQ8lDaBt037xoBlxPT70ozoJ9_9rXd0Fo9_MtOI
As soon as my sister gets home, I'm going to update her phone... Get the update zip from her phone's cache as mentioned above, and then dump the system folder after the update.
Click to expand...
Click to collapse
Here is the updated system folder
https://mega.co.nz/#!OIMmWRJK!DR8JNER2DrN9SM5n4UIlCzlC_dIjDIh2Vqhnu7BYe1A

4.3 OTA update fails due to modified file debuggerd

When trying to apply the OTA update from Android 4.2.2 to 4.3 to a rooted Samsung Galaxy Nexus, the process failed quickly with an assert error, something like:
assert failed: apply_patch_check("/system/bin/debuggerd", …
The cause was that the file /system/bin/debuggerd had been changed since the 4.2.2 installation. There was also a file debuggerd.backup, which was, however, equal to the file debuggerd.
I solved the problem by copying the 4.2.2 file debuggerd (attached here—unzip before use) from another Galaxy Nexus phone, which was still at stock 4.2.2, and copying that into the problem phone. To do this I used ES File Explorer in "Root Explorer" mode with /system mounted r/w.
After this operation the OTA update ran fine. (I had meanwhile downloaded it as a file and flashed it with the TWRP recovery.)
The question remains, which program had altered the debuggerd file? Since only programs with root rights could possibly do this, I have two main suspicions: ReKey and StickMount. I have not tested, but if anybody here has the same problem, please check which programs with root rights you have been running.
The attached file is from Android 4.2.2 yakju. We have an indication (see below) that the file may not be the same for takju. Could somebody please confirm or deny this?

Problem with the file
hgmichna said:
When trying to apply the OTA update from Android 4.2.2 to 4.3 to a rooted Samsung Galaxy Nexus, the process failed quickly with an assert error, something like:
assert failed: apply_patch_check("/system/bin/debuggerd", …
The cause was that the file /system/bin/debuggerd had been changed since the 4.2.2 installation. There was also a file debuggerd.backup, which was, however, equal to the file debuggerd.
I solved the problem by copying the 4.2.2 file debuggerd (attached here—unzip before use) from another Galaxy Nexus phone, which was still at stock 4.2.2, and copying that into the problem phone. To do this I used ES File Explorer in "Root Explorer" mode with /system mounted r/w.
After this operation the OTA update ran fine. (I had meanwhile downloaded it as a file and flashed it with the TWRP recovery.)
The question remains, which program had altered the debuggerd file? Since only programs with root rights could possibly do this, I have two main suspicions: ReKey and StickMount. I have not tested, but if anybody here has the same problem, please check which programs with root rights you have been running.
Click to expand...
Click to collapse
Thanks for the file.
It is not working for me though. Is it Takju?

masasin said:
Thanks for the file.
It is not working for me though. Is it Takju?
Click to expand...
Click to collapse
No, this is from a yakju phone.
Sorry, I assumed, perhaps falsely, that the debuggerd file in Android 4.2.2 is always the same.
If this problem occurs more often, perhaps somebody could upload the stock debuggerd from takju Android 4.2.2 as well.

hgmichna said:
No, this is from a yakju phone.
Sorry, I assumed, perhaps falsely, that the debuggerd file in Android 4.2.2 is always the same.
If this problem occurs more often, perhaps somebody could upload the stock debuggerd from takju Android 4.2.2 as well.
Click to expand...
Click to collapse
Mine was Takju. It seems they are incompatible. Do you know if I get sent an email automatically if a file is updated?

The stock 4.2.2 takju debuggerd image would be appreciated here, too! Thanks.

takju debuggerd
I pulled these files from the factory images "takju" (system.img)
4.2.2 (JDQ39)
takju-jdq39-debuggerd - This is for OTA - takju-JWR66V-from-JDQ39
md5: c7372f8a49253c29e7f4d691276e8564
4.3 (JWR66V)
takju-jwr66v-debuggerd - This is for OTA - takju-JWR66Y-from-JWR66V
md5: a64ce8343a8cc2a7248b1c0bbab766bf

Hello, can somebody, please, post original debuggerd file from yakju 4.3 (JWR66V) ... thank you

kubuss said:
Hello, can somebody, please, post original debuggerd file from yakju 4.3 (JWR66V) ... thank you
Click to expand...
Click to collapse
Posted above. I just removed Stickmount in the meantime. Also, I can copy and paste again!

Here it is buddy! <yakju 4.3 (JWR66Y)> version of file which will do the job of the OTA update.
I have finally found the solution to my "Error 7" after several days of thread reading and wrong assumptions. The culprit seems to be a past installation of stickmount and the usb otg helper which i use now !!

empsun said:
The culprit seems to be a past installation of stickmount and the usb otg helper which i use now !!
Click to expand...
Click to collapse
Which one is that? Is it any better than StickMount?

Stickmount didn't work for me, couldn't even mount a NTFS usb key for writing. On the contrary OTG USB helper has everything you need, minus the tampering of the aforementioned file, without informing the user about the problem it causes with the JB update
Sent from my Galaxy Nexus using xda app-developers app

So... How do I now "untamper" the file that stickmount screwed up... without a computer? Lol. I only have my phone and Nexus 10 currently. *sigh*

Volkrik said:
So... How do I now "untamper" the file that stickmount screwed up... without a computer? Lol. I only have my phone and Nexus 10 currently. *sigh*
Click to expand...
Click to collapse
I copied the file debuggerd from another phone, that was not yet updated, to mine. Then the OTA update ran fine.

You must find an identical (same md5 hash check) file from an other device and copy it over the tampered one, without running "stick mount" until the ota installs.

[Q] Where is the ROM being downloaded to my phone?

I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?

glfngmble said:
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates

jhedfors said:
/data/data/org.lineageos.updater/app_updates
Click to expand...
Click to collapse
Thank You.

There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.

rigattoni said:
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.

jhedfors said:
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
Click to expand...
Click to collapse
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.

rigattoni said:
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
Click to expand...
Click to collapse
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".

jhedfors said:
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
Click to expand...
Click to collapse
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.

rigattoni said:
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
Click to expand...
Click to collapse
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.

jhedfors said:
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
Click to expand...
Click to collapse
the guys in the G4 forum are mostly connected to the unofficial version. a complete manual installation is required.
But there are some rumors in the German forum, who are using the official LineAgeOS version, where the updater script is not working.
I´ll wait for the next update in a week... may be it´s just a minor issue which will be fixed soon.

is it possible to change that path?

The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.

darrylhadfield said:
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
Click to expand...
Click to collapse
Thank you!!!! :victory::victory::victory: It works!!

rarmz said:
Thank you!!!! :victory::victory::victory: It works!!
Click to expand...
Click to collapse
Happy to help!
Now, if I can just get the attention of whoever the device maintainer is, for the Note3, to figure out the TWRP scripting issue...

Offical update to Nougat for N920A step by step. Enjoy !!!!

From The Moderator Oka1 - There are no viable links in this OP therefore, I am closing
Thanks
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC6. 1.41 GB file seems to me like nougat update.
Nougat Update Here S4CQB2-to-U4EQC6
MD5 checksum : 903aa5c5f26f430133481c4a2cfcdb69
Thanks for ABD instruction @ColoMtn
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC6-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
For who may need it this is S4CQA1 to U4QC6 update. File is around 1.5 GB and MD5 is 23d4d4c58330b618001e76fc468732d9

Congratulations! Hopefully 928a will have it soon

vista1984 said:
Congratulations! Hopefully 928a will have it soon
Click to expand...
Click to collapse
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.

I just wanted to thank you for this, going to do it now!!!! This day keeps getting better and better!!!!!

norbarb said:
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC5. 1.41 GB file seems to me like nougat update.
Nougat Update Here
Thanks for ABD instruction @ColoMtn
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC5.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC5.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC5.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
Can anyone show a screen shot of the "About Device" section of the phone settings after applying this update? Thank you in advance!

Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.

ifanr said:
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.

norbarb said:
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
Click to expand...
Click to collapse
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.

ifanr said:
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
Click to expand...
Click to collapse
I post it MD5 in first post.

norbarb said:
I post it MD5 in first post.
Click to expand...
Click to collapse
Matched.I'll try some other ways to work it out.Tks.

ifanr said:
Matched.I'll try some other ways to work it out.Tks.
Click to expand...
Click to collapse
You may try removing .zip extension and try again. Sometimes works

i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip

jerrycoffman45 said:
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
Click to expand...
Click to collapse
Two resons :
1. corrupted file
2. file in wrong place

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
I post it link to raw file try other one or re-download.

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
jerrycoffman45 said:
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
Click to expand...
Click to collapse
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.

norbarb said:
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
Click to expand...
Click to collapse
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.

ifanr said:
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
Click to expand...
Click to collapse
ALL WHO TRY PLEASE STOP. Seems like uploaded file got corrupted. I'm uploading once more

norbarb said:
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
Click to expand...
Click to collapse
It's very thoughtful of you. If you have time please post it at your convenience.

update ota with twrp

Hi,
I have twrp and stock rom on my Fire TV Stick 2 (tank). I get notification that there is an update, but whenever I try press install Unothing happens. I also tried to manually update, but it says "update failed".
Is there any way to install the latest OTA?

lars1384 said:
Hi,
I have twrp and stock rom on my Fire TV Stick 2 (tank). I get notification that there is an update, but whenever I try press install Unothing happens. I also tried to manually update, but it says "update failed".
Is there any way to install the latest OTA?
Click to expand...
Click to collapse
That is easy. Download the ota file with the settings (check update), then reboot to TWRP.
The update *.bin file is probably stored at:
Code:
/sdcard/Android/data/com.amazon.device.software.ota/files/
Check the size of the file (don't flash partial updates), a full update bin should take about 500mb. You have to rename the file from bin to zip, then flash it with twrp.

Sus_i said:
That is easy. Download the ota file with the settings (check update), then reboot to TWRP.
The update *.bin file is probably stored at:
Code:
/sdcard/Android/data/com.amazon.device.software.ota/files/
Check the size of the file (don't flash partial updates), a full update bin should take about 500mb. You have to rename the file from bin to zip, then flash it with twrp.
Click to expand...
Click to collapse
Thanks a lot.
It worked

For some reason, I can't find the new OTA in this folder anymore:
/sdcard/Android/data/com.amazon.device.software.ota/files/
Does anyone know, where the new path is?

In case the download is complete, it should be in that folder...
However, the .bin file could be also placed in /cache
Don't forget to rename the file to .zip, or twrp install won't show/find the file.