I have a XT1096 that was running an early August nightly version of CM13. I downloaded the September 6 nightly and dirty flashed it onto the phone, and now the phone is stuck at the boot screen, it never gets to the "optimizing apps" screen. I've tried accessing logcat, but the phone doesn't get far enough to start adb, so that doesn't work. There is no /proc/last_kmsg file. Then I tried clean flashing the September 6 nightly, and that seemed to flash correctly, but the phone is still stuck on the boot animation.
Not only do I not know what's going on, but I also don't know how to investigate what's going on. Any help with either would be highly appreciated.
TheSpaceTimeKaiserZero said:
I have a XT1096 that was running an early August nightly version of CM13. I downloaded the September 6 nightly and dirty flashed it onto the phone, and now the phone is stuck at the boot screen, it never gets to the "optimizing apps" screen. I've tried accessing logcat, but the phone doesn't get far enough to start adb, so that doesn't work. There is no /proc/last_kmsg file. Then I tried clean flashing the September 6 nightly, and that seemed to flash correctly, but the phone is still stuck on the boot animation.
Not only do I not know what's going on, but I also don't know how to investigate what's going on. Any help with either would be highly appreciated.
Click to expand...
Click to collapse
Which exact version of TWRP are you using?
You should keep the latest stock firmware at hand in case of problems:
https://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1096/
Use TWRP 3.0.2-2 (so far I've had no problems with it):
https://dl.twrp.me/victara/
Boot into TWRP, tap Wipe, tap Format Data, type yes and then Reboot Recovery
Tap Wipe again, tap Advanced Wipe, and select Dalvik/ART cache, System, Data, Cache, and wipe them, now flash the latest CM13 and Open Gapps, or Delta Gapps.
Related
I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
cbrvnm said:
I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
Click to expand...
Click to collapse
wipe dalvik cache??? From what i know, Lollipop uses ART.
These are the options I have in my recovery under advanced wipe
Even though the runtime is ART now, clearing dalvik in TWRP does force a 'rebuild' of apps upon boot, so it does still have a purpose.
The 'rebuild' I'm talking about is the "android is upgrading" screen.
cbrvnm said:
These are the options I have in my recovery under advanced wipe
Click to expand...
Click to collapse
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Flash system.img
Ghettonine said:
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Click to expand...
Click to collapse
When he says "firmware" he means
Code:
fastboot flash system system.img
It won't wipe your data, but it will remove no-force encryption (NFE) and you're going to need to re-root :good:
Had the same problem a few days ago.
@Ghettonine I don't think it's TWRP, more so SuperSU
I was able to use rootkit to flash stock and unroot and it goes through the whole process and states that it was successful and to wait until it boots. The problem is that it never boots and stays in the boot screen. Also I have had it on for 30 mins multiple times and still not working. I boot into recovery but this time I don't have TWRP anymore I just have a android with red triangle with no options to choose. Any other suggestions that could help?
Re-flash stock factory images and stop relying on tool kits to flash stuff. Learn how to use adb and fastboot, or just don't bother messing with root.
Using 2012 Fire HD 7"
I rooted it and installed the second bootloader and TWRP 2.7.0.0 just fine, and it even booted back into the stock OS just fine
But then when I went into recovery to flash Paranoid Android and its gapps, I started running into problems.
I rebooted after that and it stayed on the blue boot logo for over 10 minutes, so I rebooted and did a factory reset wipe and tried again.
When I tried the wipe then, though, it then said that the wipe failed and that all of the partitions (data, system, cache, dalvik, etc) couldn't be mounted...
Also, I can't use USB mounting because it says that it cannot find USB volume information.
I can get into TWRP just fine, but I can't seem to flash the ROM because it always just bootloops instead after completion.
I'm not really sure what to do now. Any help?
GoodOlTarvis said:
Using 2012 Fire HD 7"
I rooted it and installed the second bootloader and TWRP 2.7.0.0 just fine, and it even booted back into the stock OS just fine
But then when I went into recovery to flash Paranoid Android and its gapps, I started running into problems.
I rebooted after that and it stayed on the blue boot logo for over 10 minutes, so I rebooted and did a factory reset wipe and tried again.
When I tried the wipe then, though, it then said that the wipe failed and that all of the partitions (data, system, cache, dalvik, etc) couldn't be mounted...
Also, I can't use USB mounting because it says that it cannot find USB volume information.
I can get into TWRP just fine, but I can't seem to flash the ROM because it always just bootloops instead after completion.
I'm not really sure what to do now. Any help?
Click to expand...
Click to collapse
Sounds like your recovery somehow got corrupted. At this point I would just suggest to get a fastboot cord and factory reset. You can always tried to ADB sideload a ROM onto TWRP, but if you can't get it to mount now I doubt it will mount to flash the ROM fastboot.
I was trying to install CM12 on my VS980 LG G2, and in order to do that I installed TWRP 2.8 because that was what they recommended to use with that version. It worked, and I installed it by using the flashable zip from http://blastagator.ddns.net/twrp/2-8-3-1.php
I used this recovery to install the latest build of CM12 from here: http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269 after wiping my data using advanced wipe as the TWRP thread says to. I wiped Dalvik, system, and cache, and then flashed the ROM, GApps, and SU.
When I rebooted, I was bootlooping. Not too abnormal for flashing things on this phone, so I went back into recovery to restore the backup I had made, to find that the backups file list is completely blank. No (Up a folder) or anything. So I panic, and think I wiped more than I have to, so in order to reset everything and start over, I did a format. It says it completes, so I reboot and get back into recovery, and push a new rom to /data/media/0.
Now, when I try to install that zip, it's not there. Nothing gets placed in there. Installing a zip from anywhere else results in bootloops because it can't boot anything, somehow. It's like there's two partitions and it's trying to boot from the one with nothing on it, and that's the same one I'm shown when I go into the restore menu. There are folders like /data/, /sdcard/, etc still visible if I try the install option, but they do not show up when I try to use the file manager in TWRP.
I'm not sure what to do, can I fix the partitions that TWRP is looking at somehow, or is that not even the issue here? I would like my phone to be usable and I feel that having the recovery it shouldn't be this hard to get it back to booting order.
Thanks
I have close to the same issue on my vs980. Except I have twrp 2.7 and I can't flash it 2.8.4 it always fails. But cm12 and gapps were successful on 2.7 version of twrp except it out me in a bootloop. Which my backup and everything was still there for me to restore. Do you have an issues with random reboots after you put twrp on your phone too?
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
phoenix964 said:
Hi,
I had recently tried to root my Moto G 2014 (running 6.0) so I could install the latest CM13. I followed all the instructions and even came across the red WARNING BOOTLOADER UNLOCKED SCREEN every time I try to reboot the device(status code=3). After installing TWRP 3.0.2.3 and making a backup of current state, I ran into a few bootloops which I managed to fix by flashing it back with a stock as shown on this thread http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 (I downloaded both the download links and extracted everything to a single folder before following all the commands)
The SIM wasn't receiving any signal thereafter, which I luckily managed to fix with help from another thread.
My problem is that I've tried to install SuperSU more than a couple of times with different versions and it almost always sends my phone into a bootloop. The few times where I was able to boot into system, it kept giving me the error that the necessary binaries weren't installed and I was not able to do as well, due to the bootloop issue. Working RootChecker told me that my device wasn't rooted properly, which I wasn't surprised at.
Although I read somewhere that rooting isn't necessary to flash a custom ROM like CM13, so I decided to negate SuperSU (I did the unroot everything option on SuperSU and factory reset the device, cleared data, cache and dalvik too) and try flashing it directly instead through TWRP. It kept giving me the Error 7 even after I had removed the assert checks.
Can someone tell me what I did wrong and what can I do to go ahead? Also, is my bootloader completely unlocked? I tried checking *#*#7378423#*#* but nothing happened, so I rebooted into bootloader and used the 'fastboot oem device-info' command but it said that the command was invalid or something.
As of right now, the phone is running 6.0 with all the stock apps. The bootloader unlocked warning still shows up every time I reboot the phone though.
Click to expand...
Click to collapse
while @kushal_10 explained most of the things to do, i would like to remind you that CM13 has inbuilt Root. You just have to enable Developer options, then in Developer Options,under Root Access, choose Apps and ADB. Don't flash SuperSu
Hope I helped you.
kushal_10 said:
Boot into twrp and wipe cache , dalvik cache, system and data and flash cm13 and wipe cache and dalvik cache and reboot you should be good to go if u want root access flash the latest version of supersu or you can for a rom which has preinstalled supersu such as dirty unicorns.
Click to expand...
Click to collapse
I read somewhere that wiping the system isn't advisory because in case something goes wrong, there will be no way to restore. Can you confirm this?
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Aravindtop said:
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Click to expand...
Click to collapse
RSDlite, Mm firmware, fastboot mode.
Sent from my XT1254 using Tapatalk
Aravindtop said:
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Click to expand...
Click to collapse
Try flashing the ROM, let it boot, then go back into TWRP and flash the GAPPs. No you probably shouldn't have to do that, but I've had to do stuff like that before on some phones.
Also drag a fresh copy of the ROM over from PC to TWRP. Something may have gotten corrupted.
Last make sure you have most recent version of GAPPs. Some people had bootloops trying to run GAPPS from March when there was a 7.1.2 update to all Nougat ROMs in April. GAPPs was incompatible. "But I've been using this for weeks now!" Yes, that's the problem.
ChazzMatt said:
Try flashing the ROM, let it boot, then go back into TWRP and flash the GAPPs. No you probably shouldn't have to do that, but I've had to do stuff like that before on some phones.
Also drag a fresh copy of the ROM over from PC to TWRP. Something may have gotten corrupted.
Last make sure you have most recent version of GAPPs. Some people had bootloops trying to run GAPPS from March when there was a 7.1.2 update to all Nougat ROMs in April. GAPPs was incompatible. "But I've been using this for weeks now!" Yes, that's the problem.
Click to expand...
Click to collapse
Yup, I did that, flashed nothing but the latest version of LOS and let it sit for half an hour, didn't boot. Funny enough, I flashed the official Turbo Marshmallow ROM and it booted up pretty quickly. So I immediately went back to TWRP and flashed LOS and GAPPS again and what do ya know, it booted. Everything works fine now. That episode was really strange and had me thinking that I finally killed the phone would need to get a new one.
Yeah, every time failed to boot, I would go back to TWRP do a wipe and copy the files over again from my PC. I was using the latest version of LOS and GAPPS, literally downloaded them today for the first time.