Hello.
I was trying to complete https://forum.xda-developers.com/xperia-m5/development/kernel-stock-marshmallow-kernel-root-t3453072 this guide to keep all my drm keys. But I got a bit lost in moment when I need to "flash_dk". Then I installed twrp recovery and after it found out how to pass through Dk thing. But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Jeffrrey said:
But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Click to expand...
Click to collapse
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Everlastingman said:
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Click to expand...
Click to collapse
Flashing magisk through adb sideload worked. Thanks for your time, I don't know how to close threat
Related
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
Rooting in MM includes flashing modified boot.img (modified kernel). I guess that's what you are missing. There is the modified boot.img for root in MM dev edition thread or I can recommend you the flar2 elementalX 6.0.2 kernel that I am using right now and is far better on battery life/performance vs the stock one. Cheers!
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
TheEarman said:
Thanks. I had read something about a modified boot.img but thought it was only for the GPE version. I'll give it a try. Thanks for the help!
Click to expand...
Click to collapse
let us know what the outcome is. Been looking for a thread on rooting unlocked/dev edition and was unable to find any
TheEarman said:
I have a One M8 DevEd which I have just upgraded to Marshmallow (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4). After the ugrade I flashed TWRP 2.8.7.0. I rebooted into TWRP. It asked me if I wanted to leave the System R/O and I said NO.
I then Installed Beta-SuperSU2.65 by flashing the Zip from TWRP Install. It flashed fine. It asked me if I wanted to install SU to rootbefore rebooting and I said NO as I had read that it can get the phone stuck in boot loop.
However, when I did reboot, it got stuck in boot mode...
I reflashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.
Am I missing a step? Any suggestion? Thanks!
Click to expand...
Click to collapse
I was able to root properly, with proper binaries, by using the method described here (I was missing the boot.img flashing step, as indicated by High_voltage): http://forum.xda-developers.com/htc-one-m8/development/kernel-unlocked-developer-edition-t3262823. Problem solved. Thanks!
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
jshamlet said:
This isn't a bad question, as the newer 2.6x SU betas can alter the boot image of some devices during the ZIP install. I was actually about to ask whether or not that included the M8's boot image, but it would appear the answer is no.
Click to expand...
Click to collapse
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
ckpv5 said:
I was running 2.64 and now I'm running SuperSU 2.65 and about to test 2.66 later on stock boot.img for MM (I'm on stock MM 6.12.709.4 ROM)
There is no need for a patched boot.img
SuperSU will detect boot.img
If it is stock boot.img, it will install root in systemless mode
If it is a patched boot.img, it will install root in system mode
The point is I have no problem to root a stock MM ROM with 2.64 and later versions
Click to expand...
Click to collapse
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot. While those were for the gpe version i shouldn't think it matters.
Your suggesting its possible without modifying the boot.img? If so are there any repercussions vs using a patched boot.img?
ShinAkira00 said:
The posts i've read point to the possibility of getting stuck in a bootloop or worst case bricking the device if its attempted without a modified boot.
Click to expand...
Click to collapse
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
redpoint73 said:
You should always do a TWRP backup before making major system changes, including root. Doing a TWRP backup mean you can simply revert to your backup if you run into such issues.
A bootloop or no boot (into OS) are always possibilities when modding the phone. I doubt a real brick is possible just by attenting root. If you read this somewhere, my guess is the person just meant a bootloop or no boot, not a true brick (which by definition is not recovery except by opening the phone).
Click to expand...
Click to collapse
cool, thanks for clarifying.
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.
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img
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!
I have an ATT LG V40 on android 8.1. The phone is already rooted and has magisk installed. I have been unable to get TWRP installed so I can flash a custom rom. It seems that being on android 8.1 is causing issues, but I am not really sure. I followed this guide: https://forum.xda-developers.com/t/twrp-lg-v40-judypn.3970111/ and when I send the comand to flash TWRP in the command window is says the flash is finished and my phone boots up, but it doesn't seem to do anything. Any help would be greatly appreciated, thanks.
You need to use LGUP to get to 9
Noob question but did you installed and tried magisk manager(I bet you already have) and flashify(searchable on Google) (magisk manager grants root to flashify and flashify installs twrp from storage)?
Are you certain that you're booting in to recovery? Many phones have an advanced reboot menu option on the developer settings. If yours doesn't I recommend an app like Simple Reboot.
If you're not certain that it's installing the recovery correctly have you just tried installing TWRP.zip from Magisk?
dn.34 said:
I have an ATT LG V40 on android 8.1. The phone is already rooted and has magisk installed. I have been unable to get TWRP installed so I can flash a custom rom. It seems that being on android 8.1 is causing issues, but I am not really sure. I followed this guide: https://forum.xda-developers.com/t/twrp-lg-v40-judypn.3970111/ and when I send the comand to flash TWRP in the command window is says the flash is finished and my phone boots up, but it doesn't seem to do anything. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Which 'command', specifically, are you typing in when you say you are 'when I send the command to flash twrp'? The only command in those directions are to boot twrp, not flash it.
After you boot it, then you need the advanced section so you can recovery ramdisk, which will inject twrp into the current boot partition (and it keeps boot intact).
If you want to use current aosp roms, then follow the 'metadata' sections as you'll need that version of twrp for those roms.
cheers