HI guys,
My tablet is giving me issues with my wifi all of the sudden.
It was working fine and now it just says Turning on Wi-Fi... this never stops.
I have a Huawei Mediaoad S7-301u
Any ideas how I can get my wifi back up and running?
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
lecorbusier said:
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
Click to expand...
Click to collapse
I have done a few restarts and I have also reinstalled the same rom. I am starting to think it is the rom, it seemed buggy from the start.
Which rom would you suggest?
Stability-wise it's the older the better. Stock rom and After Silence's CM10(probably gone forever) . He developed the kernel Zyr3x was also using, whose roms got buggier and buggier. Zyr3xs AOKP, maybe, that was my first custom rom on the Mediapad, but I don't remember the bugs there were. Some, but not many.
Related
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
Can somebody help me? I used the CM for a long time, but less than a month when I was with the CyanogenMod, the phone restarted and did not turn on anyway (something like a bootloop, but the darkened screen as if you were about to turn on, then lit again).
I tried to reinstall CM, but always after a short time of use, it restarts, and bootloop again.
I reinstalled the stock, but the frustration and willingness to use CM was so big that I tried to install again. Result: bootloop.
Anyway, I'm using the stock rom for a while, but still want to use CM.
Does anyone have any idea what could have happened? (All Xposed modules and mods that put into CM are the same I'm using now, but the stock has no problems)
This happened with RR rom too.
Sorry for this long text and my bad english
I want suggest you to wipe all thing system and data , cash/dalvik, (after backup) and then try to flash the ROM and just try another ROM instead CM and RR
Sent from my GT-I8190 using Tapatalk
But I've never had this problem before!
I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!!
On both rooted and non rooted rom ....
after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
Please help me get rid of this issue thanks ...!
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Nemeziz 56th said:
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Click to expand...
Click to collapse
Well i have already tried using the stock ROM without any root or recovery !!
and its still the same
however im not sure whats the zip file u r talking about and where i can get it for my Sony z2 D6502...
By the way i just thought it might be another reason that my device is lagging so much after installing like 30/40 apps.
i have overclocked my CPU with root and even after flashing the stock rom i feel like CPU settings hasn't been reset? is it possible?
its always on end MAX and less Min value on both stock/pre root rom my CPU gets very hot on TWRP specially, its more than 70Celcious so i thought maybe its a hardware issue and my CPU is overheating bcuz its old or something... and i should prolly change my CPU ?
i really don't understand whats wrong with my phone and im so confused about what to do
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Nemeziz 56th said:
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Click to expand...
Click to collapse
I dont think if its even about TWRP because i even installed the stock rom with Flashtool and started installing my apps one by one and after a couple hrs device started lagging and freezing and odd how Wifi gets soooo slow ! (like everything gets slow in it) and also when i reboot the phone it oddly takes long time on boot menu to load .
im not sure if i did anything to cause it tbh...
it just happened on a normal day...
it gets soooo slow and leaves no other way for me but factory reset option...
i have the latest rom 23.5.A.1.291
the only time i can get it temporary fixed is when i backup the rom on TWRP and factory reset the Rom and Restore it back!
and everything is working fast and fine again only for like 6 or less hours...
and while data is restoring TWRP shows the CPU Temp on +80C !! Is this normal?
Btw i have a unlocked bootloader.
do u have any idea what i should do?
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Nemeziz 56th said:
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Click to expand...
Click to collapse
man i kinda feel like its my CPU that is messsed up and idk why
cpu usage doesnt show any app, no app is taking more than 1%.
i think ,my system is overclocking...
and if it is how can i reset or stop it smh?