Hi. I tried to flash 4.4 kitkat rooted from PA and I found the WiFi wasn't working. (which is a problem as you need to go through the new user tutorial and you're stuck at the WiFi part)
so I tried to revert back PA (4.3) but I encountered a problem. I played around the Encrypt tablet last time and had a pin code for that.
Now the strange problem is, when I load the System (trying to get into the ROM), it would ask me for the pin right? the pin is incorrect.
BUT when I put the PIN from recovery (different keyboard maybe?), IT WORKS.
WTF IS GOING ON LOL.
So now the question would be:
a) how to disable encrypted tablet mode?
b) how to fix WiFi turning on issue?
Thanks hope someone can help me.
Nvm. unrooted, update to kitkat, then re-root again.
Solved.
Related
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
I've got a rather strange problem... I'm running stock due to this issue... I'm running mm right now... Anyways, every time I root this phone, I lose my dialer program menu for example, *#0*#. I figured it was a rooting issue so I just flashed back to stock and then flashed only twrp and then flashed a mm rom. Well it still did the same thing. Anybody else having this issue or know of a fix? I need to be able to access the calibration menu for my compass for work..
Nobody has this issue? Ik I can't be the only one...
So I changed from my old ROM to Dirty Unicorn, all went well, but no pin lock on the lock screen, when I try to change that the settings part of the lockscreen lock will crash, but it will ask me for a pin to access it, tried 3 more ROMS, same problem, I have now just tried Imperium and the problem is still here!?
I have never encountered this before, anyone know how I could fix this? Also my backups fail (can't access some folder or something) so I can't even restore to my version beforehand
Any and all help is appreciated
Edit: Just going back to DU so you all know what ROM I'm running now
works fine during setup then vanishes and the wifi button doesn't do anything afterwards. is it hardware or software related?
weird thing i noticed is that any wifi related setting, will make the settings crash and not respond...
miui global 12.5.8 stable, Android version: 11 RKQ1.200826.002, security update: 2002-01-01
dunno how to explain this, but this is what it looks like when I try to do anything in the settings (google drive video)
I have also looked at this thread where it seems similar to my problem, but could not find a solution.
MIUI 12.5 wifi issues
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas? The behavior is - I...
forum.xda-developers.com
edit: seems like i have to unlock the bootloader to install a different rom, will update in a week
Sounds like a major issue , after watching the video, 2 things I would try remove sim reboot then try, of still fails the ROM must be corrupt , I would reinstall/flash sounds like you tried a factory reset so thats what I would do
thank you for your response. I did remove the sim and factory reset but no change. Can I reeinstall without having the phone unlocked? or is that only possible with an unlocked phone and the fastboot thing?
edit: found out how to local update rom, going to that and see how it goes.
edit2: installed a new rom but the issue still persist.
21sep said:
thank you for your response. I did remove the sim and factory reset but no change. Can I reeinstall without having the phone unlocked? or is that only possible with an unlocked phone and the fastboot thing?
edit: found out how to local update rom, going to that and see how it goes.
edit2: installed a new rom but the issue still persist.
Click to expand...
Click to collapse
you meant to say you just did a update? you will need unlocked bootloader I do believe but not positive if your going from stock to stock
I installed MIUI 13.0.3 with this method https://c.mi.com/oc/miuidownload/detail?guide=1 but the same problem with the WIFI persist. If it was an software issue it should have fixed it right? so I'm thinking that it might be a hardware issue instead.
21sep said:
I installed MIUI 13.0.3 with this method https://c.mi.com/oc/miuidownload/detail?guide=1 but the same problem with the WIFI persist. If it was an software issue it should have fixed it right? so I'm thinking that it might be a hardware issue instead.
Click to expand...
Click to collapse
Did you mess up with any wifi or persist thingy?
update: I unlocked the phone and installed different rom versions with MiFlash.
I installed everything step by step following this guide for installing via fastboot https://c.mi.com/thread-1857937-1-0.html.
alioth_global_images_V13.0.2.0.SKHMIXM_20220314.0000.00_12.0_global: same problem
alioth_eea_global_images_V12.5.8.0.RKHEUXM_20220210.0000.00_11.0_eea: put WiFi settings on static
worked long enough to fully setup and install some apps than it went full retard. (longest working wifi connection yet)
after a second restart, the wifi is compeltly gone now.
alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global: WiFi didn't work at all
alioth_eea_global_images_V12.5.3.0.RKHEUXM_20210706.0000.00_11.0_eea: WiFi worked for 2 minutes
I don't think i have any more roms to test out so maybe i will try a custom rom xd
try with custom roms
Hey guys,
My Pixel 2XL initially had some reboot issues so I decided to root it, and was able to do that successfully with magisk on stock firmware with some modules installed as well. It regained its functionality for the most part but unfortunately the Wifi stopped working (kept searching, could'nt find any network). It would sometimes randomly work on some reboots but whenever it did, the phone would auto-reboot after a while and lose the function again (but would work perfectly otherwise).
So I decided to unroot and factory reset with stock firmware thinking it might be a partition defect, just to see if that fixes it but it didn't. And what's more, the phone has once again returned to bootlooping like before root. Can anyone help me find out the issue here? And if I can manage to root it again and get it working, is there some way to resolve this issue (maybe through a custom kernel)?