Here's all the details i have in a nice list:
I did a factory reset and then installed cm12 and gapps
I now realize that I left xposed installer installed
rebooting to recovery sticks at bootloader unlocked warning
turning off and plugging in yields cm animated charging battery
EDIT: Got recovery working by reflashing it through fastboot
Solved.
Had to enter fastboot and reflash twrp, then recovered into a backup of stock to disable xposed (oops ), and then go back to twrp and wipe everything except external sd card before flashing.
I am now running cm12 nigthly build for 2/1/2015!!
Can you help me? It seems u had a simular problem. I installed CM12 nightly but NOW anytime (regardless of ROM)(except the stock TW ROM) if i try rebooting the phone will not reboot. You mentioned something about Xposed modules. Did i need do uninstall exposed before moving from slimrom to CM12? I wiped, cache, dalvik, data and system and then installed CM12. Did i do somthing wrong? If i reboot i have to wipe everything, format data and then restore to my slimROM backup. (or do i clean install of some other rom) to use my phone. Please help me if you can. I cant reboot my phone
sharpknight said:
Can you help me? It seems u had a simular problem. I installed CM12 nightly but NOW anytime (regardless of ROM)(except the stock TW ROM) if i try rebooting the phone will not reboot. You mentioned something about Xposed modules. Did i need do uninstall exposed before moving from slimrom to CM12? I wiped, cache, dalvik, data and system and then installed CM12. Did i do somthing wrong? If i reboot i have to wipe everything, format data and then restore to my slimROM backup. (or do i clean install of some other rom) to use my phone. Please help me if you can. I cant reboot my phone
Click to expand...
Click to collapse
I'd imagine wiping everything would take care of the xposed framework. How long did you let CM12 boot for? Lollipop ROMs can take a very long time for first boot, sometimes upwards of 20 minutes.
Sent from my Blissful RAZR M 5.0.2 from Tapatalk
xKroniK13x said:
I'd imagine wiping everything would take care of the xposed framework. How long did you let CM12 boot for? Lollipop ROMs can take a very long time for first boot, sometimes upwards of 20 minutes.
Sent from my Blissful RAZR M 5.0.2 from Tapatalk
Click to expand...
Click to collapse
10 minutes. Im back on slimROM (4.3) but the problem still persists.
If i reboot i have to restore. Could SLim also be taking so long all of a sudden?
I updated to TWRP 2.8 btw.
sharpknight said:
10 minutes. Im back on slimROM (4.3) but the problem still persists.
If i reboot i have to restore. Could SLim also be taking so long all of a sudden?
I updated to TWRP 2.8 btw.
Click to expand...
Click to collapse
Slim should not be affected. I'd uninstall Xposed (via the installer app) and start fresh, with either LP or KK, whichever you prefer. LP takes significantly longer than 10 minutes to boot the first time, if you decide to try it again, let it go for at least 25 minutes before calling it dead. After first boot, it can restart pretty quickly.
Sent from my Blissful RAZR M 5.0.2 from Tapatalk
xKroniK13x said:
Slim should not be affected. I'd uninstall Xposed (via the installer app) and start fresh, with either LP or KK, whichever you prefer. LP takes significantly longer than 10 minutes to boot the first time, if you decide to try it again, let it go for at least 25 minutes before calling it dead. After first boot, it can restart pretty quickly.
Sent from my Blissful RAZR M 5.0.2 from Tapatalk
Click to expand...
Click to collapse
I know the problem happen to me all you have to do I download the Correct gapps. Lollipop gapps not kk gapps.
Sent from my SCH-I545 using XDA Free mobile app
Related
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
ifonuser78 said:
Hi guys,
I'm having a weird problem. I've used a i9100 and i9300 in the past and have flashed hundreds of different ROMs, kernels and recoveries. I was running WanamLite on my i9505 until I wanted to switch to PAC Alpha 4.3. I had a few problems installing it (didn't want to go past the boot logo) but eventually with TWRP it worked. I wasn't too happy with the alpha version (freezes here and there) and switched to Omega 9 4.2.2. Installed Xposed framework, rebooted and got stuck on boot. I couldn't access the recovery immediately, first I had to remove the battery, wait and after a few tries I was in the recovery. Removing Xposed framework, wiping data, cache, dalvik cache didn't help Omega 9 to boot up. I re-installed Omega 9 and did a restart without installing Xposed framework, and it froze on boot. Same thing happened when I installed WanamLite, Echoe and Google Experience ROMs and did a restart after the successful first boot after installation.
The only way to get past this problem is to:
a) flash the pre-rooted, original Samsung MGA ROM
b) enter recovery and wipe data/factory reset
If I skip b) then it will just enter a boot loop (boot halfway, reset, boot halfway, reset...)
It's driving me crazy. I do not want to use the original ROM and have no idea what is causing this behavior. I appreciate your help.
Here the information of the working MGA ROM:
4.2.2
I9505XXUBMGA
3.4.0-1081224
[email protected] #1
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
This happens with many including me some time with many diffrnt files chainging and overwriting causes the same
Best option as u said above flash stock firmware
Then u can try what I feel will work better in ur case
Root the phone with CF root method
Flash Philz Recovery
wipe cache / dalvik / ix perm and reboot and go ahead with ur Rom flashing
Ok, flashed the stock ROM which was not rooted, then rooted using CF's method and flashed PhilZ. I couldn't find the option to fix permissions in PhilZ recovery, and went ahead with the installation of Omega 9 after wiping. I couldn't even get Omega to boot, previously it worked on the first boot and then no longer after a restart.
I don't know whats going on here.
I'm flashing the pre-rooted MGA now.
ifonuser78 said:
I'm flashing the pre-rooted MGA now.
Click to expand...
Click to collapse
Pre-rooted MGA works fine, but no other custom ROM.
I ran TriangleAway to reset the counter, but that didn't help either. No third party custom ROMs for me. :crying:
Flash latest Philz recovery.
Go to mounts and storage.
MAKE SURE YOU HAVE A ROM ON SD CARD.
Format system, cache, data and preload.
then just to be sure everything is gone I go to wipe /data factory reset and choose the wipe to install a new rom.
Then go to install zip and flash rom.
Once it's flashed you should be good to reboot.
If you're still in a bootloop then go to wipe/data factory reset but choose first option not the one to install rom.
Now reboot again, good to go!
Just a thought, if you're still having trouble flash a AOSP kernel in Philz as you might be trying to boot an AOSP rom with a TW kernel installed
Sent from my GT-I9505 using XDA Premium HD app
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Hello, xda. I have a lot of time using the Motorola android phones, but faced with the problem of firmware change on my xt907 for the first time. I'm on stock 4.4.2 (182.46.10) with root, custom recovery, but now would like to try CM or gummy.
I met a problem that after cm-11-20140914-NIGHTLY or any other ROM installed from recovery, during the first boot, after language selecting my phone starts cyclic reboot.
I tried cwm 6.0.3.9 and twrp 2.8.0.0, 2.7.1.0, doing all wipes before (or/and after) installation. I try to install this ROMs over 4.4.2 stock and on the clean system (after erase /system). But nothing worked. With RSDLite I can always switch back to 4.4.2 I can always switch back to 4.4.2, but the inability to use CM bother me.
I have original xt907 from verizon, but I use it abroad (gsm).
I will be glad to hear any ideas and suggestions about this situation, many thanks
And sorry for my pigin-English
Do you wipe data before installing the ROM?
Klen2 said:
Do you wipe data before installing the ROM?
Click to expand...
Click to collapse
Sure. Before and/or after. From fastboot (first time), from recovery. And i`m telling about clean stock 4.4.2 from RSDLite
I'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
MrJodroid said:
I'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
Click to expand...
Click to collapse
Maybe bad download redownload
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
MrJodroid said:
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
raptorddd said:
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
Click to expand...
Click to collapse
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Hiiii
MrJodroid said:
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Click to expand...
Click to collapse
glad you got it back working.. youre welcomed.
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Chikyu Tenshi said:
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Click to expand...
Click to collapse
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
Try these gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
You need to perform a full wipe though.
Lennyz1988 said:
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
You need to perform a full wipe though.
Click to expand...
Click to collapse
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
You need 5.1 gapps then.
Chikyu Tenshi said:
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
Click to expand...
Click to collapse
My bad. Here is also another gapps
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Lennyz1988 said:
My bad. Here is also another gapps
Click to expand...
Click to collapse
Still :c I only flashed the base tho, Am I supposed to flash the add ons too?
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
CHIN3S3_N00B said:
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
Click to expand...
Click to collapse
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Could you try GearCM? Official CM for i9500 had lots of issues.
Sent from my GT-I9500
Chikyu Tenshi said:
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Click to expand...
Click to collapse
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
CHIN3S3_N00B said:
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
Click to expand...
Click to collapse
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Lennyz1988 said:
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Click to expand...
Click to collapse
I think that i didn't express myself very well. Yes it's advisable and strongly recommended to use lastest builds of any recovery available as stable build.
But once i had to use Philz to flash a MIUI ROM because TWRP 2.8.6.0 was unable to execute the installation script didn't know why and that's why i said about different recoveries, and oh.... I forgot to say that after successful install rollback to TWRP because it's pretty new , stable and more user friendly than others.(CMW and the rainbow Easter egg was fine but having to use vol and power keys..... NO THANKS!)