Hey guys:
FIRST OFF: I don't have enough posts in order to stick this in Dev, SORRY!!!
I have read all related posts and stickies but still can't get this sorted out.
Let's get some background... I'm looking at rooting the phone with Magisk. This did not work directly and I was guided by another "how-to" to do it via TWRP instead.
Flashed the vbmeta and TWRP without issues. Booted into TWRP and tried to flash Magisk, which gave me an error at first. It was an old version so I tried a later version, which flashed "successfully," but after a reboot I'm stuck in a loop that reaches the SAMSUNG Galaxy A70 screen, then reboots to show that the bootloader is unlocked, and again and again and so forth...
What did I do wrong? And is there any way for me to fix the boot loop?
Holding in Volume Up does allow me to boot into TWRP so I don't feel as though the phone is bricked.
Any help will be appreciated, preferably that that gets my phone rooted, but even just getting it back to normal will work for me
Thanks in advance,
ShOrTyNoLeGs
Follow this guide
https://forum.xda-developers.com/ga...root-galaxy-a70-twrp-los-17-1-magisk-t4100655
After flashing magisk using twrp, you should reflash stock recovery, Reboot into it then select reboot system BEFORE 1ST BOOT to prevent bootloop.
Factory reset after flashing magisk in twrp will fix all bootloop.
Or follow the guide in my signature for successful root. But you wouldn't have twrp that way, just stock rooted rom
Related
N00b needing some help. It seems I have corrupted the recovery on my rooted G3 VS985. Used TWRP Manager to flash TWRP. Followed the app's instructions, installed BusyBox, applied the KitKat/Lollipop patch, went ahead and flashed. Booting into recovery just gives me a black screen and blinking blue and red LEDs. Since I'm not an expert, I'm a little paranoid to continue.
If I use bump to flash TWRP, will that wipe the corrupted file and flash a working version of TWRP (assuming I don't eff it up)? I've also seen root methods for the G3 that install TWRP as well. If I unroot and reroot with one of those methods with a bum recovery, will I brick my device? Sorry for the n00b questions, and I appreciate the help!
Look at here forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
I have d851, looking for another alternate solution for the corrupted recovery. please help.
Same issue
Same question here also. Updated twrp from twrp manager playstore app now when i enter recovery i get black screen and boot security error. Other than that i can go to download mode easily and can boot my device to android cloudy g3 without a hitch the only problem is that i can no longer use recovery
hey'
every time i boot my phone it bootloop into recavery
what to do?
mega unbrick guide...
timrock7 said:
mega unbrick guide...
Click to expand...
Click to collapse
but in the guide it's you see nothig but a black screen i have recavery https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
it hapen when i exedantly press the istall update of the ota (i had OxygenOS 4.0 and i perss on the update of 4.0.3)
You should never install an update through the phone's update setting while using a custom recovery. The updates are designed to work with the stock recovery only.
If you can still boot into and use TWRP, use it to flash the full ROM of OOS 4.0.3.
If you can't boot into TWRP, try to see if fastboot works and manually sideload a working ROM in.
Otherwise, you're going to have to use the unbrick guide. Your phone doesn't have to be completely bricked to use it. It simply reverts the phone to a truly factory-fresh state (relocks bootloader, wipes everything, etc. - At least method 2 does anyways).
I got stuck in the same situation some time ago, and in order to solve it I had to flash the stock recovery, let it restart, it tried to update (and failed) and then it booted to system again. Hopefully that way you can avoid installing everything again. Once the device boots you can try to update with the stock recovery and revert to twrp if you want.
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Hey guys,
Hope someone can help me or point me in the right direction, I am having serious issues trying to root my 1952-1.
I followed the guide in this post to install TWRP
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
I followed all the guidelines but when i tried rebooting to recovery I ended up in having TWRP splash screen bootlooping, but was still able to fastboot boot twrp.
I then flashed Magisk, it completed and then i booted the phone back up, no magisk was in the app drawer. So i installed the Magisk Manager apk and this told me I was not rooted. Repeated the whole thing and still the same result.
I have also tried patching the boot.img file using magisk but same as before the phone is not rooted, on top of this I have also clean flashed the stock rom but again still not rooted.
Anyone got any ideas ?
Yeah the rooting process can be a little bit frustrating. You will have to copy the original boot.img file to your phone. In the magisk app make sure you enable recovery mode. Then you can patch the boot.img file. Copy it back to your computer and flash it via fastboot. But there is a catch. The phone will be rooted only if you boot the phone through recovery.
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.
Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.
Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!