[Q] Help! NFC broken, cannot access settings - Samsung Galaxy Nexus

Sorry if this has been covered before, I'm normally good at self diagnosing my problems and fixing them with a simple search but I cannot find my answers to this problem.
I have rooted and rommed my device a few times over (bugless then AOKP currently) and some where along the line I have lost NFC abilities. Even the ability to access the "more" tab in the connections settings. If I click on it all it does is freeze and go black.
Is there any fix to this? Please help
Thank you in advance..

It looks like NFC capability is under 'non-working' list. Try to flash different rom and see what happens.

dcdgoth said:
It looks like NFC capability is under 'non-working' list. Try to flash different rom and see what happens.
Click to expand...
Click to collapse
Really?? Where did you hear that because I'm on aokp and it works just fine.
Link me to where you saw that.
OP just they reflash your current rom and see what happens.

nodstuff said:
Really?? Where did you hear that because I'm on aokp and it works just fine.
Link me to where you saw that.
OP just they reflash your current rom and see what happens.
Click to expand...
Click to collapse
he said he already re-flashed it. if the rom is perfectly fine accordingly, why is he having the problem? do you have any suggestion to fix the issue?

dcdgoth said:
he said he already re-flashed it. if the rom is perfectly fine accordingly, why is he having the problem? do you have any suggestion to fix the issue?
Click to expand...
Click to collapse
He never said he reflashed it, he said he flashed several different roms on it and with his current one his nfc doesn't work.
I know that nfc isn't on the not working list as I have that EXACT rom and it works fine.
So a reflash is the best option, wipe cache, system and dalvik, reflash rom and gapps and kernel and see how it goes.
Ps this is a nexus device, roms are mostly built from aosp so chances of things not working in roms are highly unlikely unless there is a problem with that particular device.
All the drivers etc are released for nexus devices so everything works.

Related

HELP! Installed rom and now earphone doesn't work (or any other roms installed either

I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!
Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?
Codename Android is one of the most popular roms on Rootzwiki
HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
I tried a few other roms and the issue was still there as well.
HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.
HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.

I'm so close to downgrading....

Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.
mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!
cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:
cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.
g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks
abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".

bt problem with new aokp rom 4.2.1on att samgung gs3

I read some post on here and it told me to find revert-my-alsa.zip and flash. So that's what I did and wiped data and still nothing. Anyone know something I don't.
sparky205 said:
I read some post on here and it told me to find revert-my-alsa.zip and flash. So that's what I did and wiped data and still nothing. Anyone know something I don't.
Click to expand...
Click to collapse
Bluetooth is fully working on all AOSP ROMs.. So Idk why someone would tell you to flash something...
BAM1789 said:
Bluetooth is fully working on all AOSP ROMs.. So Idk why someone would tell you to flash something...
Click to expand...
Click to collapse
Mines not. When I go to slide it from off to on it slides itself right back to off. any idea
sparky205 said:
Mines not. When I go to slide it from off to on it slides itself right back to off. any idea
Click to expand...
Click to collapse
Are you using Task's AOKP? The last few builds work without the ''revert my alsa'' zip (and you shouldn't flash it as it will break other things).
Did you make a clean flash? If you didn't, then do so.
Also, did you restore any system apps? If so, once again, clean flash and don't restore them.
Don't know what you did, but I use Task's AOKP and bluetooth works great. Just do a clean install.

[Q&A] [ROM][N5110][KK4.4.2][July-17-2015]Stock Rooted Deodexed[Regular/Debloated]

Q&A for [ROM][N5110][KK4.4.2][July-17-2015]Stock Rooted Deodexed[Regular/Debloated]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][N5110][KK4.4.2][July-17-2015]Stock Rooted Deodexed[Regular/Debloated]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No wifi
I love love love this ROM, it's incredibly fast, I've got the debloated version. But I have no wifi on it. The wifi stays off and when I try to turn it on it flips right back to off again. Any suggestions? I wiped, cache, dalvik, everything before and after and reinstalled once. Will reinstall again.
I'm using TWRP vs CWM-would that make a difference?
TwistedPenguin said:
I love love love this ROM, it's incredibly fast, I've got the debloated version. But I have no wifi on it. The wifi stays off and when I try to turn it on it flips right back to off again. Any suggestions? I wiped, cache, dalvik, everything before and after and reinstalled once. Will reinstall again.
I'm using TWRP vs CWM-would that make a difference?
Click to expand...
Click to collapse
Glad you like the rom, thanks for the feedback!
Not sure about the wifi, haven't had any trouble on mine. N5110, right?
I have Philz on mine but don't see why TWRP wouldn't be fine... What rom were you on before?
Sent from my SM-N910W8 using Tapatalk
sefrcoko said:
Glad you like the rom, thanks for the feedback!
Not sure about the wifi, haven't had any trouble on mine. N5110, right?
I have Philz on mine but don't see why TWRP wouldn't be fine... What rom were you on before?
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I had tried several, but wipe completely each time. It might've been one of the Lollipops right before. I wondered if it had anything to do with the kernal? I don't know much about that aspect of it.
TwistedPenguin said:
I had tried several, but wipe completely each time. It might've been one of the Lollipops right before. I wondered if it had anything to do with the kernal? I don't know much about that aspect of it.
Click to expand...
Click to collapse
Yes kernel controls hardware related things including wifi if I'm not mistaken. Which kernel are you using? The stock kernel included with the rom or a custom kernel?
Sent from my SM-N910W8 using Tapatalk
sefrcoko said:
Yes kernel controls hardware related things including wifi if I'm not mistaken. Which kernel are you using? The stock kernel included with the rom or a custom kernel?
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I didn't ever specifically change kernels (if that's possible). I just installed 4 or 5 different ROMs over the course of the past few wks to see which I liked. I made back ups of my original stock/rooted ROM and several that I liked. I've got SlimKat ROM on here now, would it do any good for me to go into settings and see which kernel it is? Probably not, I suspect.
TwistedPenguin said:
I didn't ever specifically change kernels (if that's possible). I just installed 4 or 5 different ROMs over the course of the past few wks to see which I liked. I made back ups of my original stock/rooted ROM and several that I liked. I've got SlimKat ROM on here now, would it do any good for me to go into settings and see which kernel it is? Probably not, I suspect.
Click to expand...
Click to collapse
Ok no that's cool. Yes it's possible to change kernels, but since you didn't flash a different one that means you had the stock kernel (which is included with the rom and works fine). Just to be sure, you have the N5110 model, right?
sefrcoko said:
Ok no that's cool. Yes it's possible to change kernels, but since you didn't flash a different one that means you had the stock kernel (which is included with the rom and works fine). Just to be sure, you have the N5110 model, right?
Click to expand...
Click to collapse
Yes, sorry. It's the N5110 model.
TwistedPenguin said:
Yes, sorry. It's the N5110 model.
Click to expand...
Click to collapse
Ok cool thanks. Really not sure what the wifi issue on your setup might be. Works fine here and for other users as far as I see. I did a quick Google searche and the top solutions seem to be a factory reset, the "wifi fixer" app in the Play Store, or possibly trying different settings/channels/reboot on your router. If nothing works, then it might be because something got corrupted in the base over time by flashing different TW/AOSP ROMs, in which case it might be worthwhile to Odin stock firmware from sammobile and then install this rom and test. Might be more hassle for you than it's worth (especially if your other ROMs already work fine), but just trying to provide options lol. You could also try Regular instead of Debloated to see if there is any difference in wifi for you there.
sefrcoko said:
Ok cool thanks. Really not sure what the wifi issue on your setup might be. Works fine here and for other users as far as I see. I did a quick Google searche and the top solutions seem to be a factory reset, the "wifi fixer" app in the Play Store, or possibly trying different settings/channels/reboot on your router. If nothing works, then it might be because something got corrupted in the base over time by flashing different TW/AOSP ROMs, in which case it might be worthwhile to Odin stock firmware from sammobile and then install this rom and test. Might be more hassle for you than it's worth (especially if your other ROMs already work fine), but just trying to provide options lol. You could also try Regular instead of Debloated to see if there is any difference in wifi for you there.
Click to expand...
Click to collapse
I appreciate your input very much! I love this rom. I've got it installed again messing around with it while the Regular version is downloading. (I'm bestowed with slow rural internet). I'll let you know if Regular works better. It's probably going to bug me enough as to why it doesn't work that I'll go to the trouble of going back to stock, re-downloading and trying it fresh
TwistedPenguin said:
I appreciate your input very much! I love this rom. I've got it installed again messing around with it while the Regular version is downloading. (I'm bestowed with slow rural internet). I'll let you know if Regular works better. It's probably going to bug me enough as to why it doesn't work that I'll go to the trouble of going back to stock, re-downloading and trying it fresh
Click to expand...
Click to collapse
Sounds good! Yeah it's a bit of a hassle but at least you have other roms to fall back on worst case, but i'll admit this is kinda bugging me too so if you get to the bottom of it please let me know . [emoji106] . Thanks again for the positive feedback btw, happy to hear the rom's working out (aside from your wifi)
Sent from my SM-N910W8 using Tapatalk
Enable Android Encryption
Has anyone been able to successfully enable android encryption using this rom? I tried with the Deodexed version, safe boot, turning off SuperSU and haven't been able to get it to start encrypting properly. I need it since I have policy looking for encrypted state before I can allow mail to be made available.
Many thanks in advance!
LD
diazlaz said:
Has anyone been able to successfully enable android encryption using this rom? I tried with the Deodexed version, safe boot, turning off SuperSU and haven't been able to get it to start encrypting properly. I need it since I have policy looking for encrypted state before I can allow mail to be made available.
Many thanks in advance!
LD
Click to expand...
Click to collapse
Not sure... does it work fine on other rooted deodexed roms?
wifi won't turn on
Hi, I've flashed both the regular version and the debloated version on my N5110 after clean wipes.
The wifi will not turn on in either case.
I've done factory resets from within settings.
Any ideas?
I've read the thread, the Q&A thread, and done a google search to no avail....
I'm coming from stock 4.2.2 (rooted and unlocked of course) where everything worked... it just seemed to have a pretty short battery life.
I've reinstalled the nandroid backup and wifi still works there.
I'd really like to try this.
Thanks for your hard work as a developer by the way
zippersmith said:
Hi, I've flashed both the regular version and the debloated version on my N5110 after clean wipes.
The wifi will not turn on in either case.
I've done factory resets from within settings.
Any ideas?
I've read the thread, the Q&A thread, and done a google search to no avail....
I'm coming from stock 4.2.2 (rooted and unlocked of course) where everything worked... it just seemed to have a pretty short battery life.
I've reinstalled the nandroid backup and wifi still works there.
I'd really like to try this.
Thanks for your hard work as a developer by the way
Click to expand...
Click to collapse
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh
sefrcoko said:
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh [/QUOTE
This^
Worked for me. Nice smooth Rom... thank you I hope this saves me from constant looping unrooted stock provided. Although battery life seems to still drain quickly. Any thoughts?
Edit to say im having a slight issue with the tablet shutting down on its own when not in use.
Click to expand...
Click to collapse
BBBlessed said:
sefrcoko said:
Not sure...Works fine here but I saw another user report this a while back. The others said all working fine so I'm assuming something may have got corrupted on your setup along the way. Perhaps you can try using odin to flash the latest stock firmware for your device from sammobile.com, then try installing twrp through odin and finally my rom through twrp. Best way to eliminate variables and start fresh [/QUOTE
This^
Worked for me. Nice smooth Rom... thank you I hope this saves me from constant looping unrooted stock provided. Although battery life seems to still drain quickly. Any thoughts?
Edit to say im having a slight issue with the tablet shutting down on its own when not in use.
Click to expand...
Click to collapse
Thanks for confirming! Yes flashing different roms can corrupt system files so a fresh odin install is always a good way to start clean. No issues here with the tablet shutting down..could possibly be due to a rogue app conflicting with something or an xposed module. As for battery life I agree. Not worse than stock but not better either. The built-in battery is now also probably less efficient than it used to be, as they all do over time. Sammy should have put a bigger battery in this tablet!
Click to expand...
Click to collapse
sefrcoko said:
BBBlessed said:
Thanks for confirming! Yes flashing different roms can corrupt system files so a fresh odin install is always a good way to start clean. No issues here with the tablet shutting down..could possibly be due to a rogue app conflicting with something or an xposed module. As for battery life I agree. Not worse than stock but not better either. The built-in battery is now also probably less efficient than it used to be, as they all do over time. Sammy should have put a bigger battery in this tablet!
Click to expand...
Click to collapse
I did a battery pull and that help a great deal with the battery life . Also I don't think I have had the issue of shutting down maybe the rom needed to settle in lol. I don't know but all is well now thank you so much for this rom. My tablet isn't trash anymore.
Click to expand...
Click to collapse
BBBlessed said:
sefrcoko said:
I did a battery pull and that help a great deal with the battery life . Also I don't think I have had the issue of shutting down maybe the rom needed to settle in lol. I don't know but all is well now thank you so much for this rom. My tablet isn't trash anymore.
Click to expand...
Click to collapse
Awesome, glad to hear it's all sorted out now. Cheers!
Click to expand...
Click to collapse
Hello sefrcoko
my Note N5110 currently has the stock fw 4.2.2.
Once I have root and custom recovery, can I directly flash your rom?
Or I have to flash the stock fw 4.4.2 before your rom?
Thanks a lot
Bye

Porting LineageOS 14 to the d710

Disclaimer: I am not a ROM developer. I am a developer and Linux user, but I know next to nothing about creating Android ROMs. Whole other world to me.
I'm wondering if all three of us Epic 4G Touch users left might be able to get a working port of LineageOS 14 on our aging handsets.
The good news:
I just loaded the Official LineageOS 14 for i9100 20170419 nightly on my d710, and IT WORKS
...almost.
The bad news:
The ROM boots up, everything works and looks normal except for:
Wi-Fi - Settings app spins with message "Turning Wi-Fi on..."
Menu Button
Home Button
Now, I'm wondering if there is a way to fix these problems. I prefer on-screen navigation anyway, so that's probably an easy "fix." But Wi-Fi will probably be trickier. I assume it's kernel related, but I can't find any Nougat kernels for this device, so that will likely be the most difficult part.
Thoughts? Anyone else out there have any input or want to give this a crack?
Links:
https://wiki.lineageos.org/devices/i9100/build
https://wiki.lineageos.org/devices/i9100/install
https://web-beta.archive.org/web/20161224202958/https://wiki.cyanogenmod.org/w/Build_for_d710
https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0
https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig
https://github.com/Lanchon/TWRP-Patcher-SGS2
https://github.com/Lanchon/REPIT
https://forum.xda-developers.com/ep.../rom-cyanogenmod-11-official-nightly-t2852074
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
svaethier said:
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
Click to expand...
Click to collapse
Link is in the OP. Here it is again: https://forum.xda-developers.com/galaxy-s2/general/rom-t3555834
Direct link to the download page: https://download.lineageos.org/i9100
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
svaethier said:
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
Click to expand...
Click to collapse
I don't know what you're talking about. I don't get an error.
The ROM flashes without modification. Make sure you have an up-to-date TWRP with the i9100 crossflash patch: https://github.com/Lanchon/TWRP-Patcher-SGS2
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
svaethier said:
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
Click to expand...
Click to collapse
I followed lots of advice from this thread: https://forum.xda-developers.com/epic-4g-touch/help/help-getting-stock-rooted-4-1-2-to-cm11-t3384832
I believe the method that finally worked for me was: Odin to EL29 rooted, Philz recovery, TWRP, CM11.
That's where I was before I tried the i9100 LOS 14.1 ROM.
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
svaethier said:
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
Click to expand...
Click to collapse
If you have root in CM11, you can use Flashify to flash the new TWRP .img file.
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
flamadiddle said:
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
Click to expand...
Click to collapse
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
flamadiddle said:
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
Click to expand...
Click to collapse
I'll reach out to some developer associates and see what I can find out about the WiFi.
Sent from my SM-S903VL using Tapatalk
I'm not a developer, but I have a D710 lying around and I am willing to do testing if you need me
I also have an Epic 4g touch that im willing to test stuff
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
chrismin13 said:
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
Click to expand...
Click to collapse
Never had any real interest, and I don't know enough to do it myself.
flamadiddle said:
Never had any real interest, and I don't know enough to do it myself.
Click to expand...
Click to collapse
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make it work for our device, because why not!
Thanks for still responding after so many months!
chrismin13 said:
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make a for for our device, because why not!
Thanks for still responding after so many months!
Click to expand...
Click to collapse
Those were the only two things I noticed. Bluetooth worked. I didn't see any apps crash (but I couldn't load new ones because no wifi). I didn't try cell service because I don't even have Sprint anymore, but I suspect that probably didn't work for the same reason wifi was killed.
Thanks for looking into this! I'm still interested if we can find a way to make it work. I just don't know much about creating ROMs. I'm not an Android dev.

Categories

Resources