Related
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.
Long story short, with above average ROM knowledge, and two previous successful flashes under my belt, I flashed Slimbean JB 4.2.1 Beta1 for my Sprint GS3 SPH-L710, and all was quite fine until I messed with menu/security/SIM PIN. Though I thought I was setting it for extra phone security, I actually implemented an unknownst-to-me feature that upon the following reboot, the phone requested a PUK code for a now-locked SIM card (my phone doesn't have a SIM card by the way).
After a long CS call to Sprint, including International Sprint, I was told to go to a local store. The short part of this story is that no one has been able to help. You see, since I DON'T have a SIM card, I have no ID to provide to Int Sprint for them to find a PUK code for me to enter. Although, I've had many troubles in doing so, I have since been able to reset the phone to stock factory settings; HOWEVER, this has NOT removed the PUK code screen, which prevents me from using the phone at all.
I am out of ideas of things to change, alter or fix to get rid of this issue. I have tried CWM and TWRP solutions with no success. In a sense, although I can do anything with the phone - recovery, download, flashing - except actually use the OS, I would consider this phone as useless as if it were bricked at this point. Any ideas from out there would be appreciated. Thanks.
Have you tried Odin
Sent from my SPH-L710 using xda premium
I would try flashing an odin stock tar, then re-rooting.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
This is good info to know. Please let us know of a solution if you find one - good luck!
Have you tried Odin
Click to expand...
Click to collapse
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I would try flashing an odin stock tar, then re-rooting.
Click to expand...
Click to collapse
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
Nothing in recovery, such as a full wipe, factory and system reset fixed the problem?
Click to expand...
Click to collapse
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
GRazor71 said:
I can use and have used Odin - no problem. I have full access to the device, just none to the OS.
I have successfully returned boot, system and recovery to stock, but this has not resolved the overriding issue. I don't believe I have tried to re-root since doing so. Perhaps that is worth a try.
EDIT: rerooting after Odin stock flash did not help the issue.
I am afraid none of these tasks worked. This issue must reside somewhere recovery can't get to, and only the OS can. The software is likely built so that a regularly performed task can't override a security issue - even if it is a false issue.
Click to expand...
Click to collapse
Have you tried wiping internal storage through twrp? I saw a solution for wiping encryption by wiping internal storage through twrp,
Mcluvin
Sent from my SCH-I800 using Tapatalk 2
Have you tried wiping internal storage through twrp?
Click to expand...
Click to collapse
Tried it last night. Though promising, this too failed.
GRazor71 said:
Tried it last night. Though promising, this too failed.
Click to expand...
Click to collapse
Do you have insurance on your phone?
Sent from my SCH-I800 using Tapatalk 2
Do you have insurance on your phone?
Click to expand...
Click to collapse
Nope.
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them worked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Sent from my SPH-L710
jazz995756 said:
This happened on my nexus and I had to get a new phone because your phone is basically locked at that point and I did try random codes and one of them forked but my lte didn't work after that neither did MMS so I just kept calling sprint non stop for a replacement and they finally gave in and gave me an exchange for free
Click to expand...
Click to collapse
Did you have to contact International Sprint CS or just regular? How long exactly did you badger them? Had you flashed the phone, increasing your Binary count? If so, did Sprint not hit you with a bill after replacement? Just curious, as I have really upped my count due to recovery flashes to try to fix the phone. I think I can still get a Samsung E-ticket through Sprint store for about $37.00. But again, I am concerned about the flash count, and being unable to reset it. Perhaps I should do what I can to really brick it once and for all before I turn it over.
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
Awesome! Thanks, will give it a go.
ChaseBroyles said:
Flash http://forum.xda-developers.com/showthread.php?t=1904099 to go to stock unrooted with stock recovery and a reset flash count.
Click to expand...
Click to collapse
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
mstrmscn said:
I don't think this will work seeing as he's already flashed an odin stock tar which brought the phone back to stock everything. :/
Click to expand...
Click to collapse
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
He wanted to reset the flash counter and go to pure stock so he could take it to the Sprint store.
Click to expand...
Click to collapse
Correct, and it worked like a charm. Thanks again!!!!!
Handsfree Activation?
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
RS7JR said:
I don't think Sprint even implements that rule anymore so he should definitely be fine. Have you tried handsfree activation ------>
http://forum.xda-developers.com/showthread.php?t=1670131
Maybe give that a whirl. I believe you must be on stock tw for this to work effectively which it sounds like you should now be on.
On second thought, your phone may not even allow you get as far as being able to dial the activation number, but just thought I'd throw it out there.
Click to expand...
Click to collapse
Yeah, I don't have any access to the phone OS whatsoever. Sprint tech has it now; doing some kind of process which includes a 40-minute file extraction and a 30+minute flash. Perhaps that will finally reset everything. If not, Sprint has already said it will then replace the phone.
Received a new GS3 today and I'm back in the game. Thank you to everyone who tried to assist me. In the end, no one on any forum, not Sprint, and not even Samsung could correct the original phone problem. The moral - be very cognizant and careful when flashing any CMDA variant of a native GSM ROM, as there could be settings within them regarding the SIM cards that GSM's do have, but CMDA's do not, or perhaps other harmful settings if messed with or changed. This warning is really nothing new to anyone flashing custom ROM's; it's simply another hard-learned lesson by one person whose adding more truth to the usefulness of such warnings.
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
It is a rooted samsung galaxy s4 M919 from t-mobile
is it stock rooted or what ROM are you running ?what kernel? what settings ? what mods? we need some detail sir but for starters if you can get it to boot try *#2263# and if its not set to automatic try clicking your options auto is the default setting
bobolinko said:
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
Remove your sd card sim card and battery let set 10 minutes put back in see if the message is still present if so you might need a new sim card.
Click to expand...
Click to collapse
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Might just be a lemon. I would just flash back to stock then take the phone and get a replacement.
bobolinko said:
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Click to expand...
Click to collapse
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
bobolinko said:
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
Click to expand...
Click to collapse
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Glad I could help. The modem isn't in your back up that's why back ups won't fix this problem. As for apps, it's from syncing your Google account. Aloha
Sent from my SGH-M919 using xda app-developers app
bobolinko said:
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Click to expand...
Click to collapse
If you chose to have Google back up and restore your apps, it will do just that.
After rooting, launching the camera app resulted in some errors. I cleared the cache and data, and everything looked fine. I went ahead and flashed a custom ROM. Then I realized the FFC was not working. I'd get camera error. Someone said that I should go back to stock to see if it worked, and I flashed stock, and it still didn't work.
Not sure what to do next. The FFC was working fine before the root operation. Any tips on how to restore the FFC functionality?
You need to supply more info as far as what os, rom, what else isn't working before you get any input. If all is well and just the camera is borked you can always flash a camera apk. Reflashing the rom may also help.
Pp.
Sent from my bluetooth equipped toaster using mind control.
PanchoPlanet said:
You need to supply more info as far as what os, rom, what else isn't working before you get any input. If all is well and just the camera is borked you can always flash a camera apk. Reflashing the rom may also help.
Click to expand...
Click to collapse
I flashed Virgin ROM (http://forum.xda-developers.com/showthread.php?t=2343513). I tried to flash over the camera.apk from OP. It didn't help. I have since then clean flashed the same ROM and a couple of its updates, and clean flashed KOT49H(http://forum.xda-developers.com/showthread.php?t=2539361). At all times the FFC did not work. Someone suggested that I flash a different kernel. I tried that but ended up in a bootloop and reverted to the KOT49H. I also did try to ODIN flash the stock ROM, but found the camera to be not working there too. I am now running the KOT49H ROM. Everything, except the FFC, works.
Not trying to be rude but this why backups are made before you flash something
Sent from an A.I. frequency
Kriptik210 said:
Not trying to be rude but this why backups are made before you flash something
Sent from an A.I. frequency
Click to expand...
Click to collapse
I believe something went wrong right after I rooted the phone. Backing up would not have achieved anything.
Maybe it's hardware failure what you're dealing with. Not sure but there may be a dialer code you can enter using your dialer that can check to see if it works or not. You may need to be stock firmware /Rom in order to do this. Google it.
****** Edit ******
Try this https://www.google.com/url?sa=t&sou...1ce0hlHnyNRhUDpxw&sig2=sLCXBjxinKSz0GeZWCkM_w
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
Maybe it's hardware failure what you're dealing with. Not sure but there may be a dialer code you can enter using your dialer that can check to see if it works or not. You may need to be stock firmware /Rom in order to do this. Google it.
****** Edit ******
Try this https://www.google.com/url?sa=t&sou...1ce0hlHnyNRhUDpxw&sig2=sLCXBjxinKSz0GeZWCkM_w
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
Click to expand...
Click to collapse
Thanks. None of those codes for the camera worked. It's annoying to go to stock. I'll just live with it for now!
Maybe it's a warranty issue.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
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