Related
As the title says is it possible to root, install modifications to stock ROM and is there a fast way to revert everything is something go wrong? I'm asking because support for 5X has ended, and I can't permanently unlock bootloader. I don't want to hard brick this phone by mistake and also I don't want just look how this device is being wasted.
So here's some probably noob questions that I want to ask:
1. Can I install TWRP on NO RPMB bootloader and boot it without issues? If so, how?
2. What recovery version should I install 4-core or regular 6-core?
3. Can I root device and hide it with magisk?
4. If an security update appear how to install it since stock recovery is replaced with TWRP?
5. If something go wrong like 2nd death loop how to revert everything? Can I simply flash stock system image in TWRP to "fix" device?
Thanks in advance.
You might try the solution the user in this thread suggested, https://forum.xda-developers.com/nexus-5x/help/rpmb-bootloader-locked-t3481906/page2
So I have to unlock bootloader, then flash TWRP, Super SU, compatible Magisk in one attempt, then I'm ready to go? Will TWRP boot and work like nothing happened?
Sent from my Nexus 5X using XDA Labs
I haven't tried it but based on the steps I would think it should work. It won't hurt anything. It also won't stop the bootloader from locking upon a reboot. But as long as you can unlock it prior to flashing any of the partitions as the reddit thread suggests you could be ok.
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Banan PL said:
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Click to expand...
Click to collapse
I'm running custom kernels just fine with locked bootloader.
CazeW said:
I'm running custom kernels just fine with locked bootloader.
Click to expand...
Click to collapse
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Haven't tried Jolla's multiboot or drivedroid. As long as you can get into fastboot, you can just unlock it again and flash stock (though you will obviously lose everything that's on the device). Haven't tried flashing custom ROMs but as custom kernels are working, I don't see why custom ROMs wouldn't.
negusp said:
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Click to expand...
Click to collapse
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't own a device without RPMB (I got a fairly new refurb), but I've used TWRP/flashed ROMs and kernels successfully with the bootloader locked and TWRP installed.
Alright I'll flash TWRP take nandroid and hopefully device will boot. Can someone give me link to 4-core TWRP, I can't find it?
Sent from my Nexus 5X using XDA Labs
Google 4 core twrp 5x xda. It's in that thread. https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Banan PL said:
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Click to expand...
Click to collapse
Did you unlock and then without rebooting flash the TWRP?
CazeW said:
Did you unlock and then without rebooting flash the TWRP?
Click to expand...
Click to collapse
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Banan PL said:
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Click to expand...
Click to collapse
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
CazeW said:
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
Click to expand...
Click to collapse
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Banan PL said:
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Click to expand...
Click to collapse
So you are not actually getting into recovery at all. Try with different TWRP image.
CazeW said:
So you are not actually getting into recovery at all. Try with different TWRP image.
Click to expand...
Click to collapse
I tried with regular TWRP 4-core modded TWRP and with Multiboot TWRP. Same result.
Sent from my Nexus 5X using XDA Labs
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
JIJOK said:
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
Click to expand...
Click to collapse
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
levone1 said:
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
Click to expand...
Click to collapse
so, can get the image by just unlock the bootloader ? I though root was necessary for that
JIJOK said:
so, can get the image by just unlock the bootloader ? I though root was necessary for that
Click to expand...
Click to collapse
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
levone1 said:
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
Click to expand...
Click to collapse
So, if you was wondering it, no, cant flash it with locked bl.
At the moment Backup ta didnt work, will check that thread
And thanx the help, nice to have you on z1c forum :good:
perfect. thx! i was already wondering, if i had to downgrade my z1c in order to get the recovery back. but now, how i do i flash magisk from here?
when i try to flash, i get an error message saying, that the ftf is in sony elf32 format and that i need bootbridge from @AdrianDC to flash.
anyone ever did that or has a better idea?
just tried it now and ended up in a bootlop
It is many months after this post, but in case this helps anyone, here is the answer.
BootBridge method is pretty simple and it worked for me.
On an un-rooted device. (important)
Just rename magisk zip to "install.zip" put it in a folder called install.
Then with 7zip, create a zip-file, include the bootbridge folders, "META-INF" and "scripts" with the "install folder" you just created.
Then name it "anything_you_like.zip" and flash with TWRP
Basically Magisk is SuperSU alternative and provides SuperSU service for your device. ( roots it )
No problems for me at this point. Working on 14.5.A.0.270 and can also get working on 14.6.A.0.236 but have other problems related to getting compatible recovery on 236.
Eventually in recovery, system mount and unmount break for me, then other mounts eventually fail after trying to get Nanodroid working (My Goal to UnGoogle my Z1c) and can't wipe format or anything (only way to fix is reflash with flashtool)
Deodexed ROM seems to be necessary for Nanodroid and this is causing additional problems for me.
If I have to run with unlocked bootloader, I think AOSP may be a better starting point.
I'm guess there is no root for oreo as of yet for the z2 force? I bout this phone used and it had already been upgraded to oreo. From what I understand I can't downgrade to 7.1 without bricking the phone, I'm I correct? any help would be appreciated.
There is. You can flash TWRP and then Magisk. I take it your bootloader is already unlocked?
sabrdawg said:
There is. You can flash TWRP and then Magisk. I take it your bootloader is already unlocked?
Click to expand...
Click to collapse
Not yet.
I have an unlocked bootloader on Oreo for sprint and want to know if it really is as easy as flashing twrp through boot, flashing the zip in twrp, then flashing magisk. I don't want to brick because there doesn't seem to be a Flash-all to flash back to stock oreo. Please correct me if I'm wrong
xDABZx said:
I have an unlocked bootloader on Oreo for sprint and want to know if it really is as easy as flashing twrp through boot, flashing the zip in twrp, then flashing magisk. I don't want to brick because there doesn't seem to be a Flash-all to flash back to stock oreo. Please correct me if I'm wrong
Click to expand...
Click to collapse
Correct:
Boot (NOT flash) official TWRP
Flash the installer.zip in TWRP
Flash Magisk for root
And there is a Sprint Oreo Flash All for stock - https://forum.xda-developers.com/showpost.php?p=75658956&postcount=65
[deleted]
So i have the Sprint variant and TWRP / rooted so i could SIM unlock the phone. Now I did a Flashall.bat with stock Sprint 8.0.0 image and then did an OTA update to latest build. So I am assuming I am stock with Sprint factory image and factory recovery but my bootloader is still unlocked and I am NOT rooted (SuperSU / Magisk or otherwise). I am not passing SafetyNet check and thus cannot DL Netflix, use Google Pay, banking app complaining. I have a few questions:
Whats the least painful or suggested route to this? I'm assuming SafetyNet fail is due to unlocked bootloader
If I relock the bootloader will this erase data similar to unlocking does?
I read that flashing a custom kernel will fix this by not tripping a Safetynet Flag but what other effects does this do? Will it break OTA?
I do not want to root because I would like to continue receiving OTA updates.
Thanks in advance!
If you relock bootloader safetynet will pass and OTA will work
Marcowe said:
If you relock bootloader safetynet will pass and OTA will work
Click to expand...
Click to collapse
Yeah but does relocking the bootloader on our phones wipe data (factory reset)?
I ask because I heard it does on some Android phones.
Thanks for the reply!
jeffritz1 said:
Yeah but does relocking the bootloader on our phones wipe data (factory reset)?
I ask because I heard it does on some Android phones.
Thanks for the reply!
Click to expand...
Click to collapse
Relocking the bootloader will erase everything, that is the same for all phones with unlockable bootloaders. Magisk hides your unlocked bootloader and helps you pass safety-net while rooted with magisk.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
Relocking the bootloader will erase everything, that is the same for all phones with unlockable bootloaders. Magisk hides your unlocked bootloader and helps you pass safety-net while rooted with magisk.
Click to expand...
Click to collapse
Got it. But Magisk means goodbye OTA's correct?
jeffritz1 said:
Got it. But Magisk means goodbye OTA's correct?
Click to expand...
Click to collapse
Correct
Anyway to not wipe data, still accept OTA's, and pass SafetyNet?
jeffritz1 said:
Anyway to not wipe data, still accept OTA's, and pass SafetyNet?
Click to expand...
Click to collapse
You could boot twrp and flash pantheon. When you want to ota, just flash stock boot img and you can get ota again. Pantheon hides the flags in cmdline that make you fail safetynet. (In your case, the bootloader lock status flag). You could do the same with magisk though as well, you would just have to do a no wipe flash all when you want an ota. (Edit the .bat to not wipe user data)
I heard people brick their phones after flashing magisk. Is that their fault or it's just that magisk doesn't work on this phone yet?
Seems to be the later.
I will test some Magisk versions today.
The manager installs just fine, I downloaded the image from Mi and extracted the boot.img from their firmware. It seems to have been patched just fine with the Magisk app, I haven't flashed it yet, haven't figured out how to get to download mode on this phone. They have a custom boot loader and custom recovery on it. adb reboot download just reboots the phone. I went through the motions of unlocking the bootloader per their instructions but they're having me wait a week before I can unlock the bootloader. I'm hesitant to flash magisk before unlocking the bootloader and making sure I can re-flash with twrp if needed.
Flashing magisk bricks the phone, flashing patched boot.img also bricks the device.
Kingoroot anyone ?
A loot of people brick their phones.. but the sad part is to recover it back.. I dont know why is so hard to unbrick almost everyone Xiaomi phones...
tze_vitamin said:
A loot of people brick their phones.. but the sad part is to recover it back.. I dont know why is so hard to unbrick almost everyone Xiaomi phones...
Click to expand...
Click to collapse
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
astrakid said:
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
Click to expand...
Click to collapse
So did you manage to actually flash or install magisk and obtain root?
donkyshot said:
So did you manage to actually flash or install magisk and obtain root?
Click to expand...
Click to collapse
no, root is not working. but it is easily possible to recover a bootlooping rn8p.
astrakid said:
no, root is not working. but it is easily possible to recover a bootlooping rn8p.
Click to expand...
Click to collapse
Such a shame, I can't believe there's no custom recovery and root available yet for such a popular device. Let's wait and see.
Hey,
This guy here at the twrp thread says that he managed to root with Magisk 19.3.
rrk said:
Hello all,
Can somebody tell me how to replace Chinese ROM with Global one.
I am waiting now for bootloader unlock, abt 100 hrs remain, thanks in advance
Click to expand...
Click to collapse
Is this possible yet? Looking to buy this phone.
razerphynx said:
Is this possible yet? Looking to buy this phone.
Click to expand...
Click to collapse
Should be quite similar to before, but if you flash preloader & lk, you can recover from these bricks. That said, I've never had magisk bricking it for me.
I am on MIUI 12, Android 10, Chinese Beta Rom and I have Magisk installed as well...
Any update on a fully working method to root our device?
Android 11, custom ROM, CFW
astrakid said:
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
Click to expand...
Click to collapse
There is an easier way.
I had twrp as recovery and when i flashed magisk v20 zip it bricked both the normal system and recovery
It was saying "The system has been destroyed"
So i was doing random stuff and found the solution
1) go to fastboot
2) from pc execute the "fastboot flash recovery twrp.img" you probably know how to install twrp
3) then boot to recovery
4) enter password and allow modifications
5) go to reboot > System
Thats how i did it.
I have not tested with other custom recoveries
Hope I help
nakedowl said:
I will test some Magisk versions today.
Click to expand...
Click to collapse
Did other versions of magisk work