Just flashed the uXylon rom to a brand new N4, using CWM.
The problems I'm getting are:
Browser tries to open and does opening animation and short press vibration, but doesn't open
Navigating/Navigation ring hovers over home button and home button unusable, though vibrates on press
Trying to download GApps or anything else through Goo.im or CWM just doesn't work.
I tried looking through the uXylon official thread and couldn't find any answers, and tried the basics of going through settings and wiping cache & dalvik. None of this did a thing, and the N4 Toolkit by Mark Skippen couldn't even reflash the stock ROM.
Absolutely anything I'm missing would be extremely appreciated.
Related
This is my first post. I wanted to post a reply on a forum where I saw people asking about this problem but because I have not yet posted enough I was unable to post on that forum.
I have a Galaxy S3 I9300, rooted and running Resurrection Remix v3.1.2 with JellyBean 4.1.2 and kernel version 3.0.31-Siyah-1.7rc1+. I love Resurrection Remix and was really disappointed with Samsung's Touchwizz UI, even the JellyBean 4.1.1 version. Today while using the camera I encountered an error. It started when I tried to take a picture and the a popup appeared, "Unfortunately Gallery has stopped". I tapped OK and then tried to reopen the camera but got the following error: "Camera Error: Cannot connect to camera," after which the camera app closes.
I have seen posts about this here: http://forum.xda-developers.com/showthread.php?p=36491568 and I am aware that you can flash a custom camera app: http://forum.xda-developers.com/showthread.php?t=1746611, which I will try. I also saw some people say that upgrading to the latest version of Resurrection Remix fixes the problem, but I don't want to do that because, correct me if I'm wrong, but the ROM is still work in progress and not ready for daily use. I tried clearing just gallery's app data but that did not work for me and I did not want to do a complete data wipe or reflash the ROM.
I found a quick solution if you are also encountering this problem. Power off and boot into recovery mode (hold volume up, home and power buttons until you see the recovery screen). Using the volume up and down button to navigate options and the home button to select options select the following: wipe cache -> yes, wipe cache -> reboot phone now. The phone will reboot and then you will be able to use the camera again.
Hi. This is first time I rooted and changed something to my phone's core system. I bootloaded through Flashtool and got in the newest kernel, ROM and GApps from this thread: http://forum.xda-developers.com/showthread.php?t=1613017 and my baseband is 77 (http://www.mediafire.com/?1oyztnqww22bgek). Things looked fine and my system was working as it should. But soon I was starting to see these bugs:
Screen moving from left to right and back at recovery menu on vol up/down press. Not a big bug though, still possible to work with the menu and read the text.
No lockscreen. Tried all the lockscreen options at settings, but power button still just turns the screen on and off. I can only see the lockscreen right after I reboot my phone and before I enter the PIN, the wheel works as I've set it but then I can't get into the lockscreen anymore.
Strange menu button functionality. Firstly, when I was in the home screen and pressed the menu button, a menu with system settings popped up. Now nothing happens, for both HW and SW buttons. Since the time it worked I was just messing with settings but I'm sure I didn't disable anything like that.
Browser and Google Play not working, Play says RH-01 error, browser just crashes. GMail works.
Tilt not working properly. It did after the fresh install, but now it works only for menus, not for homescreen like it did before. I've tried running a widesecreen-only game but it's being displayed in normal, portrait mode- with errors. Enabling/disabling the tilting didn't help.
And I believe that there are more bugs I didn't mention. I did everything as told in this article http://www.theandroidsoul.com/aokp-xperia-neo/, just with getting the newest links instead of the ones provided. I installed the Hallon version of AOKP and I was running GB 2.3.4 before, if that helps. And like I said- I am doing it for the first time so I am quite new to these things, so firstly sorry if I didn't mention anything important and please describe the steps about how to fix it a little bit more detailed. Thanks!
Hi..
That ROM is legend sometimes ago,and dont have problems like you said.
The step I did was like this :
1. Flash full firmware ICS(.ftf file)with flashtool.
2.Flash kernel
3. Flash ROM
4. Flash Gapps
5. Flash Add-on if any
Enjoy
Sent from my Xperia Neo V
MT15i_4.1.B.0.587_Global.ftf ICS firmware and hallon kernel flashed through Flashtool, then rebooted into system. Then in revocery I wiped cache, dalvik and reseted to factory, installed the newest AOKP ROM, installed GApps, booted into system. My screen is still moving from sides as the screen refreshes in recovery. But after booting, still the same issues persist...
Inside the old recovery,screen dancing is known issue,try Flash other kernel,no harm changing kernel.
Can you provide,Aokp ROM version and kernel you have..
Sent from my Xperia Neo V
AOKP Hallon JB Milestone 1
I tried the CM10.1 and my recovery menu fixed but the bugs weren't fixed, so then I flashed the CM10 and my recovery menu changed again, now with black background and again, fixed animations. But then my device bricked so I flashed again the MT15i_4.1.B.0.587_kernel.ftf.
Couldn't you just send me links to a working combination of kernel-firmware with AOKP? The requirements says I need baseband 72/77, do you have any links or tips for these? I've tried several combinations but just none really worked, now I am on stock laggy JB 4.0.4 and I have no idea what to try now...
Hello,
I would like to apologize in advance if the question was posted before, the description is too brief or anything like that since it is my first post here (although I had searched for similar questions but didn't find any with a proper solution).
After installing CM10.2 with GApps on my Galaxy S2 i9100 (actually, before that I tried Firefox OS which messed up my /data, had to repartition manually and it helped then) I tried to install - and run - Triangle Away, but it froze. Then I made a terrible mistake imo: I rebooted. After that (I mean, after flashing CM again since it didn't work at all) I got an issue with the screen going black after unlocking the phone or apps freezing (running launcher, going to 'system settings' etc; tested on Trebuchet, haven't tried any other launcher so far). I also had a problem (again) with broken datafs, but used patched PIT from somewhere in here, I will edit out that post and paste the url to the thread.
Another thing that should be mentioned is that that status/notification bar is working without any problems when the launcher freezes, and when the screen goes black the 'back' and 'menu' buttons give feedback when pressed (they make the phone vibrate but when I press volume up/down there is no sound).
I've already tried doing wipe data/factory reset, cleaning cache and dalvik and wiping system with flashing CM again but without any progress. Also wanted to check adb logcat, but I cannot get into usb debugging settings (launcher freezes when 'system settings' is pressed).
What could be the solution?
Thank you very much for any answers!
I'm really hoping someone can help me. My back and menu buttons stopped working today, and I'm pretty sure it has to do with a failed Swype install.
I'm running AOKP 4.4.2 (1/25 build) on my VZW Galaxy S4 (jfltevzw). The phone has been running great, but I can't stand the new kitkat keyboard. I decided to try Swype again, after dumping it a few years back.
I installed the free Swype (which obnoxiously comes with Dragon also), but I couldn't get past step two (select default keyboard). The wizard just wouldn't progress further. I went into the menu to try switch manually, but I trying to type would just bring up the installer again. I tried switching back to the stock keyboard via Settings>Language, but nothing would happen when I tried to type. The only thing I could do was reboot.
When I booted back up, the menu and back buttons would no longer work. I tried clearing dalvik and cache, resetting permissions, reinstalling AOKP and Gapps, and so on and so forth. I'm backing everything up to do a hard wipe, but I'm not holding my breath.
Has anyone seen this problem before? Is it failing during the Swype install just coincidence? I can't see how it could be....
After a hard-reset / factory wipe, everything is working again.
I will not be installing Swype on AOKP/KitKat again, hehe.
Hi all, hoping to get some help. I rooted my phone the other week and was using viperrom. I had no problems whatsoever, no glitches that I could remember. That is, until I decided to trade my m8 with a friends Note 3. I factory reset it and give it to her, I left the viperrom on because she didn't mind but then the glitches started to happen. The onscreen bottom 3 buttons disappeared for her (home, back,etc.), So I reset it again but the problem persists. I searched for an at&t stock rom and sideloaded that after master resetting, wiping the dalvik cache and all that... now a different problem popped up. It hangs at the HTC logo for what seems like forever, but then I noticed the volume up and down make a noise as if the phone is loaded up. I pressed the power button a few times and eventually the screen turned on and I could see the home screen. This happens every time I restart the phone and I have tried reinstalling the stock rom a few times. I am now in the process of trying a different stock rom.. the first was odexed and this new one is deodexed, I dont know if that makes a difference in my situation but does anyone know what could be causing this? Any help would be appreciated.
Nvm, after a few more master resets it seems to have sorted itself out... not sure what it was but its gone now.
If its the latest version of Viper, based on 2.22 software, you need to update the firmware package, otherwise the long boot times will continue.
Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592