Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Enigma. said:
Hi,
I'm using CM13 on my LG d620, recently I tried installing SuperSu, and then updating binary, but normal way did not worked so I tried to install it with TWRP recovery, so my phone rebooted into recovery, supersu script automatically stared and installation was successfull. I wiped cahce, even dalvik just to be sure, and rebooted system, but it is now stuck in bootloop.
So I'm just curious if anyone would know if I can somehow fix this problem, maybe through recovery, flashing some script, or in terminal in recovery, with adb... pretty much anything just to avoid flashing new rom again and losing all of data and setings....
Thanks in advance
(btw, i'm on cm13 6.0.1, latest update to this day, twrp 3.0.0, supersu latest version on google play store i think, and also have enabled root access)
Click to expand...
Click to collapse
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Rasgola said:
I end up with same issue now. I could have read this before flashing SuperSu. Now my device is in boot loop. Please help how to fix this without wiping data?
Click to expand...
Click to collapse
Just flash rom from the recovery, thats it. Let me know if it worked for you
Related
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
lopiop said:
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
Click to expand...
Click to collapse
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
tail.adam said:
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
Click to expand...
Click to collapse
i tried to manually reboot into recovery, but it wont enter.
can you use adb sideload if you cannot enter recovery?
lopiop said:
i tried to manually reboot into recovery, but it wont enter.
Click to expand...
Click to collapse
You may need to flash back to stock using Odin then re rooting again.
so i should flash the latest stock rom (4.3) for my region using odin? like this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
fixed using odin, though rather sad that my internal sd got wiped as well
lopiop said:
fixed using odin, though rather sad that my internal sd got wiped as well
Click to expand...
Click to collapse
Glad it's fixed I would recommend not to use apps from playstore to flash recoveries or roms seen nothing but trouble from them.Either use Odin or custom recovery to flash to avoid trouble in the future.
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
kisshell99 said:
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
Click to expand...
Click to collapse
Go back and change partition to read and write in twrp (I think), sounds like you set it to read only if you are getting stuck at that screen. If all else fails I'd try running the RUU then re flashing twrp , but are you s off? I've been s off since sunshine came out (which I highly recommend) and don't know how things work being s-on. Also which version of twrp are you using?
Go read up about how twrp works , that way when you are prompted with things that could prevent you from obtaining root you will know what to do. #4 in the link below might be able to help you... but once again read all the information provided.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
you need to update your TWRP to 3.0.0. Flash it through CMD or sdcard way, reboot to recovery, "Mount as Read Only" message swipe to right. You want it to be that way for an untouch system backup(if you wanted to do). Reflash MM ROM.
got it
The problem was twrp was asking to flash the supersu from itself even after i had flashed the su manually from twrp. i just installed badboyz and then flashed the su and did not accept the twrp option to flash supersu again and it is working again. To add more, i think i even got it dsu with the recent guide posted here which saved me few bucks. I love xda!
I have a T-Mobile LG G5, H830.
Current system is unlocked bootloader, TWRP installed, Rooted with Super SU.
Android version H83020F
Kernal 3.18.31-As hard_v4.1
How do I switch/ install to Magisk? So I can use Android pay?
The guides I found are for unrooted devices and wheren't specific to LG G5 H830 so I wanted to ask here before I try something.
buyslake said:
I have a T-Mobile LG G5, H830.
Current system is unlocked bootloader, TWRP installed, Rooted with Super SU.
Android version H83020F
Kernal 3.18.31-As hard_v4.1
How do I switch/ install to Magisk? So I can use Android pay?
The guides I found are for unrooted devices and wheren't specific to LG G5 H830 so I wanted to ask here before I try something.
Click to expand...
Click to collapse
Go into TWRP, reinstall Asgard kernel (may not be necessary but doesn't hurt) and then flash magisk v12. Reboot into system and open up SuperSU app and go into settings and click on full unroot and restart. In magisk manager make sure you enable magisk hide and don't use built in busy box (using magisk hide and built in BusyBox causes issues with root not showing up).
jeffsga88 said:
Go into TWRP, reinstall Asgard kernel (may not be necessary but doesn't hurt) and then flash magisk v12. Reboot into system and open up SuperSU app and go into settings and click on full unroot and restart. In r showing up).
Click to expand...
Click to collapse
I did what you said and it did not go well.
After many attempts, I was finally able to remove SuperSu and install Magisk and it said it was rooted.
Some how I lost all of my apps, settings, etc.
Then I went into settings and selected the option to restore to factory settings so I could get it to ask me to restore my apps from my Gmail account when it would reboot after factory reset.
HOWEVER, now it only reboots into TWRP recovery.
So I tried reinstalling Magisk and it still only boys into recovery. I tried reinstalling the kernel and it still only reboots into recovery. Then I tried installing the rom, the kernel, and Magisk and it still only boys into recovery.
Why won't it boot? In the TWRP advanced wipe... What options ships be selected to wipe before reinstalling the rom?
buyslake said:
I did what you said and it did not go well.
After many attempts, I was finally able to remove SuperSu and install Magisk and it said it was rooted.
Some how I lost all of my apps, settings, etc.
Then I went into settings and selected the option to restore to factory settings so I could get it to ask me to restore my apps from my Gmail account when it would reboot after factory reset.
HOWEVER, now it only reboots into TWRP recovery.
So I tried reinstalling Magisk and it still only boys into recovery. I tried reinstalling the kernel and it still only reboots into recovery. Then I tried installing the rom, the kernel, and Magisk and it still only boys into recovery.
Why won't it boot? In the TWRP advanced wipe... What options ships be selected to wipe before reinstalling the rom?
Click to expand...
Click to collapse
First of all, flashing magisk wouldn't make you lose any settings so not sure exactly what happened there. Secondly, never use factory reset option from phone when you have TWRP installed. Now to get out of TWRP bootloop go into TWRP, click advanced and then terminal and type the following:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Then reboot into system.
jeffsga88 said:
First of all, flashing magisk wouldn't make you lose any settings so not sure exactly what happened there. Secondly, never use factory reset option from phone when you have TWRP installed. Now to get out of TWRP bootloop go into TWRP, click advanced and then terminal and type the following:
Then reboot into system.
Click to expand...
Click to collapse
Thank you for giving me that terminal code. I am now rebooted and phone is working fine.
Help for install magisk
Can u give me step by step how to install magisk? My position on h830a, rooted, UBL, twrp.
i have xposed, busybox, gltools,
Can i directly flash magisk via twrp or flash asgard first?
Because i can't found asgard yet for H830
Thanks before
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
resutatto said:
So I was wondering...
Today once again I forgot to flash SuperSU after flashing new kernel and I'm left without root. While rooted I was using an app to restart into recovery and it was fine.
As we all know, when you boot into recovery on LG G5 by button combination, you're asked to to wipe everything. My question is, is there any method to boot into recovery without wiping? Without root?
Click to expand...
Click to collapse
If you still actually have TWRP installed, pressing yes when it asks to factory reset / wipe (using the button combo) will not wipe anything, it will just boot into TWRP. Just be sure TWRP is actually installed still, as if TWRP is not installed, then it would wipe your phone saying yes. To check, you can always boot into phone and use
Code:
adb reboot recovery
I'm using TWRP 3.1.0.0, but as far as I remember it wipes anyway. It was on the older TWRP version though. And unfortunately adb command doesn't work for some reason, adb reboot bootloader works.
Anyway, worth trying, I have to do it anyway sooner or later. It would be nice if it wouldn't wipe my apps.
Same problem here. I ran into a bootloop and need to flash the Magisk uninstaller. How to boot into TWRP? With the key combination it always asks me to wipe my phone?!
SOLVED. Just select Yes. This is only a leftover of the Stock recovery. Nothing will be wiped if you already have TWRP installed.
Hi there
I'm totally happy with this device but had an issue today for no apparent reason.
I was using it normally, I put it in my pocket (80% battery) and when I took it out, it was stuck on MI logo screen. Maybe screen wasn't properly blocked or something. But I find all the situation quite shocking since I normally set manual updates for system, and apps, playstore, etc.
I haven't done any flashing opperation recently since I'm not much into this kind of things nor installed any new app recenlty. However the phone was rooted (previos bootloader unlocking) quite a while ago by using "magisk method keeping stock recovery for OTA".
The phone is permanently on with MI logo on screen. I tried using power off button for a long time to see if I could turn it off but it didn't work.
I have access to Fast Boot and to Stock Recovery (3.0).
Is there any way to enter the system again without losing all data? If not, can I recover data before "flashing" anything or before using "wipe all data" option in recovery mode?
Thank you for any possible answer.
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
notoriouslion said:
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
Click to expand...
Click to collapse
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
It happens sometimes for Unknown reasons and Lazyflasher will not harm your device and I would suggest you to flash Another Rom
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
Did you run any root apps ? If /system changes you need Lazyflasher I think. You could alternatively reflash the ROM (without wiping data)