Straight to the point:
Installed Xposed Lollipop, gave me low storage warnings
Rebooted to see if it would fix that, it built cache again but warning stll there
Boot into recovery, selected "Fix Permissions" in TWRP, wiped dalvik cache and cache
Booted again, goes through boot cycle but then goes straight to a black screen. Can get into bootloader. Wasn't able to go into recovery (spit out a black screen) but I plugged it into the charger and was able to get in.
I've unlocked the bootloader, rooted and that's about it. I'm rocking the Pure Edition. Anything I can do short of Factory Reset? I really don't want to lose my data for no reason.
Edit: I flashed system.img and boot.img from the toolkit in Android Development. That didn't work outside of TWRP detecting root wasn't installed. I did a Factory Reset in TWRP and that fixed things. Oh well.
Did you wiped dalvik and cache after flashing zip? ?
@jcracken: the perils of using Alpha software.
Go back into recovery and reflash xposed. Then reboot. I also used selmodechanger and set it to permissive.
This is not due to xposed. The bootloop was due to TWRP, DO NOT FIX PERMISSIONS FROM TWRP. It will cause a boot loop on lollipop whenever you do it
To uninstall xposed on lollipop go into file manager in twrp and delete xposed.prop in /system partition after mounting and also delete xposed.jar in /system/framework
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
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.
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 just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.