[Q] Very odd behavior after rooting/flashing recovery...help! - Verizon LG G2

Ok so this is everything I have done... Got a new VS980, used OTA to update to 4.4.2 andriod, 27a. Then I decided I wanted to root. I used Stumproot with brute force option and that was successful. I thought I could flash TWRP with Flashify and that obviously didn't work. I then realized I needed to use Autorec. I downloaded and installed that and successfully flashed TWRP. Afterwards I noticed my battery was draining super fast, and I still don't know how rooting and flashing TWRP have anything to do with that, but it has somehow. I thought flashing a new ROM would fix it I downloaded the newest Cloudyg2 and the bootstack that goes with it. Flashing it worked but I kept getting a "Unfortunately the process com.android.phone has stopped".. I cleared data and cache on the Phone process and force closed Sim card process and the error stopped but I couldn't send any MMS, it said invalid address no matter what phone number I tried... But that wasn't the main issue, the battery drain was still present. I rebooted in recovery to see if it would drain in recovery, while not doing anything and it was still draining, almost 1% every 10 minutes... I am lost and can't find any similar posts/threads on this anywhere... Somebody please help! Thanks in advance for any feedback...

Related

Reset Issue

Hi guys I wanted to go ahead and reload a different ROM. I had purehero 2.1 MOC (maps-oced) but I heard that the nonclocked version has better stability with wi-fi. I went ahead and tried to downgrade the rom without wiping and everything booted up fine. However wi-fi tethering was still not working I kept getting an error about unable to start wifi tethering etc. I went ahead and tried many roms (pure hero/alysious) all that wouldn't require wipe. I still kept getting same error. I went ahead and went to recovery I did a factory wipe/loaded rom and it just stays on the nexus X cross as if it's trying to boot but it doesn't it just keeps recyling over and over again. I went back to recovery and wiped data/factory and also dalvik cache ( i have a2sd enabled) then retried loading rom and same thing. I'm at the moment of wiping all mentioned plus eXt2 and reloading rom AGAIn. I hope this time it boots up.
Will something in my SD card possibly have my phone acting up the way it is? If so what solutions do u guys suggest? I hope after doing the last step I mentioned I can FINALLY log into my phone. At the moment i'm unable to do so. My aim name is crown510. If any of u can assist me I would appreciate it. Thank you!

HELP: com.android.systemui in FC loop

I have ViperOne 4.2 rom installed with latest fw, radio and Elemental X kernel 10.10.1. I have this setup now for about 2 weeks or so and have not changed anything on my phone drastically or have installed any new software etc.
Today all of a sudden my phone rebooted and once it did i am greeted with the message that Unfortunately, the process com.android.systemui has stopped. When i click ok the UI seems to reboot itself quickly but then i get the same error message again and again after repeating these steps.
I have restarted my phone several times, even booted into safe mode only yet the same error keeps comming up again and again.
Can anybody advise what the problem could be or what to do to make it stop?
Worst case scenario i can restore from a Nandroid backup but i would prefer not atm as i'd rather know what is causing this problem.
Any help would be appriciated!
Great. I tried to delete the cache in recovery just as a try. When i rebooted i was greeted by stockish type of welcome screen with setup your phone info. So i went back to recovery to try restore the nandroid backup which is on my phone. After some time TWRP sais "Restore failed".... never had that before either.... wonderfull...
So this day just keeps getting weirder and weirder. While trying to somehow restore my nandroid (which still does not work btw) when i go to power off my phone via TWRP it sais no SU is installed and it seems i do not have root permissions.
Which is very odd because i am S-OFF, SuperCID for quite some time now....
What the hell is going on today? Meh...
I had the FC in com.android.systemui too, but so far i did`t have the issue with restoring. Would be also thankful for further advise...
Anybody an Idea?
bonzai80 said:
I had the FC in com.android.systemui too, but so far i did`t have the issue with restoring. Would be also thankful for further advise...
Anybody an Idea?
Click to expand...
Click to collapse
if you're using a custom rom try a 'dirty' flash (flash without wiping). That fixes most of these types of FCs without losing any data.
I am using the Viper 4.3 ROM, was choosing to NOT install some of the Apps that would be included on a regular install - maybe this causes the FC. I try without removing these applications. Thanks for your advise! :good:

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying:

IMEI Unknown

Ok guys. Need some help, installed Repulsa's Rom. Once booted I believe I had service but I kept getting errors about services stopped working. So done full wipe again but second time I choosed to update bootloader act during install and also enabled SU instead of magisk. Booted fine with no errors, but also no service/imei. I done an efs/baseband backup just before. Restored that and it didn't work. I have also done a full restore from a stock backup I had. Still getting no service here.... Anybody out there able to help?
Fixed it guys. Just updated boot loader again. Think something went wrong the first time.

Recovery mode and Root issues after stock flash

Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..

Categories

Resources