So I just flashed the LG G6 Port rom, and it worked fine. Booted into the phone to check and it worked so I booted back into TWRP to flash Gapps. I got the Full Gapps for Android 7.0 as that is what the software version is listed as in Device info on my phone. Downloaded them from the Open Gapp Project Website. For some reason it keeps failing to flash properly tho. I tried version 7.1 too just for the hell of it and that didn't work either.
I've never had an issue flashing Gapps before and I've been flashing them for years. So I have no idea what could be causing the issue so I was hoping one of you al might have the solution to my problem.
So yea HELP PLEASE !!! LOL
When you flashed gapps did you be sure to wipe the cache? I think you should always do that if you flash something after first boot
Related
I was flashing and using LP roms normally till I came back to KK.
After a week I wanted to come back to LP, but then, every lp rom I flash gave me the message "systemui stopped working" right after the boot
I can't even click an app icon
What i've already tryed:
-Clean Flash
-Dirty Flash
-Update Recovery (TWRP)
-Flash With/Without GAPPS
-Diferrents ROMS
Nothing seems to work, every rom gave the same error after flashing
Can someone help me?
I have seen this and forget how I got past it but try this recovery - http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
Even before trying that - try a clean flash of a very early version of L then boot it up. Then dirty flash the latest version and gapps.
rdenova said:
I have seen this and forget how I got past it but try this recovery - http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
Even before trying that - try a clean flash of a very early version of L then boot it up. Then dirty flash the latest version and gapps.
Click to expand...
Click to collapse
WORKING!
Thanks man, changing the recovery made the trick
I could never imagine that was it. Thanks again!
Man, right after i replyed you and was config my phone the problem came again from nothing!
I have no idea what to do
What gapps are you using?
Try this->https://www.androidfilehost.com/?fid=95864024717066722
Flash that from recovery.
I gotta remember how I beat that...have not seen that issue in a while now....
rdenova said:
What gapps are you using?
Try this->https://www.androidfilehost.com/?fid=95864024717066722
Flash that from recovery.
I gotta remember how I beat that...have not seen that issue in a while now....
Click to expand...
Click to collapse
Remember pls
I guess there's no problems with the gapps, because, even when I flash without the gapps, I got the same error
BTW i'm download that gapps to flash it
Help pls
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Has OP found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Did you guys flash CM11 first let it boot up and then dirty flash CM12? Might not be needed still but was when I tried CM12.
Just installing CM 11, or any other rom, caused this problem. Unfortunately can't go back to my 1053 stock as I didn't make a nandriod backup since I didn't think I needed.
...not sure if it'll help, but did you guys update the bootloader and such to match your android version? I had to update mine before it would work right.
Your kernel may be out of date, update it or change it
Hey everyone, :laugh:
I found an Official update for my device from CyanogenMod Download Site.
I search any forum if available here about this ROM, unfortunately i cannot be able to find any form related to this ROM. Then i download 5.1 Gapps and download the ROM CyanogenMod 12.1. i wipe dalvik , userdata , cache and system. then flash both of the zip files ive downloaded. As i was using 12.0 Cyanogen i dont think i need to flash Cyanogen snapshot as it require for 12.0 to solve the BootLop. After flashing my phone is stuck on the booting animation since 20-25mins then i force reboot my phone into Recovery then i flash the SNAPSHOT and then reboot for once it works fine for me, then i just flash 12.1 and L gapps on the phone and then reboot, unforunately im facing the same problem from last hour. I dont know how to make 12.2 Cyan to work on my phone wihtout bootlop.
If anyone knows how to remove the bootlop then please let me know, thanks
Shehry_97 said:
Hey everyone, :laugh:
I found an Official update for my device from CyanogenMod Download Site.
I search any forum if available here about this ROM, unfortunately i cannot be able to find any form related to this ROM. Then i download 5.1 Gapps and download the ROM CyanogenMod 12.1. i wipe dalvik , userdata , cache and system. then flash both of the zip files ive downloaded. As i was using 12.0 Cyanogen i dont think i need to flash Cyanogen snapshot as it require for 12.0 to solve the BootLop. After flashing my phone is stuck on the booting animation since 20-25mins then i force reboot my phone into Recovery then i flash the SNAPSHOT and then reboot for once it works fine for me, then i just flash 12.1 and L gapps on the phone and then reboot, unforunately im facing the same problem from last hour. I dont know how to make 12.2 Cyan to work on my phone wihtout bootlop.
If anyone knows how to remove the bootlop then please let me know, thanks
Click to expand...
Click to collapse
Hmmm...I was on CM12 and wiped everything (cache, dalvik cache, system, data) so I clean flashed CM12.1 and GApps 5.1, after 2-3 mins it booted ok. So I guess flashing CM11 first is not needed. Just try again idk...:/
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked
Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
BEDickey said:
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
Click to expand...
Click to collapse
I haven't flashed this rom for my turbo yet and this may not be the issue but in the past, dealing with other phones on CM, when you would 1st flash the rom, (& before rebooting the 1st time) you would then need to flash the gapps immediately after for everything to work properly. Try flashing the rom and gapps before rebooting.
I didn't see if the CM op instructions recommended this, just personal experiences from previous rom flashing.
I have had this happen twice after installing any CM13 on top of the March 31 nightly. I have not found a way around it yet besides doing a factory wipe after installing CM13, Open GApps and the latest radio code in this thread.