I have an LG G3 running the latest CM 13 nightly with TWRP for a recovery.
Last night I went into the SU app on my phone and it said it needed an update (I was not connected the internet). I clicked update via TWRP and it went into TWRP. It ran some code and now it is stuck in a bootloop. It will boot to the CM logo with the pulsing light and will get no further. I've tried wiping cache and dalvic cache and that didn't work. Tried fixing permissions and that didn't work. Also tried factory reset via TWRP and that did not work also. Please help.
Try reflashing your rom
Sent from my HTC One M9 using Tapatalk
Flash an earlier build of su. When prompted select normal "NOT TWRP"
Sent from my XT1526 using Tapatalk
Why is this in the xposed section?
I am facing the same problem.
Tried factory resetting.Didn't work,still stuck on bootloop.
Somebody please help me out!
Related
I installed elemental x kernel and all was fine went back into recovery and twrp is asking for a password and i cannot mount anything when i boot the system i all kinds of FC's now...
I fixed it by reformatting data then restarting recovery
Sent from my Nexus 7 using Tapatalk 4
unobtainiumdroid said:
I fixed it by reformatting data then restarting recovery
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
were you able to restore after that?
I had to adbpush the ROM through
Sent from my Nexus 7 using Tapatalk 4
i cannot restore data....
Many people have had this problem.
When you're asked for a password, hit cancel. Then go to Wipe and Factory Reset. If that doesn't work, then restart your recovery. If that still doesn't work then try reflashing TWRP again.
When you do the fastboot oem unlock, you should do it using stock recovery and let it reboot and wipe data.
Then boot back into bootloader to install twrp.
Don't do both at the same time.
sfhub said:
When you do the fastboot oem unlock, you should do it using stock recovery and let it reboot and wipe data.
Then boot back into bootloader to install twrp.
Don't do both at the same time.
Click to expand...
Click to collapse
I did... was running fine a few days and all of sudden this happened. Wiping data did but i still could not restore data from backup i had to reset and restore from titanium.
When TWRP does this to me I reboot into system then with goomanager I reinstall TWRP. It seems that some changes in the system cause this. AOSP Browser appears to do this to me or the kernel as those are the only thing I have on that modifies the system. Need more testing
Blackwidowman said:
When TWRP does this to me I reboot into system then with goomanager I reinstall TWRP. It seems that some changes in the system cause this. AOSP Browser appears to do this to me or the kernel as those are the only thing I have on that modifies the system. Need more testing
Click to expand...
Click to collapse
Happened to me after the kernel.
Sent from my Nexus 7 using Tapatalk 4
I have the kernel and also have aosp browser and twrp is fine so far.
Sent from my Nexus 7 using XDA Premium HD app
Hi, I have the same problem and I can't boot my tablet in normal mode, it remains frozen on start animation screen. I started unlocking bootloader with no problems and the problem started after i install the TWRP 2.6.3.0. I'm on Android 4.3.1 (JLS36I). I can't wipe or mount /data, I can't enter in ADB Sideload mode.
I tried to fix it installing TWRP again and I also installed CWM but with the same result.
I was trying to find the original recovery image but with no success.
Any idea about how to get out of this mess?
Thanks!
pvitruvian said:
Hi, I have the same problem and I can't boot my tablet in normal mode, it remains frozen on start animation screen. I started unlocking bootloader with no problems and the problem started after i install the TWRP 2.6.3.0. I'm on Android 4.3.1 (JLS36I). I can't wipe or mount /data, I can't enter in ADB Sideload mode.
I tried to fix it installing TWRP again and I also installed CWM but with the same result.
I was trying to find the original recovery image but with no success.
Any idea about how to get out of this mess?
Thanks!
Click to expand...
Click to collapse
If it is frozen on X then your /data is messed up. Do a wipe data factory reset from recovery.
If it is frozen on Google, then your /system is messed up, to a nowipe factory image restore.
It is doubtful TWRP caused this problem. Most likely your tablet corrupted /data and it only showed up after a reboot.
sfhub said:
If it is frozen on X then your /data is messed up. Do a wipe data factory reset from recovery.
If it is frozen on Google, then your /system is messed up, to a nowipe factory image restore.
d
It is doubtful TWRP caused this problem. Most likely your tablet corrupted /data and it only showed up after a reboot.
Click to expand...
Click to collapse
It was frozen on X but I couldn't wipe it because it didn't mount /data, all the wipe commands failed.
Now I could fix the problem. What I did was to connect an external drive through USB-OTG and I installed the SuperSu zip (the step where I was stuck), after that I could format data and perform a Factory Reset. After the first complete boot, the TWRP stopped to ask password and everything seems to be OK.
Thanks!
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
sgtfrnz said:
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
Click to expand...
Click to collapse
Well something was messed up when you flashed xposed installer( i don't know what you mean by automatic method) but do a clean install,since you can get into download mode,grab the twrp img.tar and flash it using pc odin ,then you can access recovery, do all the wipes again by going under "advanced" and reflash your rom.Now to install xposed go to xda thread for it and grab the apk from there (i think it's available on play store as well).You should have no more issues
Twrp
Like the previous post said I'm not sure what you've done. When xposed framework is installed there is usually an unistall zip created on the internal so card. If you can get recovery find it and flash it
Sent from my GT-N7105 using Tapatalk
The device is now fixed.
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
sgtfrnz said:
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
Click to expand...
Click to collapse
Boot into Download mode and flash philsz touch recovery 6 and reboot device .. Everything will be ok>
Old thread may be old, but it's still relevant.
I just tried to install XPosed as well on my Note II and it did the same thing (mine's AT&T)
Info
Device: Note II
XPosed Version: 2.6.1
Install Method: "Recovery (flash zip automatically)"
Recovery Image: TWRP
Mine exhibited the same behavior as OP's, however after leaving it alone for a while to bootloop recovery as much as it wanted to, I came to my laptop, found this post, grabbed as USB cable, and I was just about to start the process of reflashing recovery when all of a sudden I saw my lock screen.
It took roughly five minutes of bootloop to get it there, but it successfully installed XPosed and my device is running fine.
So, for all the other Googler's out there that landed on this post, leave it alone for a while! See what happens. If it's still bootlooping, like, 30 minutes later, then try reflashing TWRP using ODIN. If that still doesn't work, reflash a new ROM using TWRP.
[EDIT:] Device is not bricked as per previous post..have managed to get back to TWRP.
Now, to my earlier issue. I am stuck in a TWRP loop. I have flashed the AOSP 6.0 ROM, reboots into TWRP. I have wiped and restored my backup, still boots into TWRP. Should I try a different ROM or what am I doing wrong?
Thanks
Have the same problem. Help please!
Sent from my LG-H901 using Tapatalk
http://forum.xda-developers.com/lg-g-pad-83/help/help-flashable-rom-kitkat-lg-v490-t3295885 Please read this, that should work. for me it help.
Hey guys,
first what happened.
I was running the latest CM 14.1 nightly on my oneplus 3. Then I saw the new Video from xda on youtube. I installed substratum and a theme. But after rebooting I got a bootloop.
Tried resetting via cm recovery did not work. Then tried resetting via fastboot. Also did not work device won't boot up.
So I tried flashing the original boot.img and system.img. Flashing itself worked great. Phone gets to the OP and Android-Logo then screen goes black and device turnes off. Same with the twrp-recovery I tried to flash. Won't boot into recovery.
What can I do/try?
Please help thx
Premaider
Premaider said:
Hey guys,
first what happened.
I was running the latest CM 14.1 nightly on my oneplus 3. Then I saw the new Video from xda on youtube. I installed substratum and a theme. But after rebooting I got a bootloop.
Tried resetting via cm recovery did not work. Then tried resetting via fastboot. Also did not work device won't boot up.
So I tried flashing the original boot.img and system.img. Flashing itself worked great. Phone gets to the OP and Android-Logo then screen goes black and device turnes off. Same with the twrp-recovery I tried to flash. Won't boot into recovery.
What can I do/try?
Please help thx
Premaider
Click to expand...
Click to collapse
Flashed original cm recovery. That works an boots up. What now?
flash the custom recovery for CM or sideload a official oneplus rom.
Hey i flashed the CM-13 on my GT-N5100. At first, it worked well. I can even installed GApps package and changed the theme. Then i tried to install SuperSU and it asked to install the SU binary. So i installed it using flash recovery. It succeed, but when i tried to reboot the phone, it stucked on the "marshmallow" animation boot. I have tried to wipe data and cache, but those didn't work. Then i tried to re-install the CM-13 package (using flash recovery ofc) but it just showed an error message. What should i do? I'm planning to downgrade the phone back to Kitkat. Would it do? Or is there any other way? Please help. Thanks!
hyemun01 said:
Then i tried to install SuperSU and it asked to install the SU binary. So i installed it using flash recovery. It succeed, but when i tried to reboot the phone, it stucked on the "marshmallow" animation boot. I have tried to wipe data and cache, but those didn't work.
Click to expand...
Click to collapse
Hi
had the same problem yesterday, i found no other way as to make a complete wipe (including SYSTEM!) in TWRP and then without rebooting install the ZIP again. Than it was resurrected.
But make sure that the ROM Zip is on the external sd card.
The problem is the SuperSU, just use the internal Root function.