Hi I need help with my at&t LG g3 with Lollipop 5.1 I just rooted the device then downloaded the expose framework but then realized I needed a custom recovery to make it work so then I tried that next but failed now my phone is stuck on the at&t logo (bootloop) how can I get it working again maybe getting it back to stock recovery
aldo.arredondo said:
Hi I need help with my at&t LG g3 with Lollipop 5.1 I just rooted the device then downloaded the expose framework but then realized I needed a custom recovery to make it work so then I tried that next but failed now my phone is stuck on the at&t logo (bootloop) how can I get it working again maybe getting it back to stock recovery
Click to expand...
Click to collapse
There might be a way to get back stock recovery but if not just go back to stock.
Sent from my iPhone using Tapatalk
Related
Hey folks,
i got a serious issue with my MotoG...
I tried to install/flash the GPe Rom (Android 4.4.2) here from xda and it fully worked. After the install process i received the OTA Update to Android 4.4.4 and installed it with the stock recovery. The result was a working up to date GPe rom where i deleted some system apps. I rebooted the phone and got stuck at the boot logo from Google with the unlocked symbol. A full wipe and reflash of the GPe Rom didn't fixed the problem. The phone sticks at the boot logo. After this i tried to reflash the Motorola Rom which didnt fixed it either....
My guess is that the OTA Update from GPe changed something which can't be fixed with older firmware flashes...!?
After a couple of hours of work i pushed via adb my CWM backup to the internal storage and restored it. My Moto booted and i was finally able to get it back to run the stockrom.
Then i saw something weird... The google logo with the unlock symbol stays and then the motorola boot logo appears and im not able to flash via fastboot other rom
Anyone experience similar or the same problem after restore from GPe 4.4.4 to lower Android version 4.4.2?
Thanks in advance for help and tipps
Flamey
many peopla have bricked phones right now
we have to wait for fastboot images of 444 or gpe 444
there are none yet
Yeah I'm luckily half bricked..
Can't flash stock..
Stuck with CM based ROMs..
I go either side and my phone dies..
Sent from my Moto G using XDA Premium 4 mobile app
http://forum.xda-developers.com/moto-g/general/howto-fix-stuck-boot-downgrading-t2808098
you can use that
lol sorry, you fixed the issue by your own guide, lol
Okay so basically, today I got the request of installing the Android 4.4.4 kitkat update on my rooted moto g. I press yes and that my phone shut off as it's meant to be. Then this is when the problem occurs; when it turns back on it goes to TWRP and it goes the the normal page of TWRP. I reboot my phone to try again and the same thing happens. Can someone help me to get rid of this problem and to install the Android 4.4.4 kitkat update on my rooted moto g? Will be much appreciated :good:
P.S: The Android update was from Google.
Installing an OTA on a Rooted Phone with Custom Recovery is not advisable!
Sent from my XT1052 using XDA Premium 4 mobile app
I tried too and the installation stops and comes out an error with /system/framework/core.odex.
I tried to flash again stock recovery but it persists..
Sent from my XT1032 using XDA Premium 4 mobile app
Azonto said:
Okay so basically, today I got the request of installing the Android 4.4.4 kitkat update on my rooted moto g. I press yes and that my phone shut off as it's meant to be. Then this is when the problem occurs; when it turns back on it goes to TWRP and it goes the the normal page of TWRP. I reboot my phone to try again and the same thing happens. Can someone help me to get rid of this problem and to install the Android 4.4.4 kitkat update on my rooted moto g? Will be much appreciated :good:
P.S: The Android update was from Google.
Click to expand...
Click to collapse
Same here. Had to flash stock recovery from bootloader (fastboot flash recovery recovery.img) and then reboot, and let the phone reboot and apply the system update.
All is good, and it kept root... No need to have the system breaking TWRP on there.
I get an error while updating, it just says ''error''. I have stock kernel, stock recovery, unrooted... Nothing seems to work, but I think the problem might be that I have a custom boot animation. Is there any way to flash the 4.4.2 stock UK rom?
Use the search guys: http://forum.xda-developers.com/moto-g/help/how-update-rooted-moto-g-to-4-4-4-t2823106
CrazyPeter said:
Same here. Had to flash stock recovery from bootloader (fastboot flash recovery recovery.img) and then reboot, and let the phone reboot and apply the system update.
All is good, and it kept root... No need to have the system breaking TWRP on there.
Click to expand...
Click to collapse
Do you have a moto g ? I did a factory reset which meant that the update wouldn''t keep shutting down my phone and then it would go to TWRP. So how do I install the 4.4.4 update?
Hi,
I wonder if anyone could offer me a little assistance please ? I have a UK Tesco Moto G 16GB (2013) that I have successfully unlocked the bootloader and rooted and CWM recovery installed. Currently, it's running 4.4.4 Kitkat. I gave up with the OTA update as I was getting the 'preflash validation failed' message. More recently, I have tried following the guide on here to flash the XT1032_GPE_5.1_Optimized_v1.1.zip file using CWM. However, this resulted in what I believe is termed a bootloop - i.e. the coloured dots animation just never stopped - I waited half an hour and it was still going.
I've managed to restore it back to my previous 4.4.4 for the moment, but I would like to move to Lollipop at some point - if I could !
Could someone suggest a method I could try please ?
Many thanks !
Kev.
Hi there.
Well, my device is a XT1032 Retail US but I may have been through the problems you're facing right now.
Here we go:
Go full stock (don't know if you revocer from a backup or already did this but in any case you'd know what to do: This guide helped me a lot. http://forum.xda-developers.com/showthread.php?t=2542219.
Do not install any official update using a custom recovery
Make sure you got the actual latest recovery version. If you went stock from the latest firmware you should have already got it.
If you have your OTA, Install it manually from the stock recovery
This method should work. It is the one I followed.
I got two errors: 1st was because was using custom recovery.
2nd was because my rom was stock but had deleted system apps, so the install failed always at some point.
Once I flashed the latest stock firmware including the stock recovery, I was able to install my OTA update.
Let me know if this works.
I recently updated to the rooted lollipop upgrade using the chainfire method. it had lags so I decided to go back to 4.4.2. I made an error by flashing stock 4.4.2 and now my phone is bricked in boot loop. can anyone help me to restore my phone please. The recovery system status says custom.
I installed custom ROM asop on d850 test mode..and when I tried to get back to cyanogenmod I could not boot into recovery mode due secure booting error! Cause: boot certification verify..other than that my phone works fine..my phone is not rooted and the ROM doesn't have any thing on it no play store no browser etc...is there any way to fix it..I tried to flash back to official firmware but I couldn't due to either wrong files or I'm just too dumb...kindly give me an easy solution guys..
Axad101 said:
I installed custom ROM asop on d850 test mode..and when I tried to get back to cyanogenmod I could not boot into recovery mode due secure booting error! Cause: boot certification verify..other than that my phone works fine..my phone is not rooted and the ROM doesn't have any thing on it no play store no browser etc...is there any way to fix it..I tried to flash back to official firmware but I couldn't due to either wrong files or I'm just too dumb...kindly give me an easy solution guys..
Click to expand...
Click to collapse
You don't have play store because your supposed to flash a google apps package along with CM. If you've lost recovery you need to follow my tot method and flash it back to stock.
Sent from my iPhone using Tapatalk