hey there,
so i had my lgg6 h870 rooted 100% fine, until i yesterday stumbled upon the bug that mobile hotspot turns itself off. so i troubleshooted and i could outsorce that my root is doing that. so i deinstalled magisk and then reset my phone via adb. everything worked perfectly. then i tryed re flashing twrp and it wouldnt at first but then it did after turning on uzb debugging. so then i wanted to boot into twrp, but it only showed me the twrp logo and then booted up into my system as if nothing ever happened. then i deleted EVERYTHING (system, dalvik, cache,.....) and then the fun began, i had no OS on it, so i flashed a lg g6 h870 stock rom onto it and it sayed it worked, so i rebooted to system but i ended up in twrp. so i rebooted again to system and ended up in twrp. so i tryed using adb to get into fastboot, but not even that works. so now im out of ideas what to do, and i hope someone can help me out with this.
thanks
Related
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.
Not really sure where I should have put this but have a weird issue. I have a droid turbo xt1254 that I have rooted and flashed many times. The most recent, today, I accidentally did a full system wipe and when I went to reflash the rom already in twrp, it gave me an error.
I then tracked down cm13 for my phone, which had worked previously and reinstalled it but every time I reboot the phone, it goes straight into twrp.
I have found that If I reboot into the bootloader, I can choose factory and whichever rom I have installed works until I reboot.
Can anyone help me stop this and get it to boot straight into the rom?
I had rooted my device with Magisk. The phone got stuck in a boot loop.
I decided to say "Screw it" I'm going to stock. I reflashed stock using adb. However when I booted back into the OS, apps are still detecting root, I have cleared the application data and it still finds it.
I have booted to TWRP and ran the uninstaller but it still seems to be there.
Any advice?
Try flashing boot.img . Guess you only flashed system
Hey, I recently got my Poco X3 NFC. I unlocked the bootloader, flashed a custom ROM and recovery, everything seemed fine. After installing Magisk (flashing the new "apk") from TWRP recovery, everything went fine too. Later I decided to switch to another ROM and I did a FULL wipe of pretty much everything except the stuff necessary to run the phone. I then flashed the new ROM and it got stuck at the yellow POCO screen, powered by Android and the padlock. I then rebooted back to TWRP and flashed the apk again, the phone booted with no problems whatsoever. The "Uninstall Magisk" button in the manager was completely broken, complete uninstall did nothing. I decided to uninstall it again from TWRP using the apk and renaming it to uninstall.zip. It successfully uninstalled, and after booting the same thing happened. Just stuck at the POCO screen. Then I flashed Magisk again, and it booted fine. I can't get my phone Magisk-free without it bootlooping. I tried flashing the stock boot.img, the ROM's boot.img, pretty much everything and nothing worked. Anyone knows what's happening?
same problem with samsung galaxy s8, and now it got worse on me after trying new rom, now my phone is stuck at recovery and doesn't work at all even the samsung repair center said the motherboard should be REPLACED, so I would recommend that you choose the most stable rom and keep it and stop changing your phone software or it will ne soft bricked like mine !
Alright, thanks. I guess I'll just keep the current ROM with Magisk. It'd be nice to have a phone booting without it though.
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
Reflash the rom but erase everything then flash.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
You needs msmtool to restore the phone to a stock image. Search in xda and follow the steps, its easy