Bootloop after installing TWRP and trying to start xposed - Samsung Galaxy S7 Edge Questions and Answers

Hi there,
I followed all the instructions but I didnt read the part where it tells you that you have to install something so it can boot again. It seems that I am now unable to boot. I was really hoping that someone can help me.
I tried to install it after the first failed boot attempt but it didnt change anything.
Thank you in advance for your help.

It seems like you've installed the official build of xposed framework which is not compatible with most of Samsung devices.
You need to download the unofficial build for Samsung from here http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TWRP should be accessible if you've installed it correctly by holding the Power, Vol up and home button at the same time.
If it boots to TWRP, go to mount the mount USB storage and place the downloaded version of Xposed on the phone then unmount USB storage and install it.
That's all

Themohd is correct
Also, there is some verity opt zip which i needed to install with twrp for disabling encryption
And remember to flash supersu v2.65+ for MM,I lost my moto droid maxx to that.

Hello everyone! New member here.
I'm posting because I experienced something similar to this.
I was flashing TWRP from pure stock but missed a certain step (provided below). When TWRP loaded, it seemed like it couldn't detect any of the partitions on my S7 Edge, so I restarted it to system and ended up in bootloop.
Here is the step from the TWRP guide:
Step: 8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery
Guide: http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
So my question is, what does step 8 do exactly? Was it significant enough to cause the bootloop on my phone or could it have been something else? I was doing this because I want to flash Xposed Framework.
EDIT: After thinking about it, I'm sure step 8 brings you straight to recovery instead of booting into system then restarting manually into TWRP. So now I'm wondering this, what caused TWRP to not detect any of the partitions? In detail, TWRP showed all the partition sizes as "0 MB" when I went to a certain page (forgot what exactly lol). But I will follow the instructions step-by-step and get back to you guys.

Related

[Q] VS980 - CM11, TWRP 2.7.0.0, Whole Disc Encryption - What To Do Next?

I followed these instructions about 2 months ago. I had success flashing 11A on to the phone using the KDZ method. From there I was able to root the phone, then install TWRP 2.6.3.0, then TWRP 2.7.0.0. Once TWRP was on the phone I installed CM11 nightlies, which have been working with varying degrees of success up until about a month ago. I decided to encrypt the phone, which turned out to be one heck of a mistake! I now have a few problems, and am in need of some guidance on how to proceed:
1) When I go in to TWRP 2.7 I am not prompted for an encryption password. Without this I am unable to mount System, which means I can no longer flash CM11 updates. Despite reading about sideloading on TWRP's website I'm unsure if wiping the System partition in TWRP (likely after checkmarking rm -rf option) then attempting a sideload of the newest nightly of CM11 would be the appropriate next step. My fear is that I'll wipe System and then be unable to sideload successfully, resulting in a phone with no OS on it and a bootloop to TWRP.
2) After considering #1, I decided I wanted to install 24A using the KDZ that's available. I followed the instructions by booting in to CM11, ensuring debug mode is enabled then running the batch file as provided (which is pretty darn convenient.) I get up to Step #5 and select "Different Country", then click to start the process. The software indicates that the phone is not connected to the PC. I can see the phone as an MTP device so I know that some level of connectivity is established, and I can also see the "debug enabled" icon in CM11 indicating debugging is enabled.
Without either of the two methods above I'm at a loss for how to proceed. I'd either like to wipe the existing System partition and install a newer nightly of CM11, or I'd like to reload the phone with 24A so I can check out KitKat. Any assistance or insight would be greatly appreciated prior to my moving forward. If I can provide any additional information please let me know and I'll gladly do so.
Solved!
Okay, so I was being kinda' derpy on #2. I forgot to put the phone in to Download mode (unplug USB cable, power off phone, hold vol+ button, plug in USB cable) prior to starting the update.
Another item worth noting: if your phone was previously encrypted it will attempt to decrypt once 24A is installed. Fail the decryption 10 times (no way you could decrypt it anyways, from what I understand) and it'll factory reset, which is exactly what you want it to do anyways. Phone should be fine after that!

Installing Xposed - Stuck at installing TWRP

Hello. I am trying to install TWRP on my S7 Edge, because I want the Xposed Framework. I have the Exynos version.
I am trying to follow this short guide: http://forum.xda-developers.com/showpost.php?p=66277202&postcount=28
I am rooted, I have all the zip files, and I have TWRP Manager installed. However, when I go to try and install it, it says:
"Something is wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?"
If I select OK, I get into the TWRP Recovery, but I am unable to mount /data so I can take a backup.
Is this because of Android 6, that the device is encrypted and it won't mount /data?
I have read places that I need to flash a new kernel and format my user data, but if I have to take it that far, I don't really want to do it.
Please let me know your thoughts on this.
Thanks!

Bootloop after installing TWRP

Hello everyone! New member here.
I'm aware there's another thread regarding this topic but I haven't received a response yet so I'm creating another thread for awareness purposes.
I was flashing TWRP from pure stock but missed a certain step (provided below). When TWRP loaded, it seemed like it couldn't detect any of the partitions on my S7 Edge, so I restarted it to system and ended up in bootloop.
Here is the step from the TWRP guide:
Step: 8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery
Guide: http://forum.xda-developers.com/s7-e...0-0-0-t3334084
After thinking about it, I'm sure step 8 brings you straight to recovery instead of booting into system then restarting manually into TWRP. So now I'm wondering this, what caused TWRP to not detect any of the partitions? In detail, TWRP showed all the partition sizes as "0 MB" when I went to a certain page (forgot what exactly lol). But I will follow the instructions step-by-step and get back to you guys.
Cmindo said:
Hello everyone! New member here.
I'm aware there's another thread regarding this topic but I haven't received a response yet so I'm creating another thread for awareness purposes.
I was flashing TWRP from pure stock but missed a certain step (provided below). When TWRP loaded, it seemed like it couldn't detect any of the partitions on my S7 Edge, so I restarted it to system and ended up in bootloop.
Here is the step from the TWRP guide:
Step: 8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery
Guide: http://forum.xda-developers.com/s7-e...0-0-0-t3334084
After thinking about it, I'm sure step 8 brings you straight to recovery instead of booting into system then restarting manually into TWRP. So now I'm wondering this, what caused TWRP to not detect any of the partitions? In detail, TWRP showed all the partition sizes as "0 MB" when I went to a certain page (forgot what exactly lol). But I will follow the instructions step-by-step and get back to you guys.
Click to expand...
Click to collapse
I tried the link you offered and it doesn't work - so I wonder if you followed the correct instructions to flash twrp?
to avoid bootloops - you need to format data- it will wipe your internal SD Card so make a back up before y ou do this - then yoiu have to flash a DM-Verity File (this is available in the TWRP Thred in the development forum. Now flash the rom you want to flash and when finished you should be able to reboot with out any issues
If you did not do these things, I beleive that is what caused the Bootloop when you tried to reboot the first time
Check out the TWRP Thread in the development section for the Galaxy S7 edge - there are complete instructions there. I hoipe this helps - If you did flash the DM Verity file, then I am not sure what is causing your problem
Instead of creating a second thread the correct procedure is to bump the original one. You can bump a thread once every 24 hours
Thread closed
Moderation Team

Dirty Santa and Restoring From Backups - Suck in some kind of limbo?

So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
This may be an issue with TWRP. When I had my Galaxy S3 rooted back in the day I would have this issue, also with a Nexus tablet I rooted as well. It turns out I needed to flash a specific "fixed" version of TWRP to fix the mount/flash issue. That was a long time ago though, so this might not be the problem, but I thought I would at least tell you my experience.
Sent from my LG-LS997 using Tapatalk
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I beleive you have to do Dirty Santa over again....The steps that is.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
imucarmen said:
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
Click to expand...
Click to collapse
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
biglightbt said:
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
Click to expand...
Click to collapse
I would run the dirtysanta exploit again from the beginning. Your assumption about being stuck in read only seems correct. I'm guessing you might have chosen read only on accident one time when you booted into TWRP and now it's stuck there.
Or you could try using flashfire to flash the TWRP.img
I am having the same issue. I tried doing the DAC mod that enables high impedance as always on. Audio quit working along with the stock music app. Did a restore from after I flashed the konverged kernel. And now no r/w ability and twrp will not mount system unless I check mount as read only. I was able to reinstall supersu from the recovery. But still have the issues.
Only thing I can think of is waiting for a return to stock unrooted method to Come out and re-root.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Hey I was having the same problem and I fixed it myself messing around with a few things I could think of.
Here it is pasted from another thread.
Dinked around with a few ideas and got my problem fixed! Heres what I did.
1. Made a backup of system in twrp just in case.
2. Formatted system in wipe > advanced > and only checked system.
Panicked because I thought I bricked my device, wouldnt boot farther than the lg logo,
(next steps might be unnecessary but I panicked and tried them lol)
3. still had fastboot access so I repeated step 3 in the root method.
4. Reflashed boot2.img
5. Rebooted to recovery with volume- power, release power while keeping volume- at lg for a second then repress and hold power. Yes twice to get to recovery.
6. Restored system backup. (was able to fully boot now but with lag)
7. Reflashed konverged kernel.
And everything is working perfect now and I have my r/w ability and can mount system in recovery without having to select mount as read only.
---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------
You can probably just wipe your system like I said in the previous post then Just restore it. I panicked and did a bunch of extra stuff. I realized that when I did my initial backup of my system, or said that its size was about 126247251477482716MB. So I'm guessing when I did my restore (possibly what happened to yours) that it somehow messed up the system.

HELP URGENT! - I tried rooting my LG G6 (TWRP and Magisk)

I tried rooting my phone using TWRP and Magisk and at some point my OS was deleted.
Got a warning from TWRP satying "No OS" while trying to reboot.
At first the phone wouldnt start at all but now i've ended up with it only launching into TWRP every time i try to launch whether in Recovery Mode or not.
I have no idea what to do and need help. Please.
I believe i need a fresh install of Android but i have no idea how to do this
All you have to do is flash a ROM from within TWRP. It's relatively straight forward.
Pick appropriate ROM for your device: https://forum.xda-developers.com/lg-g6/development
Download the zip file, put it on an SD card or USB-C drive
Insert card/drive into your G6
Click "install" in TWRP, select the zip file
Flash and then reboot
Should be it. Follow the instructions for your particular ROM.

Categories

Resources