It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
ali4ek said:
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
Click to expand...
Click to collapse
Not sure I got any advice since you've already tried what I would've suggested. I sideloaded SuperSU-v2.79-201612051815.zip by booting into TWRP through fastboot and it worked for me. I read in another thread that some people were stuck on the nvidia logo for a good 15 mins and then it was fine. How long did you wait? I flashed TWRP after rooting because flashing it through fastboot wouldn't stick, but I can't see how that could matter.
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Sokraates said:
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Click to expand...
Click to collapse
I've been following the threads throughout the day and it seems to be a common problem after using flashfire. There's a thread on a potential fix here:
https://forum.xda-developers.com/shield-tablet/help/k1-fix-able-to-charge-tablet-ac-adapter-t3554261
Related
So I was on Marshmallow, got tired of the excessive battery drain and SD card limitations, and flashed back to Lollipop. I was able to flash TWRP, but then when I rebooted, I was told there was an update, so I reflashed the stock recovery and updated. Now I can't get back to TWRP. I flashed it repeatedly and every time I reboot into recovery, it's still on stock. I've lost root and nothing I've tried works. WTF?
Nevermind, I just tried flashing TWRP 2.8.7.1 and it worked. 2.8.7.3 apparently does not anymore.
Can a mod delete this?
so yesterday, I decided to root my tablet. Everything was working nicely after I rooted and downloaded clockwork mod. The whole problem started when I used an app called quick boot, and I booted into recovery mode. As it was rebooting, it asked for permissions(I accepted obviously), and I haven't been able to get past the logo screen ever since. I tried wiping everything, but it still doesn't work. Any solution to this?
Reflash stock firmware with odin should probably work.
I managed to fix it by using the adb sideload thing in twrp.
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude
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