Hi guys,
After (finally) unlocking my bootloader, installing CWM and rooting my One X (3.14.401.31) I'm now left with a weird problem. It's probably me, not understanding something, but maybe somebody can help me..
Okay, so I haven't flashed a custom ROM because stock is working just fine for me, but I did want to make some changes..
I've tried flashing the following MOD: [MOD][03 Jan] Less Notifications | Final | JB ROMs based on 3.14.401.31
It offers a feature to disable HTC SmartSync (which should actually work on JB)
Flashing the zip from CWM works like a charm, and after rebooting I get a pop-up saying it's updating an app.
After updating however, nothing has changed. I've looked at the files in /system/app and /system/framework which should have been changed by the mod, but the modified date hasn't changed.
What's going on?
You can still see the notification? Try flashing again.
Tried it a couple of times, but no effect.. I can still see the notification, and my power menu isn't showing the extra options either..
Related
Hi there
I think I destroyed my CPU or something ... I used a custom kernel which does OC and UV and it worked without any glitches for about 8 hours.
Then it froze and now I cannot boot any rom.
If there is user data it boots to a frozen lockscreen.
If I do a factory reset it says that the Process system is not responding...
Anybody got an idea?
I just flashed the official SLCD RUU and now it works again ...
I can only run official ROMs
If I root and flash a new one, the same error persists!
anybody any idea?
I cannot really tell HTC to replace my phone, it works with their froyo version :S
but I don't like Sense and now I'm stuck using it ... hate that -.-
Well you rooted with an RC of unrevoked. Could as well have something to do with that. Have you tried custom sense roms? Just to see if they work. Else, i would try the downgrade-to-hboot-0.83-method.. just practice the screenless method with the screen turned on, i managed to do iy in one attempt (H)
I recently RUU'd from ViperX to my CID's 2.17 then upgraded via OTA to 1.36 hboot and the Jellybean Sense 4+ update. My cid is 044. I then rerooted, full wiped and flashed Insert Coin 13. I soon after noticed a problem that I get on every reboot. It will reboot up till the part where it starts to load Sense and then it pops up a message along the lines of htcdialer has stopped and then I get a black screen (I can only see the top status bar) and I'm unable to do anything with my phone from there. I'm able to flash any of the JB custom ROMs and use them fine until I reboot. I've tried this with IC 13 and Maximus 8.5 so far, and I have performed a superwipe as well as a full wipe via their Aroma installers. I was going to try ARHD 15 next but the download times on both mirrors are just outrageous. Has anyone experienced anything similar to this or have any idea what I could do to fix it? Thanks a lot in advance.
Hi there, since I'm not obligated to post replays under development thread here's the place to do it.
I just installed newest version of LiteROM (used 0.7 previously) and I found some unpleasant behaviors.
First of all - I couldn't get wifi connection to work. Password was ok but it continuously tried to authenticate or get proper ip. Re-flashing with stock rooted rom, then gettin literom over it worked like a charm.
But, after installing newest LiteRom I'm getting message every time I reboot device: ... android.process.acore has stopped working.
Also, when trying to set lockscreen wallpaper it gets me a message: ... TwWallpaperChooser has stopped.
So, is there any proper fix to get things right or maybe I'm doing it wrong?
(I did full wipe before all installations but it does not resolve issues)
First, you might try downloading the ROM again(preferably from a pc) to see if maybe the download was bad.
Sent from my jelly monster.
Already did. Then reflash with FULL wipe - nothing. As long as sim card isn't on, there's no issue with .acore (it happens even when switching airplane mode on/off). I also tried to wipe contact and contact manager data but with no good solution.
Another thing is - I've tried IcePop rom and it worked fine. IMHO, there's something in literom that causes such bad behavior.
I would be grateful for helping me resolve that :good:
Hmmmm. The only problem when i flashed literom is if i didnt install the stock gallery then it seemed to crash the lockscreen wallpaper when trying to choose a wallpaper from settings and did not give me and option in quickpic.
Sent from my jelly monster.
Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.