Hello guys, I was wondering if you could help me. I have a cel phone LG-H221 and I had to flash it several times. The problem started a couple of months ago... The first time, it showed me continually this error: "unfortunately, the process com.android.systemui has stopped". I did a factory reset many times but it never worked out.
So I decided to flash it using flashtools 2014 and the original firmware (H221AR10d_00_0219.kdz) but it kept showing me errors. Since then, I flashed it again twice. Now it showed me a warning because the settings option has stopped and google apps too, I did a factory reset but now it shows me the blue screen with the language setting and it's frozen.
I don't know what to do, I bought it 6 months ago and I lost the warranty, where I live (Argentina) it's one of the latest devices by LG.
So I was wondering... is there any rom (cyanogenmod, omnirom, etc) which is compatible with my device? It's not rooted so I would need to that first. Thank you all very much in advance for any tip or suggestion!
Related
Hey everyone.
So, this started happening to my Nexus (stock, unrooted, locked) after the 5.0.1 OTA update: youtube.com/watch?v=BolnMQx3LGs
It started in the first days of January, after receiving the 5.0.1. update. The phone randomly restarts and gets in a boot loop. For the last month it happened once or twice every week, often making the phone useless for several hours. I posted on the Nexus help forums, noticed a lot of people with the same problem as me, but no solutions.
Today I had enough and sideloaded Kitkat again. So far so good, but I don't want to celebrate just yet.
Has this happened to anyone here. Is there a reason for this to be happening or a solution?
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
thionylx said:
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
Click to expand...
Click to collapse
Sounds like a stuck power button to me.
Sent from my Nexus 5 using XDA Free mobile app
Alright, this is a long story.
I own an LGMS500 from MetroPCS (or the LD500 Tmobile version).
A year back I rooted the phone, but a couple of months ago it started to act up Giving me the message "unfortunately, the process com.android.phone has stopped." at first a restart would fix it but a few days after it got to the point where I couldn't use it. So I set out to fix it.
I knew I needed to flash it back to stock ROM since a factory reset and a hard factory reset didn't do anything. But for some reason I decided that flashing a custom ROM was a better Idea. I ended up flashing the xperia ROM and it soft bricked it ( It turned on and booted but wouldn't let me past a black screen, yet I could lower the status bar).
Then I tried to flash the stock ROM or the "MS50010e_03.zip" to load with KDZ. from:
http://androidforums.com/threads/metropcs-unbrick-kdz-for-metropcs-updated-11-13-2013.788365/
But every time I tried it it came back with a parameter error, I changed many things with no avail, Then I figured that since the phone had a tmobile version I flashed the tmobile stock ROM onto the phone and it worked, even let me use data. But after a few days it stopped letting me use data, with a "Service Disabled message on the status bar where it should've shown the mobile carrier. When I went to check my phones mobile data status I noticed that My IMEI # was unknown.
After some research I came to the conclusion that something was wrong with my EFS folder since that's where all that information resides.
At the moment the phone restarts after about 3 minutes of usage, I should also mention that I rooted the phone after the tmobile stock ROM install because of what this thread suggested I should do.
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
Basically I need to know if my conclusions are correct and what kind of steps I should take to recover the phone if possible.
A
FIXED it
I just loaded the MS50012b_00.kdz from:
android creations on the weebly site (sorry I can't post links yet)
This is the only image that worked the first time. After that my phone worked normally, accessed the mobile network correctly and the crashing stopped.
I even installed the xperia ROM that is on that page. Everything is running smoothly now.
Hey there!
Sorry for creating a pull for asking help first, but I've been messing around the forum and Google with no results.
The thing is: I have a Motola Moto G 2013, it works pretty fine. Some time ago I'd like to try CM 12.0, and everything went okay. I didn't need to install the GApps cause, don't know why, it already has Play Store and Google Services, so, no problem.
Some days ago my phone started to work PRETTY bad, and reading in the web found that CM 12.1 were released, so i thought "lets give it a try"
CM 12.1 installed well, but without any GApp, so started to search the GApps packages. Tried with many of them, Pico, Nano, Stock, from april of this year, may of thies year, even from july this year! But none of them worked. When Android starts (after GApps install) appears a windows that says that a factory reset is needed. After that, starts the nightmare. Constantly, really constantly, appears two windows "Play Store has stopped" and "com.google.process.gapps has stopped" and after that, like pressing the "Ok" button10 or 15 times, almost every time, it gets on black and only can power off and restart,
As I could, went to settings > all > and cleaned and stopped every google service. When I made that the device perdormance goes pretty much better, but when try to acces mi gmail o opening play store, again, the same.
I thought that changing the recovery would do some change effect. Tried with CWM (the one i had from before), Philz Touch and now the latest version of TWRP (the one that looks like Material Design), with no effects. And finally, tried with other ROM. I downloaded AOSP http://forum.xda-developers.com/moto-g/development/rom-android-source-project-t3060704 but again, gapps error. Also tried with blisspop, but couldn't install it, it was like 4 a.m. and my mood wasn't good for keep trying.
Before you ask, yes, I made every goddamn wipe before and after the install (after only dalvik and cache partition)
It's like no matter what ROM, no matter what version of GApps, the doesn't work. I've been like this from two days ago, and really, the different options are starting to vanish.
Sorry again for creating a topic for this, but is this, or throwing the PC and mobile above the window.
And, also, sorry about my english, I'm from Argentina.
If you need more details, like Recovery versions, GApps versions, screens, anything, ask 4 it.
Cheers and thanks!
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.
Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks