So I downloaded the rooted and busybox 4.4.1 update package, installed it and flashed the radio as well. Everything was fine except ART would not enable after rebooting.
Ive come accustomed to ART so in desperation I did a factory reset but STILL ART will not enable what gives? I have ONLY the stock apps installed.
Happened to me too. I have no idea on how to fix it. Also, while on Franco's latest, after I installed 4.4.2 and tried to re-enabled ART, my nexus 5 just went into a bootloop. Good thing I backed up earlier today.
ART is broken because Google used GCC 4.8 to compile, which causes the optimization process to crash on boot.
Any way around it? Several people have zero issues.
4.4.2 update fixed it!!!
Related
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.
Seems I inadvertently killed my working CM11 opo with 9/30 Nightly
Factory Reset and wiped all data via twrp 2.8.0.1
Installed Nightly, Gapps, Gapps remover, franco r22 and cm11s app pack via USB-OTG
wiped dalvik/cache
reboot to "Unfortunately, the process android systemui has stopped working" > hit ok > infinite repeat
tried to revert to 9/25 and even the M9 snapshot to the same issue
I have a nandroid of when i first got the phone with cm11s on it but no efs backup.
I was using franco r20-updated to r21 just yesterday, Nightly 9/25 just fine with a few issues with certain apps. Figured waiting for a few more days in between nightlies would help with those issues.
Anyone got any suggestions as to what I can do to resolve this? Out of a phone at the moment so in a tough spot.
Factory wipe. Only flash CM11 nightly, flash each zip one by one. One of them is causing your phone to constantly fc.
Seems issue in last CM nightly 0930... Flash 0928 and wait for fix. Affected more (maybe all) devices.
Happened to mine as well. Though I still can't use the cm boot.img past 9/19 either lol
I flashed back 29 nightly and all works fine.
Same issue for me updating to the 09/30 nightly!
@zephiK 9/29 is offline apparently lol
9/28 seems to work (with no other zips done including gapps)
Samsung GS3 - Pulled battery to get control - boot to TWRP and installed 9/28 nightly. All is well. :good:
S5 30/09 can confirm SystemUI crash. On 28/9 atm and fully works.
Autobuilder placed bad commit and built it for all devices.
My Z3 D6603 has started to acting up now and then.
Just lastnight the phone said that Camera failed to start and once i did a reboot the phone ended upp in a bootloop, bootsound crashes.
Entered TWRP and realized my system/bin folder was empty.
So my question is, has anyone any clue whats causing this and how can i solve it?
I was on KK D6603-23.0.1.A.5.77 which worked fine.
I recently installed Android 5 with unlocked bootloader.
So this is what im runing.
Rom: Flashable_D6603_23.1.A.0.690_Customized_NCB_pre_rooted.zip
Kernel: Advanced_stock_kernel_Z3_Lollipop_23.2.A.0.278.zip
Launcher: 5-5_home.apk (installed in System/Priv-Apps)
This all started when i had the same ROM and Kernel with xposed framework installed i used xposedinstaller_3.0-alpha2.apk with xposed-arm-20150308.zip. well atleast i thought that was the issue.
I solved everything by removing xposed framework manualy in recovery and after that simply cleaning cache and dalvike but that solves everything for the moment.
After that i got the same issue even without xposed framework.
I dont know when this will happen again but last time it was 3 days ago and i had not installed anything new.
Im starting to suspect that the issue is realted to the launcher but again im not sure.
http://forum.xda-developers.com/cro...ll-xperia-home-8-0-0-7-lollipop-roms-t3062623
So has anyone any idea on whats wrong and how i fix it or should i simply just start all over and install the flashable rom and just let it be without kernel etc.
Zeggi said:
My Z3 D6603 has started to acting up now and then.
Just lastnight the phone said that Camera failed to start and once i did a reboot the phone ended upp in a bootloop, bootsound crashes.
Entered TWRP and realized my system/bin folder was empty.
So my question is, has anyone any clue whats causing this and how can i solve it?
I was on KK D6603-23.0.1.A.5.77 which worked fine.
I recently installed Android 5 with unlocked bootloader.
So this is what im runing.
Rom: Flashable_D6603_23.1.A.0.690_Customized_NCB_pre_rooted.zip
Kernel: Advanced_stock_kernel_Z3_Lollipop_23.2.A.0.278.zip
Launcher: 5-5_home.apk (installed in System/Priv-Apps)
This all started when i had the same ROM and Kernel with xposed framework installed i used xposedinstaller_3.0-alpha2.apk with xposed-arm-20150308.zip. well atleast i thought that was the issue.
I solved everything by removing xposed framework manualy in recovery and after that simply cleaning cache and dalvike but that solves everything for the moment.
After that i got the same issue even without xposed framework.
I dont know when this will happen again but last time it was 3 days ago and i had not installed anything new.
Im starting to suspect that the issue is realted to the launcher but again im not sure.
http://forum.xda-developers.com/cro...ll-xperia-home-8-0-0-7-lollipop-roms-t3062623
So has anyone any idea on whats wrong and how i fix it or should i simply just start all over and install the flashable rom and just let it be without kernel etc.
Click to expand...
Click to collapse
Camera apk failed to start and after reboot my system/bin folder was empty again..
Its either my kernel or home apk. I flashed kernel for x.690 version instead which is the same as ROM hopefully its related to that.
Hi Guys
After one of the custom 5.1 roms crashed and left me without the phone, I have decided that I will go live with Marshmallow.
I have installed the original stock 6.0 MRA58K which after booting quickly went into MRA58N with OTA update.
Once I have realised how many things I am missing in my phone, due to using the stock ROM, I was looking for a perfect solution and decided that I will no longer be flashing custom ROMs, but use XPOSED as a framework with additional modules.
I have installed the elementalx kernel and added the correct XPOSED framework.
Everything was working fine until yesterday, where I have received notification about OTA update to 6.0.1.
First I thought that I don't really care about emojis, however I do like the option of "Do not disturb until next alarm".
I know that I can achieved by some additional modules to the xposed, however the OTA update is quite annoying.
Because I was on TWRP as a recovery, I have also installed the BusyBox and SimpleRecoverySwitch hoping that this will resolve the issue. Quickly reflashed stock recovery (don't know why, but every time when I was using fastboot to flash recovery with stock recovery.img, TWRP was still there) and found that I still can't use OTA update to 6.0.1. due to error:
"app_process 32 has unexpected contents".
After googling I have found that this is because I have xposed up and running.
Googled than for "unistalling" xposed and found plenty of topics, however none of them have provided me clear answers, especially to the question of "how to uninstall xposed". I have not found any original.img, so I suppose xposed installer have not created any backup, also when I will open xposed Installer - options to "uninstall xposed" are greyed out.
So my question would be - how can I easily remove xposed (temporary) without loosing data/restarting fully the phone, because after 5 days of flashing/reflashing/factory resets I am slowly tired from setting up personal configuration on my phone (even when on Marshmallow is much more easier than on lollipop 5.1).
If this is not possible, how I could remove OTA update from not only notifying me all the time, but also not restarting the phone (wakelock?)
Once you root the phone, you will not be able to upgrade via OTA. Your choices are to follow the instructions on this thread or to completely go back to stock without root and do the OTA.