Related
Hi all,
Having real troubles with my phone trying to take the CM update (status 7 error), I need a flashable bootloader and baseband, does anybody have a link to the latest version? I can only find 4.4.1
My PC is away so I have no access to fastboot at present.
I have been using CM Nightlies for some time, I have updated to the latest CWM touch 6.0.4.5 and tried TWRP 2.7, both with the same results, my research leads me to suggest the fix id an updated bootloader, the only 1 I can find is the original, but this is not flashable (no idea how to get the file (or what file actually)
Phone is a Nexus 5 KOT49H
Hope you can help
pittnuma said:
Hi all,
Having real troubles with my phone trying to take the CM update (status 7 error), I need a flashable bootloader and baseband, does anybody have a link to the latest version? I can only find 4.1
My PC is away so I have no access to fastboot at present.
Phone is a Nexus 5 KOT49H
Click to expand...
Click to collapse
Hi,
The last radios are here: http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095.
For the Bootloader see in attachment.
Questions go in Q&A forum...
You Sir are a star, many thanks.
That solved my issue just flashing the bootloader.
thankyou.
Hammer_Of_The_Gods said:
Hi,
The last radios are here: http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095.
Click to expand...
Click to collapse
Is this definitely up to date? No Radio since December?
rootSU said:
Is this definitely up to date? No Radio since December?
Click to expand...
Click to collapse
Hi,
Nope, as far as I know...
The las factory image (KOT49H) has been released in December, nothing new from Google since this date, apart the AOSP KVT49L without new radio (obviously).
This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.
shouldnt we also be updating the radio?
diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver
diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit
diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.
Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?
janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?
trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.
janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.
works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!
I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.
This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-49)
WARNING:
The SU4TL-49 bootloader fixes the exploit used for the SunShine unlock.
However, unlocked bootloaders will remain unlocked.
Fastboot package (Mirror)
SHA1 sum: a297a5fd84f906cdfacf4efb8c656babbfe2452f
Flashable TWRP package (Mirror)
SHA1 sum: a85d11383d2543ae527846df0156886b51021dae
5.1 (SU4TL-44)
Fastboot package (Mirror)
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package (Mirror)
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package (Mirror)
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin
Thank you good sir!
firstEncounter said:
This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb shell sync && adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-44)
Fastboot package
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
This is only for if you werent on SU4TL-44, right?
Marky__Mark said:
This is only for if you werent on SU4TL-44, right?
Click to expand...
Click to collapse
Right now it's only useful for mofo users who updated to 5.1, since their BL was left on 4.4. If you updated using the SU4TL-44 OTA or factory image, there's no need to use this, since everything is already up to date.
In the future, custom ROM users will likely need to use these images to stay up to date on BL/radio as they're released.
firstEncounter said:
Right now it's only useful for mofo users who updated to 5.1, since their BL was left on 4.4. If you updated using the SU4TL-44 OTA or factory image, there's no need to use this, since everything is already up to date.
In the future, custom ROM users will likely need to use these images to stay up to date on BL/radio as they're released.
Click to expand...
Click to collapse
Thanks
What would be nice to have is the availability of a bone-stock 5.1 flashable ROM. Once we upgrade to the new BL and radios, we won't be able to flash the stock IMGs (as far as i know) you have listed here as MOFO will no longer work. You can always FXZ but it's a pain. Thanks!
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-5-1-rooted-images-t3152563
I used cf mofed 1.6 lollypop ROM and I unlocked via sunshine and now I'm running with RR ROM , so I also need to update or flash these packages ?? SU4TL-44 ??
GeoFX said:
What would be nice to have is the availability of a bone-stock 5.1 flashable ROM. Once we upgrade to the new BL and radios, we won't be able to flash the stock IMGs (as far as i know) you have listed here as MOFO will no longer work. You can always FXZ but it's a pain. Thanks!
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-5-1-rooted-images-t3152563
Click to expand...
Click to collapse
Once the bootloader is unlocked, you'll just be able to flash the system images using
Code:
fastboot flash system xt1254-5.1-stock-system-v3.img
You'll also want to flash the boot.img and wipe data/cache if coming from a different ROM. Then you'll be able to flash your own SuperSU/Xposed, etc zips over it if desired.
I probably won't be packaging them into a flashable zip due to the file size. I'd just recommend making a backup of the stock ROM in TWRP.
aneeshmbabu said:
I used cf mofed 1.6 lollypop ROM and I unlocked via sunshine and now I'm running with RR ROM , so I also need to update or flash these packages ?? SU4TL-44 ??
Click to expand...
Click to collapse
It's not required, only if you want to stay up to date on radio/BL.
Thanks, flashed the zip that fixed the bootloader warning, on the razrm we did very similar, looks like I'm going to have to make a few images.
Sent from my XT1254 using XDA Free mobile app
firstEncounter said:
This will update your device to the latest radio/bootloader images available. Unlocked bootloaders will remain unlocked.
This will remove your ability to use moforoot if you're upgrading from a 4.4 bootloader, so only use this if you're unlocked using SunShine.
I will update this thread as new OTAs come out.
Instructions for using fastboot packages:
Code:
adb shell sync && adb reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
Or if you have TWRP installed, you can use the flashable TWRP packages instead.
5.1 (SU4TL-44)
Fastboot package
SHA1 sum: a89e128f9eb518091f3370d3f2c83ab27f759732
Flashable TWRP package
SHA1 sum: 7b2d632aabdf8718650644bf74fb2824c31907c1
"Unlocked" warning removal
Flashable TWRP package
SHA1 sum: cc30ea56d134ef4585b7c2600ffff50955b10c07
Also flashable using fastboot by using
Code:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
Hey @firstEncounter thanks for your work! I used your v3 rooted system image via mofo in order to get sunshine to work, now I'm unlocked! Just to be clear after I take these steps will I be on official stock 5.1? I used your steps to pre flash those things prior to flashing 5.1 with mofo as you had said it would allow us to downgrade to kk. Is it necessary to go back to kk in your opinion? Any benefit? Basically I'm asking if I should keep the current setup or do this flash? Thanks in advance.
bigguy0691 said:
Hey @firstEncounter thanks for your work! I used your v3 rooted system image via mofo in order to get sunshine to work, now I'm unlocked! Just to be clear after I take these steps will I be on official stock 5.1? I used your steps to pre flash those things prior to flashing 5.1 with mofo as you had said it would allow us to downgrade to kk. Is it necessary to go back to kk in your opinion? Any benefit? Basically I'm asking if I should keep the current setup or do this flash? Thanks in advance.
Click to expand...
Click to collapse
After these steps you'll be running the latest bootloader, it won't affect the ROM you're running. There will likely be no perceivable changes other than the version number in the bootloader menu, but there's also no reason to stay on the 4.4 bootloader.
With an unlocked bootloader, downgrading to KK should be possible (haven't tried it), though at this point I don't see why there would be any reason to do so.
I'm looking in about phone, but I can't tell how I'd know that I'm on the latest bootloader and radios.
Droid1019 said:
I'm looking in about phone, but I can't tell how I'd know that I'm on the latest bootloader and radios.
Click to expand...
Click to collapse
In the bootloader, you'll see version 70.86 for BL and 11.05.16.02R for Baseband.
Assuming I can use the "unlocked warning removal" if I unlocked from 5.1 and did not come from a mofo root device?
m4rk0358 said:
Assuming I can use the "unlocked warning removal" if I unlocked from 5.1 and did not come from a mofo root device?
Click to expand...
Click to collapse
Yes.
Just checking before I flash: will the unlocked warning remover set it back to the same M logo it was before, or is this a different boot logo?
Thanks!
Coronado is dead said:
Just checking before I flash: will the unlocked warning remover set it back to the same M logo it was before, or is this a different boot logo?
Thanks!
Click to expand...
Click to collapse
Same logo, just no unlocked warning.
Came from Mofo 5.1 to Sunshine and running ComputerFreak's Unlocked 1.2 rom. Updated Booloader/baseband and removed bootloader warning files both flashed in TWRP with no problems. Thank you!
Any bugs with the twrp flashable bootloader unlock warning zip file?
Sent from my XT1254 using Tapatalk
It worked fine.
Sent from my DROID Turbo using XDA Free mobile app
hi...
i came from stock 7.0. ( htc_hiaeuhl / 2.17.401.2 )
1. unlocked bootloader - done
2. flashed twrp - done
3. flashed lineageos14.1 rom - done
4. flashed gapps arm64 7.1 nano - done
when rebooting after all that, the phone is stuck in kinda bootloader loop.
any hints for me? thank you.
I am pretty sure that if you came from Stock Nougat you will have to downgrade to MM firmware before going to LineageOS.
https://forum.xda-developers.com/one-a9/general/cm14-nightlys-discussion-support-t3510157/
yup... after reading and trying all night, i guess that it is not possible to downgrade unless i do this soff thing.
or will there be a way to install lineage in the future maybe?
paparansen said:
yup... after reading and trying all night, i guess that it is not possible to downgrade unless i do this soff thing.
or will there be a way to install lineage in the future maybe?
Click to expand...
Click to collapse
HTC did not released the kernel source for Nougat yet. When it will be done, you should expect LOS to work with the 2.xx.xxx.x firmwares
You might be able to downgrade even if s-on (check my ruu thread in the general section). You'll need to edit your /misc partition and have a signed marshmallow firmware.zip file for your cid/mid (i.e extracted from an old marshmallow ota update).
thank you for that information and your help.
i did read again a lot of stuff, tried this and that, it was horrible
- i modified like explained in your thread, then i flashed a marshmallow firmware, which went well. then i tried to flash latest marshmallow ruu, did not went well and phone was stuck in bootloader with an error about init mgr blabla.
tried and tried and tried, no chance in any way.
then i tried flashing twrp, which worked.
after that i flashed latest lineage, et voila.
as i can live without original rom, this is ok for me.
thank you!
alray said:
HTC did not released the kernel source for Nougat yet. When it will be done, you should expect LOS to work with the 2.xx.xxx.x firmwares
You might be able to downgrade even if s-on (check my ruu thread in the general section). You'll need to edit your /misc partition and have a signed marshmallow firmware.zip file for your cid/mid (i.e extracted from an old marshmallow ota update).
Click to expand...
Click to collapse
Hi,
Same problem for me I think. Glad to read there is a solution until LineageOS becomes compatible with 2.xx.xxx.x firmwares . I understand what I have to do : downgrade to marshmallow firmware, using S-ON method.
I only wonder where to find the signed marshmallow firmware.zip because there are none in the HTC One A9 RUU Collection thread (there are only Nougat firmwares).
I need version-main 1.56.401.70. I found the RUU (1,8 Go) in the thread but not the firmware. I tried to extract firmware files from RUU with RUU_Decrypt_Tool, but I don't know how to make them flashable for SDcard method.
I also found a link from you alray https://www.androidfilehost.com/?fid=817550096634758247 but file doesn't seem to be available anymore (about 100 Mo). Do you still have it please ?
aegidius_7 said:
Hi,
Same problem for me I think. Glad to read there is a solution until LineageOS becomes compatible with 2.xx.xxx.x firmwares . I understand what I have to do : downgrade to marshmallow firmware, using S-ON method.
I only wonder where to find the signed marshmallow firmware.zip because there are none in the HTC One A9 RUU Collection thread (there are only Nougat firmwares).
I need version-main 1.56.401.70. I found the RUU (1,8 Go) in the thread but not the firmware. I tried to extract firmware files from RUU with RUU_Decrypt_Tool, but I don't know how to make them flashable for SDcard method.
I also found a link from you alray https://www.androidfilehost.com/?fid=817550096634758247 but file doesn't seem to be available anymore (about 100 Mo). Do you still have it please ?
Click to expand...
Click to collapse
If your phone is S-ON you can't use a firmware extracted from a ruu anyway. The firmware.zip file when extracted from a ruu is an unsigned firmware.zip (only flashable on s-off phones). You can extract the signed firmware from an ota update zip file since extracting that file from an ota doesn't require any decryption and you still have a signed firmware.zip at the end. So try to find the 1.56.401.70 ota zip, extract the firmware.zip from this file or you'll have to use Sunshine and flash the unsigned version you can get from the ruu.
I tried to extract firmware files from RUU with RUU_Decrypt_Tool, but I don't know how to make them flashable for SDcard method.
Click to expand...
Click to collapse
simply zip the files from the OUT/firmware folder (zip the files only, not the folder). If flashing with a SD card, name the zip file "2PQ9IMG", if flashing using fastboot in RUU mode, the filename doesn't matter.
alray said:
You can extract the signed firmware from an ota update zip file since extracting that file from an ota doesn't require any decryption and you still have a signed firmware.zip at the end. So try to find the 1.56.401.70 ota zip, extract the firmware.zip from this file.
Click to expand...
Click to collapse
simply zip the files from the OUT/firmware folder (zip the files only, not the folder). If flashing with a SD card, name the zip file "2PQ9IMG"
Click to expand...
Click to collapse
1.56.401.70 OTA update is not easy to find (lots of dead links).
I've just found that https://www.androidfilehost.com/?fid=24421527759885224, it seems to contain a firmware.zip that I can't open, so I'm confused since you told it is meant to be a classic zip file. Just to be sure, does this firmware seem correct to you (ota and signed)?
Boot loops after Los 14.1(nightly 05/09 Eu) on htc a9 2.18.707.1
Need 2.18.707.1 rom for a9 or something compatible
Hi
I soft bricked my phone,was trying to install lineageOs 14.1 09/05 nightly on Indian A9-which was updated to Nougat in April.
I only got bootloops.
I have unlocked bootloader , but S-On.
Firmware is 2.18.707.1
I can boot in twrp recovery or download mode etc.
Tried 2.18.617 ruu which is available online, but got error 155, which said -to use compatible rom.
Wasted a lot of nights trying to solve the issue.
Could not find compatible firmware.
Kernel etc for the same firmware has been released by Htc like 3 months ago on htc dev.com
Please help. I think 2.18.707.1 ruu will solve the issue. Or please suggest any other rom or solution which may work.
More over , I was experimenting on my wife's phone
Is LineageOS still not compatible with 2.xx.xxx.x firmwares ?
Hello, i have some issues with my htc that is breaking my head, i think is something with the S-on on my HTC one a9, the problem is that when i tried to update Lineage (the 27 of Dec) it was going allright i download i flash it and all was cool, then when it began to reboot it stuck on the htc logo, so i reset format all data and flash it again, and again stuck on the logo, i did it again with the Gapps even flashing the version i had, and still the same, htc logo, whats is breaking my head is that i can rebbot to recovery like always and when i flash the roms the gapps even magisk all is a succces, nothing wrong not even a problem during the procces, any ideas??? thank you in advance for any help i can get.
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1572/EU
and also you can find other's firmware in it.
Good new for XT 1572 users!
Many thanks!
Okay. This looks really good.
A couple of noobish questions. This phones modem/OS version/Country/Pure-style mallarky is damaging my brain, compared to my old Samsungs..
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Thank you in advance.
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
timmtn said:
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Click to expand...
Click to collapse
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
janpascal said:
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
Click to expand...
Click to collapse
it means that the version of this firmware is higher and newer,and the firmware has packed the latest security patch.
zi_mo said:
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
Click to expand...
Click to collapse
Just what I was looking for. Thank you.