Hi. Nobody could answer my Reddit thread, so I figured out I would ask here instead.
I'm using this guide: https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
My device is already rooted (on HavocOS - a big mistake because it's unstable and not fully functional), with the Big cluster disabled, TWRP 4-core recovery and the ElementalX kernel.
I want to install the latest stock, unrooted ROM because it's more secure (I suppose), stable and probably faster than any custom ROM. At the same time, I need ElementalX to underclock and 4-core TWRP in case of emergency.
I have 3 questions:
The guide tells me to install a modified boot.img that disables forced encryption. Why would I have to do it? I don't want to root it but at the same time, there's no RPMB - the bootloader locks itself with each restart. Do I need the modified boot.img anyway? Nobody explained thus far why it is needed.
As mentioned, the device locks its bootloader each time it's restarted (no RPMB). This guide https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 says that locking the bootloader when custom recovery is installed can result in a brick. I have custom recovery installed right now. Should I flash stock recovery with a boot.img before rebooting to be safe?
Can custom kernels be flashed through TWRP with a locked bootloader or should I do it through fastboot?
Oh, and by the way, I've been using my Nexus 5X with occasional restarts but no bootloop for 2 years (after replacing the motherboard with a used one that I bought, but it doesn't have RPMB). When it restarted on its own, I panicked and disabled the Big cluster using the fix but I think the restarts are caused by the unstable HavocOS ROM with an incompatible (too recent) vendor image.
Related
I noticed that when using the last dev preview for my N7 2013, it keeps killing TWRP and putting back the stock recovery. Now the final release does this. If I flash TWRP again, it just gets overwritten after a normal boot then back to recovery.
Why? Is there a way to stop this? This is the first time I've dealt with this. Nothing else does this to me. I haven't found a clear answer yet to this while searching this site or others.
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
rguilamo said:
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
Click to expand...
Click to collapse
Well it is just 5.0 that does this.
Since I posted this there is a sane reason for them to do this - it might be the way they enforce the factory reset protection. It has to use their recovery to do so. Still annoying.
But thanks for a workaround, that it simply is the kernel, or boot image. That and I want root
You can try Chainfire's CF-AutoRoot, It modifies Boot.img so root is granted in boot time, I already had a custom kernel when I rooted, but you can try to root first and see if it stops auto-writing the stock recovery.
Here's the download link: http://download.chainfire.eu/347/CF-Root/CF-Auto-Root/CF-Auto-Root-flo-razor-nexus7.zip
Extract it, and run root-windows.bat (or the one suitable to your OS) while in fastboot.
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Shoruk3n said:
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Click to expand...
Click to collapse
1. If you switch roms, always do a clean install (wipe all partitions) . If you want to get rid off all the mods wipe system and flash the same rom + gapps + root. You won't loose data since you are only modifying the system partition.
2. Stock recovery by Oneplus is as if says stock, you littery can't do anything with it apart from upgrading your OOS, wiping cache partitions and doing a factory reset. I do recommend the TWRP provided by Bluspark since that seems to be the only one I tried without any issues whatsoever.
3. Magisk is the new root method in my opinion, it supports Magisk modules which simply are mods that can be installed and removed with a single click (reboot required tho). You can compare it to xposed but very limited when compared.
4. Boot.img is your kernel, never flash standalone img files apart from TWRP since the kernel modifies more the only the boot img. Always flash the full zip.
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.
My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!
I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.
There's no newbie guide anywhere. https://github.com/tkchn/daisyinstall gives bootloops.
Flashing PE and LineageOS give error 7. Flashing RR gives bootloop.
Conflicting guides and comments everywhere. Some guide says flash aboot, some dont. Some say flash dm verity, some say flash forced encryption disabler. Some skip both. Switching current slot in TWRP gives 'the system has been destroyed'.
Is there a guide out there showing how to flash custom rom, twrp and magisk from start to finish? I use offlain twrp.
I have tried:
_Flash twrp alone works
_Flash magisk alone gives bootloop
_Flash edxposed gives bootloop.
_Flash twrp and magisk on stock with slot switching gives 'system destroyed' message.
_Cant flash any custom rom without error.
I'm so frustrated. I dont even want to root but stock has kernel wakelock that kills phone battery after 3 hours of standby. I'll sell this phone if I still cant figure out how to root it. Honestly have flashed fashboot no less than 50 times. I bought this phone cus its the only small phone around but the time spent on rooting has already cost more than the phone.
That's the process I use for custom ROMs. Magisk has to be flashed after first boot into system.
kingd421 said:
That's the process I use for custom ROMs. Magisk has to be flashed after first boot into system.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 I followed that guide to root stock.
Were you able to figure it out?
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!