Related
Hi everyone. So I Just got a note 2 the other day after having been using a nexus 4 for the past six months. I never use stock Roms and haven't since I got my s3 a year or so ago (I seemingly change phones often...). That being said I was looking into how to root this device and which Roms were compatible etc.
It seems all Canadian note 2 devices are the same? Rogers, Bell, koodo/telus etc? Am I correct in assuming this, and if so that any of the Roms found in this forums sub forums for aosp as well as other Roms like PA etc are compatible? (if it's compatible with the att note 2 my koodo note 2 is good to go?)
Also, it seems this devices forums are outdated and dying sadly, so can anyone recommend a recently active Rom, be it aosp or not, that is highly themeable and configurable, and preferably has good s-pen support?
Much appreciated!
Oh, and a link to the correct post for rooting this device and flashing new recovery (twrp or cwm) in its latest compatible version would be awesome too.
Thanks everyone!
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Click to expand...
Click to collapse
Great Question and great response.
I recently got the Koodo note 2. I finally switched coming from my well aged HTC HD2. Anyway I have a quick question. If i'm using a TW or a AOSP rom I can't connect to my Mac adhoc network. The old roms I used on My HTC had something baked into them that allowed that. Note sure if there's a special file I have to change. Any help would be appreciated.
Thanks
Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
Click to expand...
Click to collapse
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
DelphinusMinor said:
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Click to expand...
Click to collapse
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Catalyst2012 said:
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Click to expand...
Click to collapse
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Darkshado said:
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
Click to expand...
Click to collapse
Thanks.
1) No need to check the TWRP code as your response was clear and helpful.
2) A local unlocker business told me: they have a new way that no longer requires downgrading to 4.1.1. With his codes, I could unlock the device without any additional software or PC for C$40. I explicitly asked about KNOX - he wasn't 100% clear but said he did not think it would affect it. He said they buy lists of unlock codes based on IMEI and resell them for a small profit. Koodo requires 90 days on Koodo + the same unlock $ fee. I wasn't planning on staying on Koodo that long. In perhaps the 8 hours by now I've spent reading about this on XDA, its still not certain a device with 4.3 can be customized without blowing the Knox efuse. Towelroot 'might' give me root without tripping it but the risk of losing a full 12 month warranty is not welcome. A used device might be OK if it was still on 4.1.x. If it had been downgraded from 4.3, though unlikely, I probably wouldn't know until after I got home. Otherwise I could root+custom right way and never mess with samsung roms.
Any suggestions are welcome!
DelphinusMinor said:
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Click to expand...
Click to collapse
You should be able to test it without using any of your minutes. Just call Koodo customer service from your handset (*611 I think) it should be a free call. When the voice menu begins, start recording. Ask a few questions like "Do you support custom ROMs?" or "Do you know the winning lottery numbers", or whatever, this is just a 2-way voice recording test. I use this trick all the time when testing. Enjoy.
I have a tmo note 10.1 2014. Are any of these lte roms compatible at all??
Why yes they are I'm running xKat 5.0, SE permissive stock kernel, and TWRP (and have been since the night I got that tablet a week or so ago). SO glad that T-Mobile is carrying this hardware, AND that they're generally cool with rooting / modding etc. I even told the guy at the Tmo store my "policy" that I WILL NOT buy (well, much more trade in this case :good: ) any device that has arbitrary restrictions preventing me from gaining root (i.e. the ability to administer my own device.) He was ridiculously cool... even told me he was pretty sure it was cool if I flashed custom firmware on my new completely gratis "cellspot" router if I restored it to stock before I returned it (or likely will end up buying). SO glad Tmo is making all of these pro-consumer moves... and also that it seems to be working out for them so well (not to mention, their customers)!
I've read some of your posts around here. You mention removing a few files before flashing. Did you? If so, can share with me what/how you did?
Sent from my SM-P607T using XDA Premium HD app
No, I didn't... as you've probably noticed, info re: the entire process of root, recovery, custom ROM is kind of spread out around the forum. I thought that might be necessary because I recalled reading something about having to do that to flash a p605 ROM on a p607t (might have pertained to a specific ROM or something), but I asked specifically in the xKat thread to make sure and found it (well, first by just trying it - then took a look at the thread mid flash and saw that someone had responded :good that the xKat zip can be flashed as-is. Select any options you'd like in the Aroma installer and you're good to go! (You do need to flash an additional file after at least one reboot - otherwise you'll need to enter your wifi pass after each reboot... it's the OP of the ROM thread).
I can only say for certain that xKat w/ SE permissive kernel works great on the 607t... I think any p605 ROM can actually just be flashed without modification (hopefully someone will chime in and correct me if that isn't true - I think the info about modifying zips was just speculation, but was found not to actually be the case). Just make sure to make a nandroid of the stock ROM before flashing
How are you liking the new tablet? Loving it here! I hope now the T-mobile is selling it (by far the best of their Android tablets), this device will gain back some popularity that it lost from the TabPro release a few months later. Perhaps the forum will liven up a bit
I absolutely love this tablet. Im coming from a Nexus 10 and although they share the same screen resolution, this one is much faster, sleeker, brighter, and I'm loving the S pen. I had it rooted ten minutes after i brought it home. I've also recovered from a soft brick after having flashed the wrong twrp. Woops! Ive been dying to try different rom on this bad boy, hence all the questions for you. I'm gonna give xkat a go here. I'll report back to you with my results!
Sent from my SM-P607T using XDA Premium HD app
Nice man! Feel free to PM me if you get stuck anywhere along the way
BTW: Something I just learned, even if you select the SE permissive kernel, your kernel will be enforcing unless you manually change it, either via terminal or that SElinux Changer app (forgot exactly what it's called). I had been confused re: why in "About device" it said that the kernel was SE enforcing even though I installed the permissive one. Just FYI
Does spen work on xkat anybody revert successfully and gain the function back?
Neozx25 said:
I absolutely love this tablet. Im coming from a Nexus 10 and although they share the same screen resolution, this one is much faster, sleeker, brighter, and I'm loving the S pen. I had it rooted ten minutes after i brought it home. I've also recovered from a soft brick after having flashed the wrong twrp. Woops! Ive been dying to try different rom on this bad boy, hence all the questions for you. I'm gonna give xkat a go here. I'll report back to you with my results!
Sent from my SM-P607T using XDA Premium HD app
Click to expand...
Click to collapse
Hi, I have this tablet as well I've been on this build ne2 since I got it, & rooted it with towelroot but can't for some reason update I trying to update to the latest version that cam yesterday ota but it keeps failing can u help me please pm me
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Dudzzz576 said:
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Click to expand...
Click to collapse
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
x3m_zion said:
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
Click to expand...
Click to collapse
dont know, still testing
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
How is it going? Any news for us?
danny02 said:
How is it going? Any news for us?
Click to expand...
Click to collapse
i decided to suspend the project because of school though
Estamos presos no Android 4.4.4 =/
Maldito SM-T116BU
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
mmacedoc7 said:
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
Click to expand...
Click to collapse
hi! you can read here https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-tab-3-lite-sm-t116-goyave-t3537793
pit file
Can anyone help me find pit file for galaxy sm-t116NU??????
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
deranche said:
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
Click to expand...
Click to collapse
What exactly are you trying to do?
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days ??
deranche said:
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days
Click to expand...
Click to collapse
Guys please give the firmware rom for TVRP on the TAB-3 Lite SM-T116 ! Cause when I for some reason flashed TVPP I realized that there are no custom firmwares for this device , But I need 100% working FI-WI, and cyanogen mod does not fit, cause Wi-Fi doesn't work there!
Hello XDA, I have been working on an Aosp-ish nougat rom for our beloved trltetmo. It has nearly no features yet, since it's an AOSP ROM. I'm a Nexus dev, and just recently started working on the trltetmo because I bought one. I had a marshmallow rom and kernel(but tend not to release stuff to anyone to avoid drama and the eta requests).
Downloads: https://www.androidfilehost.com/?a=show&w=files&flid=111459
I have uploaded my work to GitHub: http://github.com/TrlteNougat
For now until I get my gpu back, you have to flash this kernel for MM bootloader support: https://www.androidfilehost.com/?fid=529152257862667083
Known issues:
- Camera is wonky. It's going to be difficult to fix
- The phone acts like it's a dual sim phone, no usability is sacrificed, it just shows two APN settings and the carrier on Dialer
Features:
None yet, it's AOSPish
What is being worked on:
Bluetooth
Call audio (mixer_path issues)
The kernel source is up: https://github.com/TrlteNougat/kernel_samsung_trlte/commits/n7.0
Manifest located here: https://github.com/TrlteNougat/manifest
Nice! Subscribed.
Test build
https://www.androidfilehost.com/?fid=24723757092306996
This one doesn't reboot randomly. Still has ril and Bluetooth errors. Sound doesn't work. Camera does.
I m not dev. But great to see work on 7 ...cheers to all devs...hoping for a stable one soon thx again
I'm keeping my eye on this thank you
Sent from my SM-N910T using Tapatalk
Ril is now partially working. I can send and receive texts. Calls cause a soft reboot, but shouldn't be hard to fix. Still no data connection yet, but that'll be fixed soon enough. Wifi connects but doesn't access internet for some reason. I haven't looked into that any.
Because why not
improper bootloader and in some cases modem can cause Wi-Fi to behave similar to how you have described. I'm not a TMO user but I think there should be several versions newer than OK2
if you have any desire to return to 5.1.1 or keep the option open to do it in the future, you may want to steer clear of the newest 2 or so bootloaders as they may prohibit further downgrading. if TMO is anything like Sprint, anything PE2 and older should still permit downgrades. newer versions I have not tested or seen any info on the topic.
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Sterist said:
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Click to expand...
Click to collapse
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Manan79 said:
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Click to expand...
Click to collapse
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
USA-RedDragon said:
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Click to expand...
Click to collapse
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Manan79 said:
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Click to expand...
Click to collapse
I'll do that. Progress is still ongoing with all this. But this week I've been busy with an Android Dev's biggest bane: a full-time job ?
USA-RedDragon said:
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
Click to expand...
Click to collapse
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Manan79 said:
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Click to expand...
Click to collapse
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
USA-RedDragon said:
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
Click to expand...
Click to collapse
got it thx, let me know if you want me to test 910T builds, however i do need sim to be working for incoming/outgoing calls , cant live without that rest all i can test.
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP