Database Develop

Latest KitKat stock ROM available

So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
My update is 6.09.401, but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.

algiogia said:
So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
Click to expand...
Click to collapse
Yep, you'll always loose root after an OTA update. Must ppl doesn't matter about that since it only takes a few minutes to root again.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
Click to expand...
Click to collapse
The only way to use ota update is by flashing back the stock recovery that match your version-main. Like said above, you'll loose root after an update. You can also update your phone by flashing a RUU but you'll also loose root and all your file since the RUU will make your phone stock, like if it was brand new.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
Click to expand...
Click to collapse
My update is 6.09.401,?but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
Click to expand...
Click to collapse
The latest Kitkat version is 6.09.401.12 otherwise its lollipop 7.19.401.x
I think the simplest solution since you want to stay on kitkat is to reflash your stock recovery 6.09.401.? (you didn't typed the last number), install the ota updates until you are on 6.09.401.11 or 6.09.401.12, reflash twrp and flash Supersu to re-root.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.[/QUOTE]
RUU are packages that will restore then entire phone Software and firmware partitions.

Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?

algiogia said:
Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?
Click to expand...
Click to collapse
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...

alray said:
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...
Click to expand...
Click to collapse
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?

algiogia said:
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?
Click to expand...
Click to collapse
You already are on the stock rom, just flash the stock recovery over twrp, install ota update(s) until you are on the desired version, flash twrp and supersu. There isn't really any chances to brick....
Code:
fastboot flash recovery your_stock_recovery.img
fastboot erase cache
fastboot reboot
Then boot the phone, install update(s). Once updated to the desired version, reflash twrp:
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
Boot in twrp, install supersu 2.46.zip then reboot in the OS and you're done.
But yes if you prefer you can find a stock rooted rom of 6.09.401.11 if there is still one somewhere.

How to update unlocked and rooted stock rom?

Hello there.
My G5s+ is suggesting a security update. But since I did unlock the bootloader and rooted it with magisk I did not install it.
My question is: What is the best way to update the phone?
Just flash the new stock rom? And where do I get those?
Thanks in advance.

Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?

Mr.Chainsaw said:
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Click to expand...
Click to collapse
Unlocked bootloader will not affect the OTA installation..!
The reason the OTA-Update fails is that one of the boot, system, logo or recovery partitions are changed.
Magisk modifies the boot image.
On rooted device..OTA may brick the device..so avoid OTA installation..!
Reply your current build Number from about phone..
Do a clean flash.

crazytech2 said:
On rooted device..OTA may brick the device..so avoid OTA installation..!
Click to expand...
Click to collapse
Thats why I did not do it yet. But I still want to do the update somehow.
crazytech2 said:
Reply your current build Number from about phone..
Click to expand...
Click to collapse
The Build No is
NPSS26.116-26-8

Mr.Chainsaw said:
Thats why I did not do it yet. But I still want to do the update somehow.
The Build No is
NPSS26.116-26-8
Click to expand...
Click to collapse
Flash 26-11 full firmware

Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?

Chemacky said:
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Click to expand...
Click to collapse
If that is the firmware build you need, you could try the firmware here: https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ but ensure you download the correct firmware. (credit to: https://forum.xda-developers.com/moto-g5s-plus/how-to/xt1804-able-to-lock-bootloader-npss26-t3722572) Also, verify it is the firmware you require and was the latest firmware build on your device - please don't downgrade with stock firmware (else you may hard brick with OTA updates corrupting your bootloader)...
Stock OTA updates, as mentioned above, require fully stock firmware - they will not flash with root, modifications or TWRP (and attempting to flash via TWRP may soft bootloop your device). Thus, you must re-flash the stock firmware - you may be able to save your data by omitting the 'fastboot erase userdata' command and you do not have to re-lock your bootloader. However, I'm not familiar with the G5S Plus and I hope another user can provide you with flashing commands.
I would still recommend you make a backup of your device in TWRP and keep that safe, in case you have to wipe your data for stability.

OTA updates with Magisk?

I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???

jojojones said:
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
Click to expand...
Click to collapse
What I did (might be an easier way but this was fast and easy):
1) Uninstall/remove Magisk.
2) Re-flash firmware over current system but don't do 'fastboot erase userdata'
3) Boot into your system and take all the OTA's
4) Re-install Magisk via TWRP
Took about 10 minutes. Longest part was waiting for OTA's to install.

Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?

Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.

jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
Did not work for me. Nothing has so far.

jojojones said:
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Click to expand...
Click to collapse
Use this guide:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Remove command "fastboot erase userdata" from script flash-all.bat/flash-all.sh.

jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I've tried this, and it didn't work. Ended up having to boot into TWRP, uninstall Magisk, and then reboot. Haven't bothered trying to update since I attempted that.

jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.

tjololo12 said:
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
Click to expand...
Click to collapse
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).

ptn107 said:
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
Click to expand...
Click to collapse
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.

tjololo12 said:
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
Click to expand...
Click to collapse
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.

Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Click to expand...
Click to collapse
Thanks, the rom is exactly what I was looking for, I just wasn't sure which one to use. I'd hate to install the wrong rom and mess something up.
EDIT: I did get a chance to try it and you're correct, there is no way to install an OTA to this device without fully reflashing the stock rom, taking the OTA, then installing Magisk. I tried the following steps:
1. Flash ROM given from androidfilehost
2. Reboot, wait for OTA notification
3. Boot to bootloader
4. use fastboot to temporarily boot twrp
5. flash magisk 17.1 zipfile
6. reboot to system, verify that magisk/root is installed
7. Uninstall magisk using magisk manager "Restore Images" as given in the tips.md file
8. Take OTA
the OTA still failed, so even though TWRP wasn't installed and it was still the stock recovery, I was unable to install the OTA. Shame, it'd be nice if we could get this to work, but oh well.

Change system status to Official feom Modified and install OTA

Hi,
I just unlocked my X4 (XT1900-2) to try Magisk and all worked good.
Now, when I wanted to revert, I just installed the stock image using fastboot and adb.
After installing them and re-locking my bootloader I was not able to change my system status to Official(I installed Ryzen Kernel before).
Nor I am able to install any OTA to change it to Official, can anyone tell me how can I install OTA update and change my status to Official and be stock again.
Please help!!!
Thanks in advance,
Divanshu Chauhan

Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.

Shreyas17 said:
Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.
Click to expand...
Click to collapse
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939

AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.

Shreyas17 said:
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.
Click to expand...
Click to collapse
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003

AgentDivanshu said:
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003
Click to expand...
Click to collapse
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.

Shreyas17 said:
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.
Click to expand...
Click to collapse
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?

AgentDivanshu said:
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?
Click to expand...
Click to collapse
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.

Shreyas17 said:
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.
Click to expand...
Click to collapse
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot

[Deleted]

AgentDivanshu said:
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot
Click to expand...
Click to collapse
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.

Shreyas17 said:
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.
Click to expand...
Click to collapse
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.

AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.

Shreyas17 said:
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.
Click to expand...
Click to collapse
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo

AgentDivanshu said:
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo
Click to expand...
Click to collapse
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?

Shreyas17 said:
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?
Click to expand...
Click to collapse
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?

AgentDivanshu said:
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?
Click to expand...
Click to collapse
They might release the system images till then or you might get stock rom zip available the way oreo stock rom is available now so you will be able to update your device to android 9 via fastboot not by ota ?

AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

varunbala said:
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Click to expand...
Click to collapse
Have you re-locked your bootloader after flashing this script?
Did you use Linux or Windows?

I tried relocking but then the warning changes to that of a unsigned system image being used. Don't remember the exact wordings. So then I moved to back to unlocked bootloader.
I am using windows.

Unable to install OTA

I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image

I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!

I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.

FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.

e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?

FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.