I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
UPDATE 4/13/2014
Here is a new version for Namidairo's CM11 3/31/2014 update.
UPDATE 1/26/2014
Here is a new version for Namidairo's CM11 1/23/2014 update.
rayden25 said:
I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
Click to expand...
Click to collapse
Nice work!
Right when I was about to break kernel compatibility.
Edit: Well not really, you just won't have access to the sysfs for fsync toggle. Just recompile when I push it.
Just let me know when you push it and I will recompile it and post it again.
Updat in OP.
rayden25 said:
I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
UPDATE 1/26/2014
Here is a new version for Namidairo's CM11 1/23/2014 update.
Click to expand...
Click to collapse
So this must be flashed through nvflash commands? Or do you have a zip flashable? I'm assuming this is obviously only compatible with CM11?
TappEd from my Note II
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yes, needs to be nvflash only. I do not have a flashable zip. This should work with many of the kitkat cm11 builds out now.
Here is a flashable zip. Warning this is untested, but should work fine.
I tried to flash the zip file, but got a "failed" message. I'm using Voyager2k's modified bl /twrp...
I'm needing a CM11 Kernel and this one the only one I could find. I don't have NVFlash though. Any other way of flashing this? Thanks! :good:
Is there a Kernel for CM11 or KitKat then that is flashable through TWRP??? I am trying install the BAM ROM but I need a Kernel apparently to get it flashed and this is the only one I have found that is KitKat maybe?
Can you make one for the newest build?
golokipok said:
Can you make one for the newest build?
Click to expand...
Click to collapse
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
rayden25 said:
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
Click to expand...
Click to collapse
Doesn't work. Phone crashes on mine. Will make a new one and post.
alias4ever said:
Is there a Kernel for CM11 or KitKat then that is flashable through TWRP??? I am trying install the BAM ROM but I need a Kernel apparently to get it flashed and this is the only one I have found that is KitKat maybe?
Click to expand...
Click to collapse
Kernel is device and rom specific. This kernel only works with Slimrom.
rayden25 said:
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
Click to expand...
Click to collapse
I guess many had dump their prime already . Anyway, I tried it on the 3/6/14 build but screen is still inverted though it was working perfectly on the 2/20/14 build. Do you mind modifying the kernel they are using for data2sd?
Related
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
BDogg718 said:
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
Click to expand...
Click to collapse
I'd love to see it on the fascinate! I'm rolling with it on my a500 and its freaking awesome
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
Click to expand...
Click to collapse
You don't have to unlock the fascinate its all open just put cwm on it and flash cm10.1 twrp won't work on cm10 and above so you have to use cwm use this guide here http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using Tapatalk 2
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Click to expand...
Click to collapse
cm10 includes it's own "cmupdater" app. Checks for new builds on your schedule (or manually), notifies of new builds, displays change logs, and installs the updates. Works well. It's visible on the "about phone" settings menu. Also available in the app drawer...
Sent from my SCH-I500 using xda premium
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
jt1134 said:
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
Click to expand...
Click to collapse
Nice I've never used twrp so I may have to try it
Sent from my SCH-I500 using Tapatalk 2
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
Click to expand...
Click to collapse
Thanx JT! Back-up and restore work just fine! Great work as always!
BDogg718 said:
Thanx JT! Back-up and restore work just fine! Great work as always!
Click to expand...
Click to collapse
Good to know. Thanks for testing it
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Click to expand...
Click to collapse
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
hhp_211 said:
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to see this incorporated into the devil kernel
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Thanks jt. It`s a step forward. You da man that's all I can say. :thumbup::beer:
Sent from my SCH-I500 using Xparent Green Tapatalk 2
if you are on fassy, notta posted a pa twp recovery flashable test as of now
LasVegasRomeo said:
if you are on fassy, notta posted a pa twp recovery flashable test as of now
Click to expand...
Click to collapse
does that kernel notta posted kill your WiFi?
kill type ?my wifi is workin I havent had any issues as far as i know. ran wifi a lil bit earlier and no issues. My wifi has is always crappy for me though here at home. Seems spotty a lil but like i said thats normal for me.
jt1134 said:
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Click to expand...
Click to collapse
is there a way to modify the source to use the prebuilt bootimage.Also when compiling it fails to create the utilities folder.
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
lacoursiere18 said:
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
Click to expand...
Click to collapse
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary.
This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
If needed, you can try using this update-binary that was compiled with current sources.
It goes in your zip file in the META-INF/com/google/android folder. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
santod040 said:
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary.
This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
If needed, you can try using this update-binary that was compiled with current sources.
It goes in your zip file in the META-INF/com/google/android folder. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
Click to expand...
Click to collapse
Ok thank you so much! FAST response lol. Would there be another recovery that is better to use or it doesn't matter?? Currently I am using your, I believe, ICS rooted debloated ROM stock/rooted. I was on liquidsmooth aosp and cm7 thundershed switching between them to get a feel for them... But for some reason I tried to do a full wipe and then reinstall from my restore of those two roms and try the leankernal, it's saying failed after I updated to TWRP 2.4.3
**EDIT:
Where is that zip you are talking about located.. In /system or somewhere else bc I can't seem to find it?
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Thank you!
4ext is definitely the way to go on the Thunderbolt. Best recovery ever, wish the Gnex had it.
Sent from my Galaxy Nexus using xda app-developers app
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
santod040 said:
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
Click to expand...
Click to collapse
Ok thank you! I have switched to 4ext thank you for the refferal
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
lacoursiere18 said:
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
Click to expand...
Click to collapse
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Milimbar said:
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Click to expand...
Click to collapse
Dude so far no problems with 184mhz.. Speed is no issue, no lag, no reboots, but I'll have to put it through the 24hr test to fully see how it does. And I charge my battery to 100% when installed it, approx. 4hr 41mins with pretty much none stop usage.. at 72% now. On the old kernal I would have been dead..
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
My CM version
klin1344 said:
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
cm-11-20140407-NIGHTLY-jewel.zip
rohanpatelt7 said:
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Click to expand...
Click to collapse
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Reply
numel007 said:
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
rohanpatelt7 said:
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
Click to expand...
Click to collapse
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Thanks
numel007 said:
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
rohanpatelt7 said:
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
Click to expand...
Click to collapse
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Reply
GoblinZ said:
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Click to expand...
Click to collapse
Thanks! I am going to flash this after my root tonight but just a question, are you going to be following the updates with the nighties? CM's updater won't work will it with your build of it? Thanks!
###THIS IS EXPERIMENTAL###
#I am not responsible for broken phones, missed calls, missed texts,
#cats destroying your house or anything else that happens.
#Flash this at your own risk.
####THIS DOES NOT WORK ONLY DOWNLOAD IF YOU KNOW WHAT YOU ARE DOING AND ARE ABLE TO RESTORE YOUR PHONE!####
Click to expand...
Click to collapse
Here is the last build of the broken CM build that I am uploading if anybody who know what they are doing can get it working. The boot.img file inside it does not work, you will need to flash the CM-BOOT.img file.
Again:
####THIS DOES NOT WORK ONLY DOWNLOAD IF YOU KNOW WHAT YOU ARE DOING AND ARE ABLE TO RESTORE YOUR PHONE! DO NOT LOOK AT ME IF YOU BREAK YOUR PHONE!####
Broken CM Build.
CM-BOOT.img
XDA:DevDB Information
[EXPERIMENTAL] [UNOFFICIAL] CM13 for R1 HD, ROM for the BLU R1 HD
Contributors
bullet25, ColtonDRG, jasonmerc
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Device Tree: https://github.com/Bullet25fxbx/android_device_blu_p6601
Kernel: https://github.com/Bullet25fxbx/android_kernel_mediatek_mt6735
Version Information
Status: Alpha
Created 2016-09-15
Last Updated 2016-09-15
Okay, So I can't get this working. I can't get BLU to build a boot.img file that works to boot the ROM past the CM logo, and on a boot.img that does boot to the CM logo I can not make heads or tails out of the logcats. I cam going to build one more time with ENG variant of CM and post it for anybody else to mess with. I'm officially done.
reserve 3
Nice to see some development for this device. I may give it a try but my wife may not let me till her work week over.
Really excited to see if this boots or not.
This does not boot/flash please do not try yet. I am looking into it.
Okay I got CyanogenMod recovery working. I'm trying again with the rom itself.
any updates/changes/good news?
KazuDante said:
any updates/changes/good news?
Click to expand...
Click to collapse
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
bullet25 said:
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
Click to expand...
Click to collapse
from what i seen when i tried to install it last time...it seemed like its more of where and how its installing(flashing the cm13) ....also looking at other cm13 zip files i noticed that the blu r1hd one is missing a file named system.transfer.list......idk if thats important or not but in 5 different cm13 i downloaded to compare they all had it.
also something about releasekey....but what i think is that the way its flashing it....either the mounts arent mounted or its flashing it incorrectly.
bullet25 said:
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
Click to expand...
Click to collapse
If the problem is in the kernel, you just need to use stock kernel. CM works with stock kernel, as long as the necessary proprietary "blobs" from the same version of Android were correctly added to the rom. Where are you getting your blobs from, BTW?
KazuDante said:
from what i seen when i tried to install it last time...it seemed like its more of where and how its installing(flashing the cm13) ....also looking at other cm13 zip files i noticed that the blu r1hd one is missing a file named system.transfer.list......idk if thats important or not but in 5 different cm13 i downloaded to compare they all had it.
also something about releasekey....but what i think is that the way its flashing it....either the mounts arent mounted or its flashing it incorrectly.
Click to expand...
Click to collapse
Honestly, not too sure what that is for either, I did look at the contents of the system folder on the phone and its all there.
jacoghi said:
If the problem is in the kernel, you just need to use stock kernel. CM works with stock kernel, as long as the necessary proprietary "blobs" from the same version of Android were correctly added to the rom. Where are you getting your blobs from, BTW?
Click to expand...
Click to collapse
Okay here's where I am going to admit I really don't know what I am doing. I don't even know how to figure out which blobs I need. I am under the assumption that without any blobs the phone should have at least booted but a bunch of stuff would have been force crashing. All of the guides I find are no help too because they do not explain how to figure out which blobs are needed where.
I am using the stock kernel.
bullet25 said:
Honestly, not too sure what that is for either, I did look at the contents of the system folder on the phone and its all there.
Okay here's where I am going to admit I really don't know what I am doing. I don't even know how to figure out which blobs I need. I am under the assumption that without any blobs the phone should have at least booted but a bunch of stuff would have been force crashing. All of the guides I find are no help too because they do not explain how to figure out which blobs are needed where.
I am using the stock kernel.
Click to expand...
Click to collapse
Without the blobs the most you can get is a successfully booted kernel afterwards the blobs are needed
Okay Update. Current issue is I need a selinux permissive kernel for the phone right now. CM does not like the stock kernel which seems to be enforcing. I am attempting to make a permissive kernel but not having much luck at the moment. If anybody has a working permissive kernel for this phone that I can use it would be greatly appreciated. In the meantime I am still working on getting CM booted.
bullet25 said:
Okay Update. Current issue is I need a selinux permissive kernel for the phone right now. CM does not like the stock kernel which seems to be enforcing. I am attempting to make a permissive kernel but not having much luck at the moment. If anybody has a working permissive kernel for this phone that I can use it would be greatly appreciated. In the meantime I am still working on getting CM booted.
Click to expand...
Click to collapse
Can you give me the link to your device tree, i could help
DarkBlood. said:
Can you give me the link to your device tree, i could help
Click to expand...
Click to collapse
https://github.com/Bullet25fxbx/android_device_blu_p6601
I know I'm probably missing things.
bullet25 said:
https://github.com/Bullet25fxbx/android_device_blu_p6601
I know I'm probably missing things.
Click to expand...
Click to collapse
It should be permissive already
DarkBlood. said:
It should be permissive already
Click to expand...
Click to collapse
Okay that's what I thought. The phone bootloops before getting to CM splash screen with the kernel compiled from that. Using the stock kernel the phone doesn't bootloop but doesn't get to the CM splash screen.
bullet25 said:
Okay that's what I thought. The phone bootloops before getting to CM splash screen with the kernel compiled from that. Using the stock kernel the phone doesn't bootloop but doesn't get to the CM splash screen.
Click to expand...
Click to collapse
You should do adb. Secure 0 and start adb at the beginning
Just a small update; We now have CM booting to a logo, but that's it, and can't get a log pulled because regardless of what we do we can't get adb to get out of unauthorized mode.
Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
alexp1289 said:
Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
Click to expand...
Click to collapse
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Droidify said:
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Click to expand...
Click to collapse
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery. Then flash the hltetmo test build zip or wait for official hltetmo build today. Verizon support is being baked into hltetmo so that's what we have to flash.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Ok that is what I am on. Will give this a go at some point soon! Thanks
Droidify said:
Ok that is what I am on. Will give this a go at some point soon! Thanks
Click to expand...
Click to collapse
I've only gotten a couple random reboots so far but other than that it's going great.
Sent from my SM-N900V using Tapatalk
great news bobby
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
happydad4130 said:
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
Click to expand...
Click to collapse
Go to that thread I posted and ask for help. You must be doing something wrong because I'm on Verizon and everything works great on this rom.
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
happydad4130 said:
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
Click to expand...
Click to collapse
Download 20170719:
https://download.lineageos.org/hltetmo
You also need to have TWRP for hlte installed:
https://dl.twrp.me/hlte/twrp-3.1.1-0-hlte.img.html
And flash that recovery image with flashify:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Don't forget to download a gapps package (arm 7.1):
http://opengapps.org
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
https://www.androidfilehost.com/?w=files&flid=199473
Here's where you get Odin:
http://androidhost.org/PVAIv
Follow the thread link in the OP for support and submitting bugs after flashing lineage.
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
alexp1289 said:
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
Click to expand...
Click to collapse
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
nicky666s said:
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
Click to expand...
Click to collapse
I was wrong earlier I had to update mine. OF1 works but SEPL1 is preferred since it's the lastest.
cssr said:
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
Click to expand...
Click to collapse
FYI: After flashing Synergy Kernel I lost root and Reflashing SuperSU did not work. I had to flash Magisk-v13.3 after flashing the kernel and it fixed the root problem.
http://www.stechguide.com/download-magisk-v13-3/
Also, note that if you install Magisk, it will have to be uninstalled before you do an update. If you don't, it will update and you will get an error. You can still uninstall Magisk and install the update again and then reinstall Magisk. If you change the kernel again.
@ golfslicer
I had the same problem after updating the kernel and also use the same solution. Was going to post about it but, you beat me to it.
Lineage also has root (SU) solution.
https://download.lineageos.org/extras
CIFS/SMB & NFS network share
Does anyone know how to mount a cifs/smb (or nfs) share with LineageOS?
bash script that I used with Aryamod 6.5 & 6.6 & SManager no longer works with LOS. Manually trying to mount from the LOS builtin terminal or Term. Emulator (installed from Play Store), also doesn't work.
Thanks in advance.
P.S. Also can I make this permanent by editing fstab, so that the network share is mounted on boot?
I personally don't use file sharing. But a quick search for Samba(smb) will probably give you all the help you need.
Still getting a really bad echo on this mod, same as i did on the unofficial port of CM13. Any recommendations? Thanks for any help offered.
Flashed this ROM a few days ago and had no problems with it yet. Installation was a breeze. Wiped system, data, and cache, then flashed the ROM and open gapps with twrp and it booted right up. I'm using it as a daily driver at this point because it is so stable! Love stock android! Was very pleased to hear the note 3 now has official support!