[FXZ] Athene TWRP Flashable Fastboots and Radios - Moto G4 ROMs, Kernels, Recoveries, & Other Develop

*edit*
Files have been removed for now as numerous issues have been reported.

Awesome! This is what I was looking for some time (though to do it myself but never had the time) . Now we can freely jump between Nougat and MM ROMs without having to flash multiple tedious useless stock images.
Much appreciated, best regards!

Thank you!!!!! VERY usefull!
i see that the modem zips also contains fsg files. Is there a way to check what versionnumber the currently installed fsg version of a device is?

Droidphilev said:
Thank you!!!!! VERY usefull!
i see that the modem zips also contains fsg files. Is there a way to check what versionnumber the currently installed fsg version of a device is?
Click to expand...
Click to collapse
There is no way to check on device afaik, but you can dd the fsg partition, then use imgextractor.exe in windows or mount as ext4 in linux to extract fsg contents, then open "bundle_release" and look under comments for version number.
*edit*
Unless you've somehow modified the fsg from your build's default version, you can just download your build number's corresponding radio and find the fsg version in the name of the flashable zip.
Actually, just realized, you can copy /fsg/bundle_release to your internal storage/sdcard either through a root file manager or through twrp, then open with a text editor; that's probably the easiest way.

@Q9Nap, i tried the marshmallow zip files for mpj24.139-23.1, mpj24.139-63 & mpj24.139-64. All of them returns error saying "this zip is for athene but this is athene_f" - something like this. I updated to the mpj24.139-63 before nougat....this I remember clearly. Dont remember which was the original model no. when i bought it. Can you help me which one should i flash? Mine is moto g4 plus indian variant.
Edit: i read the comments in main OP and checked my device's /fsg/bundle_release. It says FSG-8952-03.68 ......which means mpj24.139-63 or 64. But i tried them both. What is the problem here?

pron_91 said:
@Q9Nap, i tried the marshmallow zip files for mpj24.139-23.1, mpj24.139-63 & mpj24.139-64. All of them returns error saying "this zip is for athene but this is athene_f" - something like this. I updated to the mpj24.139-63 before nougat....this I remember clearly. Dont remember which was the original model no. when i bought it. Can you help me which one should i flash? Mine is moto g4 plus indian variant.
Edit: i read the comments in main OP and checked my device's /fsg/bundle_release. It says FSG-8952-03.68 ......which means mpj24.139-63 or 64. But i tried them both. What is the problem here?
Click to expand...
Click to collapse
This is caused by the device check at the beginning of the updater-script, to prevent users from trying to flash these files to the wrong device.
I wasn't aware that there are variants of athene for ro.product.device.
The simplest solution is to unzip the file(s), remove or edit the device check from the updater-script(s), then rezip and flash.
*edit*
@pron_91, I've reviewed the build.prop files for all available builds, and all of them specify ro.product.device=athene.
I'm guessing athene_f is the xt1643 dual-sim version?
Just curious, is your device subsidized?

Q9Nap said:
This is caused by the device check at the beginning of the updater-script, to prevent users from trying to flash these files to the wrong device.
I wasn't aware that there are variants of athene for ro.product.device.
The simplest solution is to unzip the file(s), remove or edit the device check from the updater-script(s), then rezip and flash.
*edit*
@pron_91, I've reviewed the build.prop files for all available builds, and all of them specify ro.product.device=athene.
I'm guessing athene_f is the xt1643 dual-sim version?
Just curious, is your device subsidized?
Click to expand...
Click to collapse
Yes my device is xt1643 dual-sim version. No, its not subsidized AFAIK.
Edit: as you said, the zip works after editing updater script. thanks

How can I tell from my build number which files I need? I have xt1625 and want to run nougat 7.1.1 the latest lineage

ivwonka said:
How can I tell from my build number which files I need? I have xt1625 and want to run nougat 7.1.1 the latest lineage
Click to expand...
Click to collapse
this is custom rom you are using. go back to stock, then check the build number in the same screen

pron_91 said:
this is custom rom you are using. go back to stock, then check the build number in the same screen
Click to expand...
Click to collapse
Thank you for your help! When I flash back to stock, which was a marshmallow, then how will I know which files I want to run when I flash to a custom nougat ROM? I'm sorry but on past devices I was more accustomed to having a description of firmware/radio that I could choose based on which ROM I was wanting to run.

ivwonka said:
Thank you for your help! When I flash back to stock, which was a marshmallow, then how will I know which files I want to run when I flash to a custom nougat ROM? I'm sorry but on past devices I was more accustomed to having a description of firmware/radio that I could choose based on which ROM I was wanting to run.
Click to expand...
Click to collapse
A custom rom is going to overwrite boot and system, and presumably ignore the oem partition, so the only thing to be concerned with is which radio to run. As mentioned in the op, any radio will likely work.

Hello @Q9Nap,
Gave it a shot today. Tried to flash the M rom that my device came with. I use a European XT1642 dual-sim 16Gb. Also here i get an error 7 while flashing. My device is an athene_f it says. I checked the build.prop of the currently installed rom. There is no "ro.product.device" in it's build.prop. Or are your zips reading "another" build.prop?
OK.... it seems that this is a problem of TWRP. Flashed TWRP made by oadam11 (Ground Zero thread). And after that the zip worked fine. Report in TWRP thread?
---------- Post added at 10:21 ---------- Previous post was at 09:30 ----------
Hi,
UPDATE:
The M version (MPJ24.139-63) for my device flashes fine and boots normally.
The N zip (NPJ25.93-14 i tried) flashes in about 5 seconds and afterwards TWRP says no OS installed
---------- Post added at 10:30 ---------- Previous post was at 10:21 ----------
ivwonka said:
Thank you for your help! When I flash back to stock, which was a marshmallow, then how will I know which files I want to run when I flash to a custom nougat ROM? I'm sorry but on past devices I was more accustomed to having a description of firmware/radio that I could choose based on which ROM I was wanting to run.
Click to expand...
Click to collapse
To use a custom N rom you only have to flash the last N modem package

Hi,
Update:
Flashing the last N modem zip end with an error: /firmware can't be installed. invalid argument.
This error together with the fact i couldn't flash the full N zip lets me think that partition table is different for N stock, or am i wrong?
Still the flashable N stock rom made by Jerome installs fine on my device.

Droidphilev said:
Hi,
Still the flashable N stock rom made by Jerome installs fine on my device.
Click to expand...
Click to collapse
Where would I find that?

Droidphilev said:
Hello @Q9Nap,
Gave it a shot today. Tried to flash the M rom that my device came with. I use a European XT1642 dual-sim 16Gb. Also here i get an error 7 while flashing. My device is an athene_f it says. I checked the build.prop of the currently installed rom. There is no "ro.product.device" in it's build.prop. Or are your zips reading "another" build.prop?
OK.... it seems that this is a problem of TWRP. Flashed TWRP made by oadam11 (Ground Zero thread). And after that the zip worked fine. Report in TWRP thread?
---------- Post added at 10:21 ---------- Previous post was at 09:30 ----------
Hi,
UPDATE:
The M version (MPJ24.139-63) for my device flashes fine and boots normally.
The N zip (NPJ25.93-14 i tried) flashes in about 5 seconds and afterwards TWRP says no OS installed
---------- Post added at 10:30 ---------- Previous post was at 10:21 ----------
To use a custom N rom you only have to flash the last N modem package
Click to expand...
Click to collapse
Thanks for the info! I have a Harpia to test with but not an Athene, so I appreciate the feedback.
Obviously there are a few differences, including different TWRP and the availability of stock N.
So I need to edit the device check to include athene_f or remove it to fix the error 7 issue.
Droidphilev said:
Hi,
Update:
Flashing the last N modem zip end with an error: /firmware can't be installed. invalid argument.
This error together with the fact i couldn't flash the full N zip lets me think that partition table is different for N stock, or am i wrong?
Still the flashable N stock rom made by Jerome installs fine on my device.
Click to expand...
Click to collapse
As for the issue with N, it could be a difference in partition table, which I purposely left out, because once it has been updated, it cannot be reverted; or it could be an issue with img2sdat.py, the tool I use to convert ext4 to sdat format. It converts differently depending on which android version is specified.

pastorbob62 said:
Where would I find that?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/development/rom-jx-s-creampie-nougat-t3554937

Droidphilev said:
https://forum.xda-developers.com/moto-g4-plus/development/rom-jx-s-creampie-nougat-t3554937
Click to expand...
Click to collapse
Ahhh! Doesn't help me since it is for G4+ models only.

pastorbob62 said:
Ahhh! Doesn't help me since it is for G4+ models only.
Click to expand...
Click to collapse
i'm sure it will work though. no harm in trying.

Droidphilev said:
i'm sure it will work though. no harm in trying.
Click to expand...
Click to collapse
I may try it at a later date. Right now I am running Tesla Ground Zero ROM and I am very happy with it. Best custom ROM I have tried to date. First one to give me better battery life than stock. :good:

Thanks to the help of @Droidphilev, I have now posted working N builds!
Please note that all of these files will fail if attempting to flash with @Shreps TWRP; please see op for versions of TWRP that will work.

Related

[HIMA][AT&T] Stock Rooted Dev Edition Rom [1.32.617.30] [7/5/2015]

Hello Ladies and Gents,
I threw together a flashable rom based off the newest update for the m9 dev edition.
This runs perfectly on the regular AT&T Variant since they are the same hardware just have minor differences.
Rom Features
-1.32.617.30 base (reverted to the old base because of calling issues)
-Odex'd (not sure why HTC still does it since ART doesn't need it)
-Rooted with SuperSU
-BusyBox
Download
I might do a little cleaning up (removing boot sound and some other stuff) let me know if you'd be interested in that.
Credits and Thanks
@OMJ @Captain_Throwback for the updater script
@clsA for the firmware and system.img that I broke apart for this zip
mine
Awesome! Thanks a ton!
Sent from my HTC One M9 using Tapatalk
How do you flash this? Is this possible to flash with S-on??
This uses a "camera-fix" base - if I flash it to my non-camerafix-ota'ed AT&T M9, will I effectively have a camera-fixed phone and be able to skip the OTA? Or does the OTA fix lower level firmware images of the camera, etc? What would happen if I flashed this on my non-ota'ed 1.32.401.15 phone?
basedboii said:
How do you flash this? Is this possible to flash with S-on??
Click to expand...
Click to collapse
Flash via twrp and you'll be fine, it might give a message about not being able to mount /system but that's a normal thing because the system is read only.
It will work with s-on because its just the system and boot partitions, OTAs won't work on it though obviously.
The North American unlocked and developer editions are the same as our phone just different firmware.
kertong said:
This uses a "camera-fix" base - if I flash it to my non-camerafix-ota'ed AT&T M9, will I effectively have a camera-fixed phone and be able to skip the OTA? Or does the OTA fix lower level firmware images of the camera, etc? What would happen if I flashed this on my non-ota'ed 1.32.401.15 phone?
Click to expand...
Click to collapse
I wouldn't do it, you're asking for bootloops, different software versions
I have the Sky Dragon dev edition -1.32.617.30 based ROM on my AT&T M9 and it works fine. I did make a nandroid backup of my stock ROM just in case it didn't work.
Cool, I tested this on my unit as well.
Like I said it's the same exact hardware, just slightly different firmware
Thanks for your work man!
thoughtlesskyle said:
Hello Ladies and Gents,
I threw together a flashable rom based off the newest update for the m9 dev edition.
This runs perfectly on the regular AT&T Variant since they are the same hardware just have minor differences.
Rom Features
-1.32.617.30 (camera fix) base
-Odex'd (not sure why HTC still does it since ART doesn't need it)
-Rooted with SuperSU
-BusyBox
Additional Changes
-NFC icon removed (if you really want it back Customize/ACC/Default, look for "Show NFC Icon" change from 0 to 1)
Download
I might do a little cleaning up (removing boot sound and some other stuff) let me know if you'd be interested in that.
Credits and Thanks
@OMJ @Captain_Throwback for the updater script
@clsA for the firmware and system.img that I broke apart for this zip
Click to expand...
Click to collapse
Confirmation number: 74993903860206517
mspayde said:
Confirmation number: 74993903860206517
Click to expand...
Click to collapse
What?
Sorry to ask this guys but how did u all get twrp on the m9 att? Every time I tried to flash twrp it gives me errors saying it can't write because system is S-ON?
basedboii said:
Sorry to ask this guys but how did u all get twrp on the m9 att? Every time I tried to flash twrp it gives me errors saying it can't write because system is S-ON?
Click to expand...
Click to collapse
You have to unlock via htc dev, then flash twrp
use the beta version of twrp as well. Then you can make a backup of your stock system .
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
thoughtlesskyle said:
Cool, I tested this on my unit as well.
Like I said it's the same exact hardware, just slightly different firmware
Click to expand...
Click to collapse
Are you able to receive phone calls? I just realized I am not but of course Im on a different ROM, I just want to see if it is the firmware thing or not.
sdotagain said:
use the beta version of twrp as well. Then you can make a backup of your stock system .
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Are you able to receive phone calls? I just realized I am not but of course Im on a different ROM, I just want to see if it is the firmware thing or not.
Click to expand...
Click to collapse
Solid question, I'll have to test when I get home. Is it just fc or doesn't connect
thoughtlesskyle said:
Solid question, I'll have to test when I get home. Is it just fc or doesn't connect
Click to expand...
Click to collapse
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
sdotagain said:
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
Click to expand...
Click to collapse
I'll flip my sim when I get home
sdotagain said:
It just does not ring. Callers hear a ring and then they get my voicemail, from my end nothing at all happens. I just restored my stock backup for now. If you get calls and everything ok, I will flash this ROM to test.
Click to expand...
Click to collapse
Just tested and it works here
thoughtlesskyle said:
Just tested and it works here
Click to expand...
Click to collapse
Cool. I'm gonna flash this one then. Thanks.
Someone needs to check and see if VoLTE works with the Developer Edition, on the M8 it did not work... Just a thought. since ATT builds are differently configured thought id throw that out there for those in a VoLTE area.

[ROM] [TW] SM-G900T_PG2 Rooted Deodexed

G900TUVS1GPG2
Rooted Deodexed BusyBox Init.d
Hi all, just wanted to share a little project i've been working on. Its the latest release for the T-mobile S5 G900T, rooted busybox deodexed and init.d support. I'm am totally new to the process of kitchens and making roms. This is my first release on this project and will release debloated and other combinations as i have time. Please enjoy and report any issues. I will try my best to help in any way.
Now for the rom and instructions.
Typical disclaimer as always, I am not responsible for any damaged caused by flashing custom software period. If you have gotten this far then you completely understand the risks involved with "flashing" custom software (ROMs). Flashing this ROM will void your warranty and trip knox.
Again this is for the T-mobile S5 G900T. Stock for the most part. Its rooted busybox deodexed and init.d support. I have replaced the stock kernel with The Imperius Curse Kernel 6-20 by @ShinySide. Edited homescreen pages. There is only one Homescreen page by default. If you need screens and widgets just add them. Removed NFC icon and removed sfinder and quick connect from pulldown menu. International Boot animation and sound. All apps in system/app & system/priv-app updated as of 7/23/2016.
You need custom recovery installed to proceed. I use TWRP, have not tested on CWM.
You need to be on a 6.0.1 bootloader! I tested on the PE1 bootloader and had no issues but i recommend a full update to PG2.
EDIT Odin flashable PG2 bootloader and Modem tar download link below
If you do not have a custom recovery installed then please go herehttp://forum.xda-developers.com/tmobile-galaxy-s5/general/root-how-to-root-sm-g900t-firmware-t3358190 then continue below.
Download ROM and move to root storage of phone. ExtSDcard or internal sd
Reboot to TWRP and tap wipe then advanced wipe and check boxes 'Dalvik/ ART cache' 'System' 'Data' and 'Cache' then swipe to wipe. Do this 3 times just to be safe. If you moved the rom to phone storage DO NOT WIPE Internal storage as you will delete the rom you just downloaded.
Go back to the main menu in TWRP and tap install, choose rom and swipe to install.
After install is complete reboot and wait around 15 minutes for boot to complete.
Download MEGA
https://mega.nz/#!H1YVyKLQ!31dCtlLQWE0al04p6-ypmNnUgCvtuGXBpxJNvIHq5rw
Download AFH
https://www.androidfilehost.com/?fid=24572369242689365
PG2 Bootloader and Modem by @ShinySide
https://www.androidfilehost.com/?fid=24665509702141030
Thanks to the following for their work. With their progress we are able to bring custom roms with a lot less effort and error than in previous times. Their work is greatly appreciated!
@ShinySide for his solid Kernel The Imperius Curse 6-20 and Bootloader/Modem tar
@Chainfire for Supersu
@osm0sis for his busybox installer
@lord-ralf-adolf for his deodexer
and
@superr for his kitchen
RESERVED
Can anyone post systemui.apk and legacyincallui.apk from G900TUVS1GPG2 thx
joiN85 said:
Can anyone post systemui.apk and legacyincallui.apk from G900TUVS1GPG2 thx
Click to expand...
Click to collapse
Here ya go if you haven't already gotten them.
I have strange problem with this ROM, hope anyone can help. After installation, I can't use adb any more. "adb devices" shows the devices is unauthorized, and under "Developer options", there is no button for "Revoke USB debugging authorizations". There is also no USB key fingerprint confirmation window.
Is it just me or the ROM?
CrendKing said:
I have strange problem with this ROM, hope anyone can help. After installation, I can't use adb any more. "adb devices" shows the devices is unauthorized, and under "Developer options", there is no button for "Revoke USB debugging authorizations". There is also no USB key fingerprint confirmation window.
Is it just me or the ROM?
Click to expand...
Click to collapse
It's actually a Kernel issue and not sure ito has been updated. Flashing another kernel will fix your issue. I will update the op and possibly link another kernel.
Can anyone post the PG2 modem and new bootloader
Delete
Sent from my SM-N910T using XDA-Developers mobile app
macasus76 said:
It's actually a Kernel issue and not sure ito has been updated. Flashing another kernel will fix your issue. I will update the op and possibly link another kernel.
Click to expand...
Click to collapse
I can confirm by flashing back the stock kernel the problem is fixed. Still look forward to the new ROM. Thanks!
CrendKing said:
I can confirm by flashing back the stock kernel the problem is fixed. Still look forward to the new ROM. Thanks!
Click to expand...
Click to collapse
Been a busy 2 weeks bit will get the debloated version up this week sometime for sure.
CrendKing said:
I can confirm by flashing back the stock kernel the problem is fixed. Still look forward to the new ROM. Thanks!
Click to expand...
Click to collapse
I broke it lmao
Be updated soon though. Have the source to G2, and for some reason Samsung supplied their own toolchain in the source (which I've never seen) so been screwing around with it.
ShinySide said:
I broke it lmao
Be updated soon though. Have the source to G2, and for some reason Samsung supplied their own toolchain in the source (which I've never seen) so been screwing around with it.
Click to expand...
Click to collapse
Awesome news, about to finish up this debloated version of PG2, please keep me posted and I'll test and include in the rom.:good:
PG2 Modem / Bootloader Update
jaleal said:
Can anyone post the PG2 modem and new bootloader
Click to expand...
Click to collapse
+1
Been looking all over for it on the Googles. I'm on CM 13 / GPE1 and don't want to flash over my current ROM.
ajinxa said:
+1
Been looking all over for it on the Googles. I'm on CM 13 / GPE1 and don't want to flash over my current ROM.
Click to expand...
Click to collapse
I've been looking into how to make a bootloader/modem flashable thru Odin but can't find any reliable up to date guides. If anyone knows where I might look to start I'm very sure I could make it, just need guidelines on how to begin.
macasus76 said:
I've been looking into how to make a bootloader/modem flashable thru Odin but can't find any reliable up to date guides. If anyone knows where I might look to start I'm very sure I could make it, just need guidelines on how to begin.
Click to expand...
Click to collapse
Gimme a minute. I'll make one. It's simple easy on Linux
ShinySide said:
Gimme a minute. I'll make one. It's simple easy on Linux
Click to expand...
Click to collapse
Yeah I kept getting errors in terminal and couldn't quite get it. Thanks a bunch!
macasus76 said:
Yeah I kept getting errors in terminal and couldn't quite get it. Thanks a bunch!
Click to expand...
Click to collapse
Everything except system.img, cache.img, boot.img and recovery.img. So full upgrade beside those 4 items.
https://www.androidfilehost.com/?fid=24665509702141030
ShinySide said:
Everything except system.img, cache.img, boot.img and recovery.img. So full upgrade beside those 4 items.
https://www.androidfilehost.com/?fid=24665509702141030
Click to expand...
Click to collapse
That made it a breeze to install.
Thanks!
debloated
macasus76 said:
Awesome news, about to finish up this debloated version of PG2, please keep me posted and I'll test and include in the rom.:good:
Click to expand...
Click to collapse
How's the debloated version coming along? I can't wait to try it out. Thanks for your hard work!
Flashed this rom. Everthing is running great, thank you. I was wondering if anybody has the stock kernel in a zip format?

CM13 on kii-l05?

I picked up a Huawei GR5 when my current phone went belly up. Was going to flash CM13 on it, but I noticed that my (Canadian) phone is model kii-l05, and I can't find any info on whether I can install CM13 on this model. Will be very sad if I'm stuck with the Huawei SW....
Are you on marsmallow?
Demian3112 said:
Are you on marsmallow?
Click to expand...
Click to collapse
Yes, it's running MM. This phone was sold by Rogers locked, and has since been unlocked. From what I can tell the difference between this and a KII-L21 is that the L05 is not listed as dual sim, despite appearing to have the same HW. It must be firmware limited to only use the usim.
jemez said:
Yes, it's running MM. This phone was sold by Rogers locked, and has since been unlocked. From what I can tell the difference between this and a KII-L21 is that the L05 is not listed as dual sim, despite appearing to have the same HW. It must be firmware limited to only use the usim.
Click to expand...
Click to collapse
I've read here that it works. You will need to do some build.prop editing because your device is single-sim.
Check out this fix for single-sim here
JT-on said:
I've read here that it works. You will need to do some build.prop editing because your device is single-sim.
Check out this fix for single-sim here
Click to expand...
Click to collapse
Thanks. This is a bit scary since the only time I've flashed CM onto a device it was a Nexus and was super easy. I think I need to make sure I know how to get back to normal MM if I mess this up before I try.
jemez said:
Thanks. This is a bit scary since the only time I've flashed CM onto a device it was a Nexus and was super easy. I think I need to make sure I know how to get back to normal MM if I mess this up before I try.
Click to expand...
Click to collapse
Yeah, in general it's not recommended to flash firmware that's not specifically supported for your device. Luckily, someone else has already taken the risk for you
JT-on said:
Yeah, in general it's not recommended to flash firmware that's not specifically supported for your device. Luckily, someone else has already taken the risk for you
Click to expand...
Click to collapse
Does it matter that the fix was done for a different device?
jemez said:
Does it matter that the fix was done for a different device?
Click to expand...
Click to collapse
Shouldn't be a problem. I found the information in the Honor 5x CM13 Unofficial thread, here.
JT-on said:
Shouldn't be a problem. I found the information in the Honor 5x CM13 Unofficial thread, here.
Click to expand...
Click to collapse
Well, I decided to try this today on my KII-L05, but started with just the plain CM13 download. Surprised a bit, but it worked fine on my device without me changing anything, calls, LTE, Wifi, Bluetooth, camera all appear to be fully functional. Only thing is my device doesn't know its device model anymore in the settings, which seems of no importance.
jemez said:
Well, I decided to try this today on my KII-L05, but started with just the plain CM13 download. Surprised a bit, but it worked fine on my device without me changing anything, calls, LTE, Wifi, Bluetooth, camera all appear to be fully functional. Only thing is my device doesn't know its device model anymore in the settings, which seems of no importance.
Click to expand...
Click to collapse
Hi Jemez,
I just got the KII-L05 also. How is the phone working for you since you flashed it?
Can you point me to the procedure you used to root?
Thanks
mouf said:
Hi Jemez,
I just got the KII-L05 also. How is the phone working for you since you flashed it?
Can you point me to the procedure you used to root?
Thanks
Click to expand...
Click to collapse
It was ok until today. I tried to do an OTA update, and it hung on the boot screen. From what I'm seeing in the forum, this looks like a known issue with not using CM13 recovery.
I didn't root, I just unlocked the bootloader, installed TWRP, did a full backup onto an external SD card, and then flashed the new ROMs onto it. The backup on the SD made life much easier today when it hung, I was easily able to revert to the original OS, make sure everything was ok, and now I've swapped to Resurrection remix.
I flashed CM13 last night on my KII-L05, boy what a difference. Very snappy!
One hiccup did occur when I installed the latest nightly via TWRP. I received an Error 7 when installing. It stated that the package was for kiwi where my device was "."
Googled around and learned that the update_script in the CM13 install package is validating the device model / variant.
Essentially I had to remove the "assert" lines validating the model in the update_script.
After that, install was successful.
By any chance do you still have your backup? I can't seem to get mine to work.
jemez said:
It was ok until today. I tried to do an OTA update, and it hung on the boot screen. From what I'm seeing in the forum, this looks like a known issue with not using CM13 recovery.
I didn't root, I just unlocked the bootloader, installed TWRP, did a full backup onto an external SD card, and then flashed the new ROMs onto it. The backup on the SD made life much easier today when it hung, I was easily able to revert to the original OS, make sure everything was ok, and now I've swapped to Resurrection remix.
Click to expand...
Click to collapse
For CM and LineageOS there is no need to do an edit of build.prop. Init will detect the variant just fine and set the props by itself. Currently the variant is not supported on CM13, will include it at least tomorrow, just got the necessary info today. After that, updates won't require editing the install script anymore because model will be set as well. Next time please inform us in the thread, we were not aware of that model at all.
i think, lineage 14.1 is now available for canadian version, check out guys..there is an announcement in the thread
thilak devraj said:
i think, lineage 14.1 is now available for canadian version, check out guys..there is an announcement in the thread
Click to expand...
Click to collapse
Yes and if you would read the thread before posting, you would have seen
a) I answered them already
b) This thread is about CM13, not CM/LineageOS 14.1 and i have not yet added support to CM13...
Which specific Lineage 14.1 should I use for KII-L95? is it the honor 5x? does it requires additional steps to do?
---------- Post added at 11:44 PM ---------- Previous post was at 11:41 PM ----------
BadDaemon said:
For CM and LineageOS there is no need to do an edit of build.prop. Init will detect the variant just fine and set the props by itself. Currently the variant is not supported on CM13, will include it at least tomorrow, just got the necessary info today. After that, updates won't require editing the install script anymore because model will be set as well. Next time please inform us in the thread, we were not aware of that model at all.
Click to expand...
Click to collapse
Can I now use Honor 5x Lineage 14.1 for KII-L05? Please advise. Thanks.

Unofficial nostalgia, LineageOS cm11 and cm12.1 Latest, build date 06/21/2017

This is the latest CM 11 AND CM 12.1 builds directly from LineageOS source.
BUTTER SmoOTH AND FAST
Built with the 4.9 toolchain.
SUPER IMPORTANT BEFORE FLASHING THIS
.......
YOU MUST DOWNGRADE TO THE STOCK CM11, THEN FLASH THIS BUILD AFTER THE DOWNGRADE.
Unlock bootloader then flash back to stock.
YOU MUST DOWNGRADE YOUR MODEM TO THE APPROPRIATE ANDROID VERSION.
You must do a full wipe of the partitions or it won't flash.
If you don't downgrade the modem, you will get a black screen when making phone calls.
cm11 build
https://mega.nz/#!StZWRLiQ!3Zgfm9PZpI8xLzKkZzullElLwWHBHuK2e0ksZQnnERA
CM 12.1 Build
https://mega.nz/#!ztYCRTTA!Q3DEzDvSCdUW1AgYOKkp4yRI42mYPdDjELHCFvbmmGM
For the die hard, this is the xposed I am using on cm11
https://mega.nz/#!K9JmRSDS!hybeipNIxAQ70FcAdRxyQ8EgUBYrWclyCF02FWTaLkI
.
I need the decryption key
---------- Post added at 09:29 PM ---------- Previous post was at 09:29 PM ----------
To download, that is
Sorry about that, I update the post with the correct link
Does this have latest android security patch level?
Like are you gonna update that to April 2017?
Does it work with F2FS ? I have one of my partition formatted with F2FS ...
amit_b said:
Does it work with F2FS ? I have one of my partition formatted with F2FS ...
Click to expand...
Click to collapse
It's not supported, but it may work. I haven't tested it. Do a nandroid backup and test.
This is a totally untouched rom built from cyanogenmod source.
I just finished installation of a new motherboard in my first OPO and realized it came with CM11 05Q! I was glad to see the phone the way it looked when I first got it back in 2014. I then installed XNPH25R and plan to keep it this way for some time! Still running the Nougat on my other phones but I have to agree with you, a nostalgic ROM is nice too!
I can't get cellular networking working for some reason :/
​
You cannot dirty flash this.
You have to completely downgrade via FASTBOOT and have the old model installed.
The new package I built will then overwrite it.
Also, remember, these old roms you may have to manually enter your apn.
Yes us old timers actually had to manually enter them back then.
Just when I think I've seen it all..
Did you update the toolchains to build it?
4.7 (nostalgia baby) toolchain.....lol
Does installing via fastboot erase internal sd?
Only if you flash userdata or userdata64
For your specific situation, you can try fastboot flash all the files except userdata
Then boot into recovery, perform factory reset, then flash the new build in the recovery. Cross fingers. But be prepared for sd data loss if something goes wrong.
But the easier way to save your sd, just copy everything to your PC via USB cable. It will save you a headache, plus it's good practice to have a back up. Then you can just fastboot everything for the full downgrade and then transfer your files back after the downgrade.
Flameron said:
Does this have latest android security patch level?
Like are you gonna update that to April 2017?
Click to expand...
Click to collapse
YES,
Lastest security patch April 2017 baked in.
Deleted.
Well, it's not time vehicle. It won't make you younger, so what's the point?
giaur said:
Well, it's not time vehicle. It won't make you younger, so what's the point?
Click to expand...
Click to collapse
What are you doing in this thread? What's the point being here?
giaur said:
Well, it's not time vehicle. It won't make you younger, so what's the point?
Click to expand...
Click to collapse
Let's be respectful.. It's a different flavor for those that want a return to kk and not lose updated security..
Setting.Out said:
Let's be respectful.. It's a different flavor for those that want a return to kk and not lose updated security..
Click to expand...
Click to collapse
Yes I know that, however I can't understand what's the point to use KitKat today. But yes, only my personal thoughts, sorry for hijacking this thread
Security patch level shows November 1 2016

[RECOVERY] TWRP 3.3.1-0 For P580 OREO Compatible! [UNOFFICIAL]

The long wait has come to an end.
This TWRP was built for P580, I cannot ensure that it works on other variants, but it should work on P585, please test it and tell me.
Your warranty is now void and all that..
This TWRP is only compatible with oreo, due to some mess Sammy did with the bootloader, it works flawlessly on oreo roms, stock and custom!
Proofie
Enough talking, here is the DL link: https://mega.nz/#!MJFlyQ7L!AcEEkbvw7aGMGLnAU8OPEVxiBhfFjThHNTvqx8CMbxQ
Use odin, put this tar file in AP, flash and you're good to go [If you're on stock rom, don't let the device boot to system as it will kill TWRP, overwriting it with stock recovery]
Remember:
You won't have access to data if it is encrypted, you'll have to format data, on the wipe menu, at the side of "Advanced Wipe" there is "Format Data"
If you plan on using the stock rom, remember to disable DM-verity
Btw, if you plan to stay on stock rom, but you broke knox and want secure folder back, try this https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Please come back and tell us if it worked! (I didn't make it to work on my debloated rom)
Thanks @marky_p for writing instructions on how to install
What is working:
Everything except samsung encryption, and any <8.1 rom
Built with P580KXU1CRJ7 source, on minimal manifest twrp, android-8.1.
Sources available:
Device tree: https://github.com/unknowwiiplayer/android_device_samsung_gtanotexlwifi
Kernel: https://github.com/unknowwiiplayer/kernel_samsung_exynos7870
Instructions on how to build are on device tree's readme.md
Now please powerful devs, bring lineage 17 to us, please!!!
Reserved, because reasons
I love you ? I will test it asap on the P580!
Dang, the touch bug ist still there
Thanks very much for your work. I'll test it on my P585Y. Hope you can port android 9/10 oneui rom and lineageOs for these devices too.
I've tested twrp on my Tab A P585Y. It worked but sometimes touch is laggy and cannot do swipe action. Thanks very much for your work. Hope the next version better
Installed it on my P580 has all touch problems That plagued all the other TWRPs for this tablet. So I guess I wrong about The fact all the other versions were based off of the android Marshmallow source code as being the cause of that. That set aside it seems to work great with Oreo!!! Greatjob!!!
Installed it on my P580 has all touch problems That plagued all the other TWRPs for this tablet. So I guess I wrong about The fact all the other versions were based off of the android Marshmallow source code as being the cause of that. That set aside it seem to work great with Oreo!!! Greatjob!!!
Thanks a lot
i tried flashing first time round on P585y
Twrp - worked fine - bit buggy/laggy on the swipe
flashed No Verity Opt Encrypt 6.1
then got stuck in this endless loop of booting - wouldnt even get to the samsung screen (still have access to download mode and recovery mode usning the associated button combination)
so i re-flashed stock firmware
re-flashed twrp
flashed supersu
again got stuck in the same endless boot loop......
any help how can i solve this?
Tried again tonight after flashing firmware ,
exact steps
Developer Options unlock Oem and allow USB Debbugging
reboot download mode
install SuperSU using ZIP (actually RAR file... would this make difference?)
went back to TWRP home menu
Reboot System.... STUCK in BOOT LOOP (doesnt even get to Samsung section - only gets to "Samsung Galaxy Tab A6 with S PEN powered by Android Page")
have waited 7 minutes now - still suck...
am i doing something wrong? is it because im using a P585y (lTE model)
i have noticed some unable to mount /data errors at times.
do i need wipe? clear cache/davlik? if so when in the process.
@unknowwiiplayer
on which stock firmware are you trying you do this?
HELP
unknowwiiplayer said:
on which stock firmware are you trying you do this?
Click to expand...
Click to collapse
Hey im using oreo 8.1
the name of the file is
P585YDXU2CRK5_P585YOLB2CRK5_XSP
if you can recommend other firmware that would work on my p585y and still give me the same functionality im easy, i dont need the LTE functionality
ANTYYY said:
Hey im using oreo 8.1
the name of the file is
P585YDXU2CRK5_P585YOLB2CRK5_XSP
if you can recommend other firmware that would work on my p585y and still give me the same functionality im easy, i dont need the LTE functionality
Click to expand...
Click to collapse
I'm using p585y, but i dont see that error on my device. I think you should flash the latest firmware then flash twrp again.
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
@unknowwiiplayer Do you have a plan porting oneUi ROM for these tablet? ??
Tung Lam said:
I'm using p585y, but i dont see that error on my device. I think you should flash the latest firmware then flash twrp again.
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
@unknowwiiplayer Do you have a plan porting oneUi ROM for these tablet? ??
Click to expand...
Click to collapse
Actually no, I hate OneUI, for me the current firmware is the pinnacle of Samsung experience, sorry
I do have some plans but I'm big noob and college will kill me if I focus on developing a ROM now :c
Okay, so I have SM P580 running 8.1. I can flash TWRP fine, but cannot flash anything after that without a bunch of errors!?!?
Thanks...
Azuma73 said:
Okay, so I have SM P580 running 8.1. I can flash TWRP fine, but cannot flash anything after that without a bunch of errors!?!?
Thanks...
Click to expand...
Click to collapse
did you format data?
ANTYYY said:
Hey im using oreo 8.1
the name of the file is
P585YDXU2CRK5_P585YOLB2CRK5_XSP
if you can recommend other firmware that would work on my p585y and still give me the same functionality im easy, i dont need the LTE functionality
Click to expand...
Click to collapse
I think that I'd have to build it again for your model using the latest kernel sources for your device, but for now I'm busy with college's online classes
I left instructions on my github sources, you can give it a try on building your own TWRP, as I don't have your device, I cannot ensure that if I biuld it will work, but it should tho
unknowwiiplayer said:
did you format data?
Click to expand...
Click to collapse
Yes… was I not supposed to?
Also, could anyone direct me to the correct files to root this thing... enlighten me as to the process? I can't find any working info on it!?!?
Sorry to ask, but I'm new to this tablet(sm p580) & it is quite frustrating TBH.
Thanks guys...
… crickets up in here
Azuma73 said:
Yes… was I not supposed to?
Also, could anyone direct me to the correct files to root this thing... enlighten me as to the process? I can't find any working info on it!?!?
Sorry to ask, but I'm new to this tablet(sm p580) & it is quite frustrating TBH.
Thanks guys...
… crickets up in here
Click to expand...
Click to collapse
did you wipe or did you format?, post some screenshots of the error, that way helping is a lot easier
unknowwiiplayer said:
did you wipe or did you format?, post some screenshots of the error, that way helping is a lot easier
Click to expand...
Click to collapse
I did format, then flash dm verity thing… got a bunch of errors. I'll recreate & get screens.
Could you direct me to files needed to try & root this thing?
Any help is appreciated… oops on that unrelated pic

Categories

Resources