i was wondering of theirs some slick way of rooting with a locked bootloader? i was thinking of it was possible to inject and flash patched magisk boot.img by putting the 5X in EDL de and force flashing ether a recovery or a boot img in with the files? im not sure if theirs security on that but im just pulling hairs here.
Related
I found that my moto xt1052 has bootloader unlocking available and im very excited. I like to know if its compulsory to flash recovery to make device rooted. I don't want to install new roms or firmware. Im rooting to control running apps and use some root apps.
I like my phn to be receptive for ota, which isn't possible if i flash custom recovery.
So i want to know if recovery is compulsory to have root status and manage permissions or if i can enjoy root privileged with just unlocking the bootloader.
Thankyou.
Sent from my moto XT1052 using XDA Free mobile app
After unlocking the bootloader, flash TWRP, root, then flash stock recovery back on the phone and run that way.
KidJoe said:
After unlocking the bootloader, flash TWRP, root, then flash stock recovery back on the phone and run that way.
Click to expand...
Click to collapse
hi KidJoe,
how back to stock recovery ?
is it enough to flashing file "recovery.img" by RSD Lite ?
I know rsd lite is made to be more user friendly but I still prefer flashing via fastboot.
Fastboot flash recovery recovery.img
Moto-x said:
hi KidJoe,
how back to stock recovery ?
is it enough to flashing file "recovery.img" by RSD Lite ?
Click to expand...
Click to collapse
RSDLite is overkill to flash just recovery.
Do as @cntryby429 said... use mfastboot to flash recovery. You can use it to flash either TWRP (when rooting) and/or Stock recovery.
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
happimeal said:
Yesterday I thought I bricked my phone. I too also got stuck on the secure boot error 1003 boot loop. It happened when I tried to relock my bootloader with fastboot oem lock. Can anyone explain why that happened and if, after you obtain root, if it's possible to go back and relock the bootloader. I was attempting to get android pay working again, plus it flashes that message about having an unlocked bootloader. Is it possible to re-lock the bootloader after you have root, and if so, what did I do wrong. I finally restored back to factory using the lg bridge tool and download mode, which was a [email protected]#% to get into with a bootlooping phone.
Thanks in advance.
Click to expand...
Click to collapse
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Thank you for a great explanation.
If you ask the people at xposed modules they may be able to do something maybe....
5.1 still displays bootloader unlocked message.
cschmid44 said:
To answer your question, when you root the g4 on marshmallow using chainfire's systemless root, It on the fly flashes a different boot image, thus if you relock the bootloader after rooting the device on the 6.0 marshmallow firmware it will end up with the security error because the boot image has been "modified" and a modified image won't be allowed to boot if the bootloader is locked so the answer is unfortunately no you can't have a locked bootloader and have root at the same time, If you want to relock the bootloader on the 6.0 firmware to get rid of the boot image showing "unlocked bootloader" you should flash the KDZ for the 6.0 firmware in this case H81120i firmware and then go into developer settings and uncheck enable oem unlocking and also make sure you boot into fastboot mode, you can do this via the adb shell. another option to not have the "unlocked bootloader" show every boot would be to go back to the 5.1 firmware which did not have this. I hope this helps.
Click to expand...
Click to collapse
I have installed h815 KDZ files using LGUP. When i reboot it still displays Bootloader unlocked message. I can not use bootloader unlock/lock guide as I have bootloader unlocked.
Any other means to get rid of the message.
bump for way to relock h815
Is it possible to root OnePlus 3T without unlocking bootloader?
I was thinking maybe boot twrp through fastboot boot twrp.img then flash the supersu file without unlocking bootloader or flahing twrp.
I just want to root.
Will i recieve OTA update if this method works?
Will this method work?
Deleted
Just Passing By said:
No. That's no possible. You need an unlocked bootloader or else your phone wouldn't boot after flashing TWRP if it even makes it that far.
Click to expand...
Click to collapse
I was talking about booting twrp not flashing it
I don't think you would be able to flash SuperSU as it isn't signed, even if you do manage to boot into TWRP.
Anova's Origin said:
I don't think you would be able to flash SuperSU as it isn't signed, even if you do manage to boot into TWRP.
Click to expand...
Click to collapse
Looks like I have to unlock the bootloader after all
I have been searching all over the forum but couldn't find. Can anyone tell me if i can use fastboot unlock critical after flashing patched boot.img . I didn't knew about this unlock critical. I followed the method till boot.img after which i was warned here that i cant go back to stock in case of issue and also can i reflash the patched boot image again to get temporary root access? Or should i flash magisk manually from twrp
I was locking my bootloader to try to reroot and pass safetynet. So, I factory reset it, set it up, and then went into the bootloader and typed "fastboot flashing lock". I selected yes to confirm the locking of my bootloader and then my phone rebooted. But now my phone says "Can't find valid operating system" and I can't boot into Android. i was able to unlock the bootloader again but now i don't have magisk installed and I can't even boot into Android to install anything. Is there anything i can do to fix this?
Yes, if you're bootloader is unlocked then you can fastboot flash (or use Chrome web based Android Flash Tool) factory images from https://developers.google.com/android/images
If you want to root extract the boot.img from the zip and patch with Magisk, then fastboot flash boot magisk_patched.img after you boot the phone once on stock unrooted kernel.
Thank you. I did it with the flash tool. Then later, it happened again and I realized I could use the boot.img. I'm glad these Google pixels are noob friendly.
Never lock your bootloader unless you know for a fact that you are on bone stock OEM firmware.