A couple of years ago, I'd fruitlessly rooted and installed TWRP, and all I remember for the end of it was that I went back into the stock launcher using the LG User Support Tool.
Earlier today, I thought of doing it again, found what seemed to be a reasonable guide on it (little did about the 10/20/a/b/etc things), followed it.
It turns out I was already rooted. So I installed TWRP, worked pretty well, no problems. Most of what I really wanted was to get rid of the stupid menu button and replace it with the multitasking button for almost every other device. I know CM lets you do that from doing it with previous devices, so I grabbed the most recent one just to test it.
While going through the welcome screen, it wouldn't properly connect to any Wi-Fi networks. Entering the correct password just changed the status to "saved", and it wouldn't connect.
I flashed another ROM, and the same issue persisted.
Could someone please help me to figure out what I did wrong? I'd really appreciate it.
Related
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
I'm running CM 6.1.1 Stable on my G2 (just a couple weeks old) and I've noticed that my home button doesn't work sometimes. It works about 95% of the time, but then it will do the occasional hiccup where nothing happens. If I touch it a few more times it will eventually start working again. Not sure what it is, but I read in another thread here that it could have something to do with how the CM ROM is configured for capacitive touchscreen sensitivity. And I believe I read that this has only been reported in CM and not other ROMs.
dutman said:
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Does it completely not working??, delayed maybe??
Sent from my HTC Vision using XDA App
Had this issue yesterday. I did a factory wipe from Clockwork and reflashed CM. Fixed it.
even iam facing the problem, but i guess mine is worst as the all(4) softkeys doesn't respond, but when i press it, i receive the feedback i.e it vibrates.
2nd issue: my physical keyboard layout is pretty much messed up, the symbol key which i press on my keyboard doesn't display the exact symbol
it would be kind if someone offer some solution for this
Rom: CM 6.1.1 (even tried nightly build #85)
Build: HK
P.S: i never had those problems in the stock rom
I'm having the same problem with CM6.1.1. I noticed it after installing Twidroyd app. I couldn't exit it via the home button...had to back all the way out. Uninstalled and still having the problem. Doesn't seem to be working at all now.
I had this sort of problem with my G1, I flashed the BiffMod ROM and some day, the phone just randomly did a factory reset, the background is set to how it was when I first flashed it and the home screen was back to normal like how it was when I first flashed it. My home button would not work, when I pushed the end call button to put the phone in sleep mode, it would turn off but if I were to press it again,the screen would turn on but it didn't go to the lock screen it just turned on. To fix it I went into recovery and wiped all five(I'm using Amon_Ra's recovery on it) then I booted back up and my home button worked again and when I put the phone to sleep, it turned back on like normal with the lock screen. That has happened a few times, some times when I did the wipe, every thing would start working again and my home screen still had everything placed where it is suppose to be. You could try to wipe everything, but I can't guaranty it because I don't even have my G2 yet so this has never happened to me on a G2.
i wiped everything data / cache ,flashed GingerVillain 1.4 , the softkeys won't work even in this rom, the only place where softkeys work is HTC's Stock rom. iam just wondering is it due to my build, as its Hong Kong build, so there is a possibility that the keymap for softkeys are different?
Update: Fixed! http://forum.xda-developers.com/showpost.php?p=9353194&postcount=1
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 was trying to activate the AOSP lockscreen on the HTC ONE M8 on Verizon. I succeeded in that, but when I read through the walkthrough further it said there was a way to keep the Touch Twice to Wake and fast charge features. So I continued on to flash the Bulletproof Kernel. I, sadly, didn't pay attention when it said it worked on everything except the Verizon version. Now, I lost my soft buttons and have to reboot anytime I want to switch applications. I've found similar problems, but they were unique to settings found in Cyanogen and other roms. I'm mostly completely stock. It's been suggested that I try flashing Cyanogen or something, but I'd really like to keep the camera and IR functionality.
Solutions I've tried.
Rebooting 20+ times. Didn't work.
Draining the battery, and recharging, and rebooting. Didn't work.
I found a stock kernel and flashed that. Didn't work.
Loaded the backup I had from when I installed CWR. Didn't Work.
Wiped all cache and factory reset. Didn't work.
I'm now out of idea's and need some help. Anything guidance in the right direction would be greatly appreciated.
This was the how-to I was following: htc-one.wonderhowto.com/how-to/activate-hidden-aosp-lock-screen-your-htc-one-m8-0154651/
EDIT: I just put a ROM on it. Fixed my problems for now. I still have no idea what happened though.
I've searched around for anything related to this issue and havent been able to find any information so here I am.
I have a galaxy s3 i747 that is rooted and (until recently) was running an unnoficial version of cm12 with android version 5.1. I used all the correct files for my phone model (I'm not new to rooting or flashing) and flashed perfectly. Booted up great and ran really smooth for about 2 or 3 weeks. One day I was out and I tried to make a call multiple times and the phone wouldn't dial out so I thought "okay reboot and it'll work fine" except when I hit soft reboot this time it started to reboot but never came back on...
In the midst of being out and about I waited to get home to really look at it and, you guessed it, the phone is bricked. Somehow it bricked itself after I tried to reboot it. I don't understand how it could have done that but it did. It might be worth mentioning that I've bricked this phone before and miraculously brought it back to life and its doing the exact same thing as when I bricked it before. Except now when I try the same unbrick method (debrick image on SD card) I get nothing. So, does anyone have any information on this? I thought that maybe the phone updated itself to 4.4 last time I unrooted and that was why but I don't think that happened. If you need more information I'm happy to provide, I just really want to figure out how it got bricked and if there is any way to fix it. Thank you in advance
DON'T PANIC!
I own two Verizon note 4 devices. You could call me a flash-a-holic. I love this stuff and really love my Note 4. It's the best phone I've ever seen with great features that many newer ones do not have. However, you already know that ... so I'll dispense with the speech. Before any of you think I'm new to this stuff, I should say I've been flashing devices since 2005 with my old Windows Mobile devices. I also manage a total of seven Note 4 devices from Verizon, five of which are on my own plan. My neighbor has the other two because they loved mine so much.
Recently, I've been playing around with some of the International ROMS, particularly the Note 7 and S8 ports in the Snapdragon section. I really love those for the scrolling snapshots and S8 launcher (even though I use Nova on my daily device). However, after flashing so many of those and having to use a variety of data fixes to get 4G working, I seemed to have messed up my device. I was having really odd issues, like going from 1X, 3G, 4G, to disabled for several minutes before it would settle and finally connect. I also had issues with text messaging. It would work fine, for a while. Then it stopped receiving messages, but I could still send. I messed with APN settings, which didn't help. I flashed more data fixes and APN fixes I found. Nothing really fixed it. So I figured it was the SIM card. I went to Verizon and admitted it was a custom ROM, but he could see that obviously. He gave me a new SIM card, yet I still had the same trouble. After a reboot, it wouldn't settle on a connection for about three minutes, sometimes more. I still was unable to receive text messages (including MMS) on that device. Even a Nandroid backup did not fix the problem.
Here's what I did to fix it.
I decided it was probably best for me to restore back to stock and go through the rooting process again. Ugh... but I love my phones. I'd do anything to keep them going. Instead of using ODIN to restore back to the original stock, I used the Safe Upgrade for 6.0.1 found below. It's been fixed so it does not lock the bootloader again, but restores everything else to stock, but you get to keep TWRP recovery.
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
I let it boot and go through the process (without signing into anything). Immediately, I realized that my data/4G problems went away. It never flickered even once. I let it sit for 15 minutes once it finished it's initial setup and rebooted back into RECOVERY to flash Kevin's Flashpoint kernel. That gave me root again with Magisk. After a full reboot, I then went into DOWNLOAD MODE and flashed the newest modem (CQI2) using ODIN. Then it was time to settle on a ROM for my use. This time I decided to go back to another International ROM and it appears I'm good to go. Just remember, the Verizon Voicemail app won't be included and usually won't work with an International ROM. I've tried and only was able to get it to work on one of them. It runs, but just will not connect to Verizon properly to access your voicemail. I'd love to find a real fix for that.
Ah... it's good to be working again. Now I can use Titanium Backup to restore my apps and data. BUT I DO NOT RECOMMEND RESTORING SYSTEM DATA. It can only cause problems.
Just a few suggestions for anyone having issues. ALWAYS keep several files on your PC/Device for this type of recovery.
1. Keep the Safe Upgrade to Marshmallow 6.0.1. image. It will be your lifesaver in case something goes wrong.
2. Keep a good working kernel (of your choosing). I prefer @kevintm78 Flashpoint Kernel. It restores Magisk v14 and almost always passes SafetyNet. I keep both stock and port versions on hand (just in case).
3. Keep a good ROM or two (also of your choosing) in order to reinstall a ROM you prefer to use.
4. Keep a working data fix to flash if you're using one of the ported ROMs. Not all are created equal, nor the same at all. Not all of them work. I recommend the Aurora N7 Data fix (Alpha 5 for my N910V): https://forum.xda-developers.com/showpost.php?p=69066109&postcount=2681
5. Keep the latest version of ODIN around. You'll need it from time to time.
Last but not least ... try this fix before you start blowing up the forums with questions and complaints about problems you have. I've found that most of the odd problems people experience are caused by using Titanium Backup to restore system settings created from another ROM, or trying to add different mods, which cause issues. Don't blame the developer for issues that you have that no one else has reported. Most likely, it has nothing to do with their software. It's probably something you installed or restored from a previous backup. You can let those old text messages and phone history go.
If you use Titanium Backup, only store system data IF you are using the exact same ROM as before. Otherwise you will experience problems.
I was sure my Note 4 was ready for disposal after the cellular issues I was experiencing. However I'm happy to report it's good as gold now. I'm not sure how much longer these devices will work for us, but I'll never freely get rid of mine. Besides, who else can fix the TV in the bar when the bartender loses the remote? Not very many devices these days have IR Blasters installed. I've used mine at least a hundred times for that very reason. But that's only one reason for loving this device. I could go on, but you already know that Samsung made the best device with the Note 4 models.
I hope this info helps anyone having problems after flashing so many different ROMs. I know, it's hard to settle on only one. Happy flashing and remember ... DON'T PANIC!