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.
Related
I was busy trying to install a mod which didn't go very well. Shouldn't be a big problem, just go back to the recovery and put back the backup.... But there things went wrong....
I reïnstalled the rom, but after that I ended up in a bootloop, but what's even worse is that the recovery also reboots the whole time. For a split second I see the recovery screen but then it reboots again.
So now I can't even get into the recovery. I can get into the bootloader and fastboot, so the solution to this problem but be there somewhere.....
The Factory reset options also doesn't work, because therefore it has to go into the recovery, which reboots... So until now I'm in a sort of never ending circel. Who can help me out of this?
edit:
Found the official RUU here on XDA, so I rebooted the phone into fastboot, and started the RUU update. It's installing now.... fingers crossed...
(doing this update, because maybe in the future it might be helpfull to others).
edit2:
Hmmm getting an error that the phone can't be updated...
edit3:
I had to shut down the phone and reboot, according to the problem solver of the RUU updater... Did that, but the phone rebooted again, after that it tried to enter the recovery again, but this time it actually did. So no recovery reboot. At this moment I'm trying to reinstall by previous made backup.
edit4:
REstoring the backup gave me 1 little error, so I also ran the rom installer again. The phone seems to reboot in a normal way now. Android is booting up again.
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:
Im sure ill get flamed but i have searched and couldnt find an answer.
I have a z2 odexed stock with root. Just updated new firmware via pc companion to 17.1.2.a.0.314.
i downloaded the xposed installer and that went well. Then downloaded the serajrs xposed module so i can get different themes to work, extended power menu etc. everything seemed to install fine however now after rebooting i get this error.
it boots up but stays on the home screen and i can do is keep hitting ok to acknowledge the problem but i cant do anything else.
It was the stock rom so i dont have any custom recovery to go into to restore a nandroid or flash another rom (which i didnt want to do).
All i have is my titanium backup but i cant get past the error, any help would be greatly appreciated
* the error appeared about every 2 seconds so each time i hit ok, i was able to go 1 step each time. Basically was able to get into settings and do a factory reset which managed to do the trick. restored via TB so minimal setup time again. Would still like to know where i went wrong though but grateful didnt brick it lol (yes i can laugh about it now)
For next time: check the FAQ and stuck threads for info on how to temporarily disable Xposed (with or without a recovery).
The FC was likely caused by a module, so you should ask in the module's thread instead.
So I'm not sure what exactly went wrong, because it happened during the night. Today I got up, and my phone had booted into TWRP recovery. When I restart, it always goes back into recovery. No matter what I try, I can't get out of recovery.
I installed the Xposed Framework yesterday, and that worked just fine. It restarted just fine then, and nothing happened. I had a backup I had created before I added the framework, but restoring it doesn't help. I still boot into recovery.
Does anyone have any ideas on how to get out of recovery? I'm sure the backup I flashed works fine, because until I added Xposed I hadn't messed with anything involving root since I first rooted the phone weeks ago. Since that time, I've restarted the phone without any issues. I have no idea what exactly has happened here, since I was asleep when it did. TWRP is still installed, so I'm guessing it wasn't an OTA update that installed without permission.
Ok, I managed to get it booted, and here is what I followed:
http://forum.xda-developers.com/showthread.php?t=2451696
As concise as possible, install the USB drivers from the LG website, install Minimal ADB and Fastboot, and then open it and follow the directions of the previous thread exactly. I used copy/paste for the commands. If you can't find Minimal ADB, here is the link:
http://forum.xda-developers.com/showthread.php?t=2317790
I hope this solves the problem for anyone else who runs into it.
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...