Hello, the problem start when I using resurrection remix 5.1.1, I using it with agni kernel for 2 months without any problem until yesterday when I browsing using wifi, suddenly my wifi won't detect any networks, it keeps searching the networks, also bluetooth and tethering suddenly not working as well. If I turned on the Bluetooth I got error message "Bluetooth share has stopped working".
I think this caused by the rom so I clean install the rom, wiped everything except external sd card, but the problem still persist.
Then I trying to flashed DN4 rom but I got bootloop, it stucks at Samsung Note II screen, this rom was working great before I move to RR rom.
Now I go back to RR rom, but the problem getting worse now, every time I put my phone to sleep the phone get restarted, so I let the screen turn on, set the sleep time to 30 min. Someone tell me to try restoring stock rom but since I have limited bandwidth, I want to fix this without downloading stock rom. Please guide me how to fix this, is this hardware issue?
Sorry for wong English.
Sent from my GT-N7100 Resurrection Remix
Hi guys this problem finally solved by doing this method http://m.youtube.com/watch?v=QiiH5b82eew
I just don't believe, I just don't know what should I do, so I just try it, this method does not make sense but yes, it's working [emoji28] sorry for the trouble.
Sent from my GT-N7100 Resurrection Remix
Related
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !
Okay so, first off, I'm not much of a noob in flashing ROMS and tools, I've had a bit of experience with a Samsung Infuse before, now I got this Note 2 and TouchWiz pissed me off, of course, now I need a lolipop ROM, I used ODIN to root and install TWRP recovery, also flashed a 5.1.1 "RESSURECTION" ROM, tried CM12 too, now the thing is, I'm getting a weird lag, this lag occurs randomly, lasts 2-3 seconds, followed up with a weird vibration, yes the vibrator vibrates the fone whenever this lag occurs... Now I tried a lot of stuff, except unlocking the bootloader because I'm not sure if it'll fix it or not, also after a while I noticed that it didn't detect my SIM card, could it be that my phone is refurbished? Everything else works ok but the lag makes it unusable.. The lag occurs on both CM12 and the other ROM so I don't think it's because of the ROM.. I'll revert to stock Kitkat using ODIN, but I really need to fix this. I tried Google for solutions but I can't seem to find anyone else having the same problem... So please help me out here mates
Yo guys,
I flashed the resurrection remix ROM for my zenfone 2 (Z00A) last month but its been a big pain in the a$$. Firstly,I get a lot of bootloops. Secondly, the phone sometimes shows no range on cellular service even though I should be getting it (I'm sure as heck cuz I used to get it in my house). Due to that i restart my phone and encounter the bootloops until finally I get it to work somehow. Sometimes I would even have to WIPE everything (DATA,System,Dalvic cache,etc excluding Internal and External Data) and flash the ROM,g apps , SuperSU again. These problems were encountered in 5.6.5. I recently upgraded the ROM to 5.6.6 by downloading and flashing the ROM but the same problems along with new ones :crying: came up. I usually charge my phone in the night and turn the charge off for use immediately after I wake up. The following problem was not there in 5.6.5 but in 5.6.6 the phone restarts itself in the night (probably when I'm asleep) and it just gets stuck in bootloop and is extremely hot and my hand starts to hurt probably from the radiation or something but then when I just hold on to the power button, turn it off and back on again, it works like normal and has 100% charge. Please suggest a good ROM (other than cyanogenmod as that too has the problems except the bootloop from 5.6.5) if you guys can't figure out the problem.
P.S. Yes I've tried fixing permissions
Phone: Asus Zenfone 2 (4GB RAM Edition) Z00A
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Guys any help
KartmanCV said:
Guys any help
Click to expand...
Click to collapse
Use some other rom... Recommended crdroid latest build... Use picogapps... And try again...
The issue could be rom related and even after trying new rom the problem still persists then it could be a baseband issue...
Try the recommended rom first with complete full wipe .. Good luck
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
nicky.phoenicks said:
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
Click to expand...
Click to collapse
Were you able to fix it??? How did you resolve? After three years, I faced this issue all of a sudden after I changed my phone's battery, and tried everything with software but no fix. Any possibility that it is a hardware issue? How can it be deeply inspected to find the real cause of this problem?
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Is there any fix found for this? or is it forever? Need help, need to give this phone to someone but can't fix this issue. Please help through any ways.
You may try resetting the carrier and wifi network. This may help.
You may try resetting the carrier and wifi network. This may help.
Does anyone have issues with bluetooth? When I connect to my car it will reboot my phone in around 15-20 mins. I"m on crDorid now but it also happened on Syberia but everything was fine on stock global 12.5.2. I have already flash back to stock Miui and then reinstall crDorid rom, It still having the same issues. I have also turn off location scan for wifi and bluetooth.
Thanks
I have same issue but im in LineageOS, I tested ArrowOS and it was the same.
Swapped to evox and still having the same issue. I might just go back to stock rom.
I'll have to test it too.. I was bored to pair it to be honest but I'll do it to check it.
Not sure if it helps but I'm using another ROM with I think is not allowed on XDA (helluvaOS), and used a bluetooth headphone for 35min today, without problems.
spoonsports said:
Swapped to evox and still having the same issue. I might just go back to stock rom.
Click to expand...
Click to collapse
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.
.
franko_m19 said:
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.
Click to expand...
Click to collapse
Thanks for letting me know. I had to go back to stock because my phone was rebooting every 5 mins at some locations. But after I saw shadowam said that the banned OS was working so I gave that a try and its been good so far. Only 1 random reboot after using android auto the whole day.