Related
Wifi at work constantly needs to be disconnected and reconnected. I know this was reported issue on the developer forums on Google's site but I was wondering if anyone had a work around for Cisco routers and constantly having to disconnect/connect to get the connection working.
running the 12/24 dandvh rom with Googy kernel 1.2.4.
Thanks in advance!
Hi,
I have exactly the same ROM and kernel and mine is working fine with a lot of routers. Maybe updating the baseband could help? I've found a pretty good how-to somwhere here, including all needed files (also NON-HLOS which is for wifi), if you don't know how to do this I'm goign to search the thread and post the link here
BTW, there's an update for this kernel avaliable, 1.2.5 is the newest version, maybe this could help, too?
Here you can donwload it, remember to choose the GPE 5 version
http://forum.xda-developers.com/showthread.php?t=2741181
RCxtwin said:
Hi,
I have exactly the same ROM and kernel and mine is working fine with a lot of routers. Maybe updating the baseband could help? I've found a pretty good how-to somwhere here, including all needed files (also NON-HLOS which is for wifi), if you don't know how to do this I'm goign to search the thread and post the link here
BTW, there's an update for this kernel avaliable, 1.2.5 is the newest version, maybe this could help, too?
Here you can donwload it, remember to choose the GPE 5 version
http://forum.xda-developers.com/showthread.php?t=2741181
Click to expand...
Click to collapse
Thanks,I am trying the non-hlos modem right now to see if it fixes the wifi issues! I will report back tomorrow with hopefully good news!
Well, I am at work and still the same issue .
eissan said:
Well, I am at work and still the same issue .
Click to expand...
Click to collapse
Sad to hear that:/ updating to newest rom version doesn't help, too? Did the modem flashing work? You can look it up in setting->about phone->baseband, what does this say? Should be GNK4 at the end if everything worked.
Are we expecting any updates soon or the 5.0.1/2 update to fix the bugs that were, presumably, introduced with 5.0?
For instance, the Pebble watch disconnecting constantly. Seems perfect on my M7 with 5.0.2.
Really hope this is done quickly, as it's pretty much unusable right now.
No one knows when 5.0.1 will come, but keeping in mind that 5.1 will be released later this month I guess there's chance that Sammy might go crazy and skip 5.0.1/2 altogether and jump directly to 5.1!
If you want this topic as some request kind then its better to create it in sammobile.
Thanks for the reply.
I just hope Samsung can push through some small bugfix update then in regards to the bluetooth then. It's a big shame I can't really use the Pebble anymore.
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
s1m4an said:
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
Click to expand...
Click to collapse
Hello
May I direct you here: http://forum.xda-developers.com/gal...-official-5-0-firmware-galaxy-t3029557/page79
dariox provided this workaround, which has been working very well for me and keeping my Pebble connected.
"Download BlueTooth auto connect (UniqTec developer)
Set:
"set last device" Flag
Profiles : select all
devices : select your device, and flag in the options "healt hdp" in case of smartband ecc...
Set flag on : Bluetooth on
Device Disconnected
Device Connected"
Unfortunately, it seems to come at the cost of a constant wakelock, and battery drain, but at the moment we don't really have any other choice apart from rolling back to kitkat, getting a new phone, or stop using the Pebble.
Hope this helps.
It's Lollipop's fault, I had the same problem when I upgraded, both the early version and the official version had the same result.
I downgraded back down to KitKat and it's fine now.
A friend has an S4 (i9505) from Vodafone Spain (ATL), unlocked and using another operator microSIM (Jazztel). Last week, via OTA, she received the latest update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
After installing that OTA update, the signal level is very low, even none inside buildings, etc. This was not happening before.
In addition, the 2 soft keys (on both sides of the Home button) are not responding anymore, not even lighting up.
The Home button works, so... I think that it's not a hardware problem. Too much coincidence that the update and that hypothetical hardware problem happened at the same time...
First I did was a total hard reset, to factory settings, etc. No success, both problems (signal and soft keys) were still there.
Second, I flashed ROM manually via Odin. I flashed latest PHE one, so no Vodafone bloatware anymore: http://www.sammobile.com/firmwares/download/59311/I9505XXUHOJ2_I9505YXXHOJ1_PHE/
No success, still the same. I then did again a hard reset to factory setting, with Wipes first... and nothing.
Next thing I will do (when i have the phone in my hands again) is flashing with Odin the previous PHE one, and crossing fingers: http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/
Anyone with the same problem? Any solution/suggestion?
Flashed next-to-last Stock ROM for PHE http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/ and no success
Then I flashed Base HOH2 (4files+PIT) with Odin and... nothing either.
No idea what to try next. Suggestions?
Same here, after OTA no menu/back buttons (neither backlight or functionality)
Current status:
- seems to affect quite a lot of people, there are more threads like this on various sites
*e.g. here, here, here
- happenning after both OTA or ODIN based update to latest 5.0.1 ROM (for me it was i9505XXUHOJ2)
My findings so far:
- NO rom change seems to fix this
- it seems that touch keys' FW is updated (physically on the chip) along with the update (to version 0x12)
- Touch key FW update in menu *#2663# not applicable as it says that it won't update - versions are the same (you can check the version of driver used by ROM and the actual FW in chip on this page)
NOTE. my girlfriend has the buttons working after successful update and has both in version 0x12
Conclusion:
- It seems that the FW flashing process of the touch keys controllers somehow failed => phone says that it's also ver. 0x12 (same as android driver) but it is probably corrupted
- Re-flashing of the chip could solve the problems, however there are problems with this:
NOTES.
Menu *#2663# won't let us do the flash because of the version check - Can we use ADB to force the update on a rooted phone? Does anybody know how?
There is a slight chance, that it'll be fixed if Samsung will release some newer update which updates also the keys' FW
Samsung could release a fix, that will flash this manually as a lot of people have problem with this
!EDIT:
I've found very similar problem + solution on the Vietnamese forum bellow (don't use the files as it's for different phone!):
- to sum it up - force downgrading the FW, the update again... (any ROM cook that could help?)
see here
regards,
J.
I completely agree with you. I also tried the *#2663# path, the phone also has 0x12 touch keys FW, and it doesn't let me reflash it, either. Don't know what FW was there before the OTA update.
I have been told about the first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/download/44821/I9505XXUHOB7_I9505OXAHOB7_DBT/ and also about the last 4.4.2 one: http://www.sammobile.com/firmwares/download/40046/I9505XXUGNK4_I9505OXAGNK4_DBT/
Maybe one of those... makes something again on the Touch Keys FW?
I couldn't try anymore bcs I gave the phone back to my friend (with accesibility touch keys on-screen)
HI, have you found a solution? My Italian S4 suffered the same bug after the same upgrade. I tried to contact samsung and they said I need to replace the screen because upgrading the firmware put the electronic under stress and they got broken. I don't believe them because too many people have the same problem + my screen is two days old! Please help me!
Same problem for my S4! how we can flash/reflash/downgrade soft touch fw?
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
oiluj said:
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
Click to expand...
Click to collapse
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
kosmodisk said:
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
Click to expand...
Click to collapse
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
oiluj said:
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
Click to expand...
Click to collapse
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
BUBA0071 said:
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Click to expand...
Click to collapse
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
MoLoCEL said:
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
Click to expand...
Click to collapse
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
wild081 said:
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
Click to expand...
Click to collapse
download it again
@oiluj
HOE3 works for me. Problems start from HOF onwards.
I have also tried flashing HOA7 DBT and upgrading. Problem persists. My touchkey firmware is 0x1a and won't update no matter what Firmware package I tried. Up to now i have tried: GNG2, GNI2, GNK4, HOA7, HOB7, HOD7.
I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
MoLoCEL said:
[MENTION=3170873]I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
Click to expand...
Click to collapse
The phone that that girl gave to me, for fixing... was completely in official status. Always official ROMs, and official OTA updates, from first minute. And the problem was caused by latest official OTA update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
So the problem was not caused by any custom ROM or a not official one.
oiluj said:
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
Click to expand...
Click to collapse
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
BUBA0071 said:
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
Click to expand...
Click to collapse
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
kosmodisk said:
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
Click to expand...
Click to collapse
Wups it have been some time since it was custum, but in any cace it must have been some of the first lollipop roms. I gave to my mom 13 feb 2015 and i did a lot of flashing before that, i think one of the roms i tryed was Project Chaos. but also i tryed all the google editition roms for i9505 and cyanogen.
but when it whent back to stock it i used PDA I9505XXUHOD7 CSC I9505NEEHOD2 NEE firmware
I've got a question. When you flash the HOA7 file from the Mega link, do you use only the AP file, or you use AP,BL,CP, CSC and PIT files?
I'm gonna try to fix my S4 but i'm not sure about the right process I should follow.
Thank you!
XDA:DevDB Information
LineageOS 14.1 Q&A, ROM for the Samsung Galaxy Note 4
Contributors
jef_00, _mone, ripee
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-04-22
Last Updated 2017-04-22
Just flashed "lineage-14.1-20170227-UNOFFICIAL-trltetmo.zip" on my N910T, already installed root via TWRP, and restored my apps with TitaniumBU, and my phone keeps flashing error messages like: "com.android.phone has stopped" or "android.process.media keeps stoping", what can I do?
P.S. I come from a Note 7 6.0.1. ported rom, if that helps
Juan_Jaime98 said:
Just flashed "lineage-14.1-20170227-UNOFFICIAL-trltetmo.zip" on my N910T, already installed root via TWRP, and restored my apps with TitaniumBU, and my phone keeps flashing error messages like: "com.android.phone has stopped" or "android.process.media keeps stoping", what can I do?
P.S. I come from a Note 7 6.0.1. ported rom, if that helps
Click to expand...
Click to collapse
WipeTelephonyProviderData.zip
Flash this in TWRP.
First, thanks tremendously guys for all this hard work you do for us so we can have the latest and greatest Android system.
Okay, so on to my issue. Last night I flashed cm-14.1-20161204-UNOFFICIAL-treltexx over my N910CXXS2DQB3_N910COLB2DPE3_THL sammobile stock, and as so many have posted, it looks quite nice, but the No SIM error is too big of an issue to use on my only device. This, of course, put me into many hours researching if there has been a fix to which I have found nothing definitive. As a decades-long user of XDA I came across this post showing trltetmo.zip (T-Mobile) Snapdragon, and the treltexx (Exynos) version by jef_00. Following the posted instructions to the letter, TWRP continues to return the error "this device is treltexx but the ROM is treltexx,tredl" and stops dead with error 1. As I live in Asia, we only get the Exynos Octa-core mobiles here, so every ROM update/change I've made represents the difference between the Americas and pretty much the rest of the world, so I know the correct Exynos ROM was used last night, and it pretty much ran for many hours giving only the No SIM issue. It did turn to molasses trying to get anything to do something, but I figured I'd work that part out in time.
So now I'm using ODIN to put sammobile's latest stock release N910CXXU2DQC2_N910COLB2DPE3_N910CXXU1DPE3_HOME.tar, then root it with TWRP as I've done for many years and will try jef_00's latest release lineage-14.1-20170507-UNOFFICIAL-trltexx in hopes it will recognize the Exynos version once again. If it does, I'll then use the Bootloader/Modem combo Bootloader+Modem_N910CXXS2DQA1_6.0.1 to see if it will recognize my SIM card and allow me to use my mobile phone again.
Have any of you noticed either your Snapdragon or Exynos recognizing the ROMs incorrectly? Additionally, did/does this Bootloader/Modem combo fix the SIM issue?
Thanks for anything you can tell me.
Regards,
Cole
Does anyone know of a sound mod that works well with this ROM? Every one that I flash either has no effect or stops people from being able to hear me on a phone call.
no way of getting magisk to work for snapchat access ?
Hi everybody !
I've got a N910F and flash the 20170605 version by ripee. Baseband : N910FXXS1DQD1
I'm coming from Samsung stock version.
I connect my phone to my car (Peugeot 208) via Bluetooth. My car doesn't display titles of song from Deezer or YouTube anymore.
It display just the name of the phone.
Does anyone have the same issue ? (streaming is working)
Is there a rom for Lineage OS for my canadian note 4? (trltecan)
LedHendrix said:
Is there a rom for Lineage OS for my canadian note 4? (trltecan)
Click to expand...
Click to collapse
trltetmo, link in my signature.
ripee said:
trltetmo, link in my signature.
Click to expand...
Click to collapse
So flashing the Tmo version lets me use my phone regularly? Do I need to do anything else?
LedHendrix said:
So flashing the Tmo version lets me use my phone regularly? Do I need to do anything else?
Click to expand...
Click to collapse
Flash gapps and the latest W8 bootloader and modem in my signature, for best signal stability. You can change trltetmo to trltecan in the build.prop if you want your apps to think your phone is in fact the W8 not the T, but it's hardly important.
Vortell said:
What does creeper aroma extras do? Does it work with 910v? I'm trying to figure out how to get 4g working.
Click to expand...
Click to collapse
They are a custom aroma gapps package for the Note 4 because the Open GApps aroma package doesn't work. Are you using hsbadr's lineage on your N910V? The latest build is kinda old which is why you may be having problems with 4G.
Any chance of getting official build version?
Issues with battery life
Hi! First of all, thanks to all developers, this wouldn't be possible without you, I've been using this rom quite a while, and it's amazing, just a few questions, the battery optimization isn't as great as I wish it would be, is there any kernel to increase battery life? If there's any i would be more than happy to try it, i've been in love with this rom, it's simply brilliant, Thanks for your support and your hard work... Cheers
Hello,
I just flashed LOS 14.1, works great!
I'm trying to update my modem (as recommended by ripee), but my baseband is n910w8vlu1dpe2. I did find a file for n910w8vlu1dpi2, but no 'PE2.
It's a SM-N910W8 from Rogers in Canada.
What modem firmware should I use?
Thanks!
jaylimo84 said:
Hello,
I just flashed LOS 14.1, works great!
I'm trying to update my modem (as recommended by ripee), but my baseband is n910w8vlu1dpe2. I did find a file for n910w8vlu1dpi2, but no 'PE2.
It's a SM-N910W8 from Rogers in Canada.
What modem firmware should I use?
Thanks!
Click to expand...
Click to collapse
The only one labelled as N910W8 in my BL_CP folder.
Da_Mak said:
Hi everybody !
I've got a N910F and flash the 20170605 version by ripee. Baseband : N910FXXS1DQD1
I'm coming from Samsung stock version.
I connect my phone to my car (Peugeot 208) via Bluetooth. My car doesn't display titles of song from Deezer or YouTube anymore.
It display just the name of the phone.
Does anyone have the same issue ? (streaming is working)
Click to expand...
Click to collapse
Just to say that the Bluetooth works well now with new versions. Thank you developpers.
Flashed 20170226 trtlevzw and it wont recognize my SIM card. Then tried Resurrection Remix and same thing, shows no SIM card. Cant find any solutions anywhere and need some guidance.
azreark1 said:
Flashed 20170226 trtlevzw and it wont recognize my SIM card. Then tried Resurrection Remix and same thing, shows no SIM card. Cant find any solutions anywhere and need some guidance.
Click to expand...
Click to collapse
Flash this in TWRP either before or after flashing the rom zip, it doesn't matter: WipeTelephonyProviderData.zip
I don't ask for ETAs and my intention is not to force any release but will officiall lineage OS for the Note 4 will come in general some day?
Hey all, I was wondering if anyone could provide me with the stock recovery image from N.
The original from MM will fail when trying to system update because the updates are looking for a newer version of the rom than it thinks I am running. I have not been able to find a newer recovery anywhere.
Help me, XDA. You're my only hope.
p.s. if someone could just give me the newest image I'll just try flashing it in fastboot.
I'm having some sort of software issue with my touchscreen only working intermittently. It works fine after waking from screen off but then decides to quit at some point. I wanna totally replace my system image and the OTA packages don't contain a system image.
In this MEGA link you'll find stock recoveries from Shakalaca. In my case, since mine came preloaded with MM, Nougat recoveries won't work for me. Maybe you'll different results from it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
In this MEGA link you'll find stock recoveries from Shakalaca. In my case, since mine came preloaded with MM, Nougat recoveries won't work for me. Maybe you'll different results from it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
I'll just say "thank you," but you can safely assume that it comes with several pages worth of exclamation points that I will omit for brevity.
Seriously, thanks! Hopefully this will work out!