Related
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Joselito.98 said:
Hi I'm new, how have I got an acatel Idol 3 (6045 Y)
Well I'll have Idol 3 updated to version 6.0,
I'd like to know how I can go back / downgrade to Android 5
I've already done the hard reset, the cache wipe, but nothing stays the same
Greetings and thanks
Click to expand...
Click to collapse
You need to downgrade, only with rom if someone have it.
persona78 said:
You need to downgrade, only with rom if someone have it.
Click to expand...
Click to collapse
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Joselito.98 said:
With adb? Because it does not work for me, remote command unknown
I've tried everything, that error happens when flashing twrp
regards
Click to expand...
Click to collapse
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
persona78 said:
Is because with the update you loose bootloader commands ( fastboot)
So, you need to root, after root install Rashr from Google play, with Rashr you can flash twrp, with twrp you can flash aboot.img from 5.0.2 version with a flash zip then you recover bootloader commands like this.
Click to expand...
Click to collapse
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Joselito.98 said:
The problem is there, I want to twrp to do root.
The question is not to get recovery custon, but root
I tried it with adb, but I got the same error ...
regards
Click to expand...
Click to collapse
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
magus7091 said:
What he's saying is that without fastboot the only way you can flash a ROM is through TWRP. You need to root and then install TWRP, and then install the ROM. Also, if you're doing any kind of reflashing; to do so without a custom recovery is risky at best.
Click to expand...
Click to collapse
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
persona78 said:
You get this because you don't have fastboot any more!!
Do you get this?
You must find another way to root, maybe kingroot!
Click to expand...
Click to collapse
If I have adb and fastboot, with kingroot not working
Now I make a video
Joselito.98 said:
That's it, but I mean I can not flash the twrp nor the root, I get: unknown remote command
Click to expand...
Click to collapse
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
kt-Froggy said:
Look at this thread to get TWRP and root. Works perfectly; I went through this procedure several times on 6045I. Just read carefully to understand the steps; there are couple of other threads that are linked from this one.
Click to expand...
Click to collapse
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Joselito.98 said:
Now take a look, and in step 1 put the twrp but only for idol 4, not for mine
Click to expand...
Click to collapse
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
But does it work with android 6?
And if I get the same error?
Hello ? Can someone help me please
kt-Froggy said:
Yes, the TWRP steps are described for Idol 4, but the process works perfectly fine for 6045. That thread is a compilation of steps from few other threads that are linked from there; some may not be specifically for our model, but they work. Just read carefully and make sure you understand. It's quite normal on XDA, when you find some info from another device's forum, and adapt it to your device. Like I said, I did this myself on 6045I at least 3-4 times, while fooling around with the phone after I got it.
Click to expand...
Click to collapse
Hello, I followed all the steps of this post, but there is a problem, idol 3 6045Y, there is no download mode, as you did
regards
PS: Thank you
Hi, why are not I going? I tried the sahara and firehose
I do everything well does not come out, no error, but at the time of starting the recovery leaves the factory.
I tried that twrp and also several more, but being all ok, I do not know why it's not going
regards
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
And what about the flashtool?
regards
Joselito.98 said:
I have tried the Sahara again in every possible way.
And if with the sahara I try to put a rom with android 5?
Click to expand...
Click to collapse
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
kt-Froggy said:
You can't use Sahara & Firehose for flashing the ROM. It will only let you to flash the recovery (TWRP).
You have to understand that you need to go through several steps here...
1. Your goal is to downgrade to 5.x. You can't flash a 5.x official stock ROM, because the only way to flash stock is to use Mobile Upgrade Q, and you already got an update to 6.0 for your phone. Your only choice is to find a 5.x ROM that can be flashed from TWRP.
2. So, you need to install TWRP. I recommended using Sahara & Firehose, because this method works for me every time with no problems. I pointed you to the thread with ALL the information you need. If it doesn't work for you, I don't know why. Maybe you don't have the proper drivers installed? You need the drivers before you try doing anything with your phone from your PC. Maybe you have a bad USB cable or port? Maybe something else? I have no idea... I simply told you what works for me 100%.
3. There may be another way, if you somehow root you phone first, then flash TWRP using Rashr, for example. But I don't know how to root it. I only rooted it by flashing SuperSU, after I already had TWRP installed, so I can't help you with this...
Most importantly, you need to understand what you are doing, why you need to do specific steps, and the purpose of all the tools you use...
Click to expand...
Click to collapse
Here you have all the procedure "well done" of how to download twrp with the sahara, and you will see that it does not work ...
https://vimeo.com/210311115
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do
Hi all
ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago,
my friend wanted to see if my phone could be charged with a dash charger,
where others wouldnt
my battery was already low and overnight it ran out
and when i was charging it and tried to boot
it ran into the dm-verity in eio mode issue
apparently the device is corrupt now
so i want to flash it, but it wont work
probably bcs the device is still locked
and for the life of mine, i dont know how to unlock it
my phone only has fastboot, recovery, adb, sd options now
so .apk wont help i think
i did manage to get twrp on it
who knows how i can get it unlocked?
and perhaps how to flash my phone all together?
i have the firmware from asus themselves
source code too
but their unlocker is in .apk, so of little help
Hi, is there anyone have their AZ3U with unlocked bootloader?
Thank you
bbmuje said:
Hi, is there anyone have their AZ3U with unlocked bootloader?
Thank you
Click to expand...
Click to collapse
I'm in the same situation...for some reason, I can't even get the Bootloader interface or the Composite ADB interface drivers to run properly on Win10.
There is a way to, supposedly, unlock without the .apk tool (that no longer seems to work).
fastboot flash all unlock_ ZU680KL.raw
I have no idea if that works at all, but all you'd need is a working fastboot interface...
Dm-verity
dennizunsal said:
Hi all
ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago,
my friend wanted to see if my phone could be charged with a dash charger,
where others wouldnt
my battery was already low and overnight it ran out
and when i was charging it and tried to boot
it ran into the dm-verity in eio mode issue
apparently the device is corrupt now
so i want to flash it, but it wont work
probably bcs the device is still locked
and for the life of mine, i dont know how to unlock it
my phone only has fastboot, recovery, adb, sd options now
so .apk wont help i think
i did manage to get twrp on it
who knows how i can get it unlocked?
and perhaps how to flash my phone all together?
i have the firmware from asus themselves
source code too
but their unlocker is in .apk, so of little help
Click to expand...
Click to collapse
From my experience -
You'll need to first unbrick your locked phone with the dm-verity in EIO mode. YT has video with a procedure that worked for me with a couple of tweaks which I posted a reply to. It uses some images and ADB in sideload mode.
Link to YT video tutorial that worked for me:
See my comment under John C in the YT video for slight differences for my experience.
Bootloader locked for this phone is an issue from ASUS. It no longer works and is not worth pursuing IMO. However you don't need the bootloader unlocked to install TWRP and to gain Root - contrary to many posts here in XDA.
I successfully installed TWRP via ADB and my bootloader is still Locked. See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend. Also helpful to get an SD card format it for FAT-32 (not ex-FAT).
You'll need to acquire the TWRP image for this device. You'll also need to acquire Magisk flash Zip and the Magisk apk images. Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.
After you gain TWRP install flash Magisk from Zip.
Hopefully this helps you and others. YMMV of course and proceed at your own risk. It is best to do your own research, and gather all of the files you need ahead of time.
jrchester said:
Dm-verity
From my experience -
You'll need to first unbrick your locked phone with the dm-verity in EIO mode. YT has video with a procedure that worked for me with a couple of tweaks which I posted a reply to. It uses some images and ADB in sideload mode.
Bootloader locked for this phone is an issue from ASUS. It no longer works and is not worth pursuing IMO. However you don't need the bootloader unlocked to install TWRP and to gain Root - contrary to many posts here in XDA.
I successfully installed TWRP via ADB and my bootloader is still Locked. See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend. Also helpful to get an SD card format it for FAT-32 (not ex-FAT).
You'll need to acquire the TWRP image for this device. You'll also need to acquire Magisk flash Zip and the Magisk apk images. Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.
After you gain TWRP install flash Magisk from Zip.
Hopefully this helps you and others. YMMV of course and proceed at your own risk. It is best to do your own research, and gather all of the files you need ahead of time.
Click to expand...
Click to collapse
Hi, tried to find post introducing root with bootloader locked in this forum but with no luck. Could you kindly share a link to that post with me? I also wonder which YouTube video tutorial you watched is specifically about the bootloader unlock on Zenfone 3 ultra. Thank you in advance!
kenarp said:
Hi, tried to find post introducing root with bootloader locked in this forum but with no luck. Could you kindly share a link to that post with me? I also wonder which YouTube video tutorial you watched is specifically about the bootloader unlock on Zenfone 3 ultra. Thank you in advance!
Click to expand...
Click to collapse
Updated my OP to add link to the YT video, which is about unbricking the Zenfone 3 Ultra.
Other info my post discusses how I obtained root (not on YT video) without modifying bootloader.
As always, "Use at your own risk" and YMMV.
Good luck.
@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...
neophilos said:
@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...
Click to expand...
Click to collapse
“Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.” This part from jrchester's reply didn't work for me. The bootloader is locked which prevents me from doing any fastboot flash operations, have no idea how jrchester achieved.
I have no idea what could be helpful from the YouTube video he posted either, I just want to either unlock the bootloader or (if possible)flash the recovery+moded rom with the bootloader locked, while my phone is not bricked.
I also had no luck to find any posts as he mentioned "See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend."
neophilos said:
@kenarp – did you manage to get root without using the unlock tool? If yes, could you share your steps (and what may have went wrong during your procedure) in a little more detail than jrchester did? That would be great!
I am somewhat reluctant to simply give it a try because I already spent days with this some time ago, without any success...
Click to expand...
Click to collapse
See my previous posts on XDA developer forum. Two separate Ultra 3 issues are discussed, both Unbricking phone (Yt link in OP added with procedure given), and then root and TWRP without unlocking bootloader. Both completed successfully. Still using my Ultra 3 today (rooted and still bootloader locked) with no issues. No special unlock tools used other than listed procedure with ADB Sideload, TWRP, and Magisk. Use at your own risk and YMMV.
kenarp said:
“Basically procedure is factory reset, boot into recovery mode, fastboot flash recovery TWRP image.” This part from jrchester's reply didn't work for me. The bootloader is locked which prevents me from doing any fastboot flash operations, have no idea how jrchester achieved.
I have no idea what could be helpful from the YouTube video he posted either, I just want to either unlock the bootloader or (if possible)flash the recovery+moded rom with the bootloader locked, while my phone is not bricked.
I also had no luck to find any posts as he mentioned "See other OP posts here on XDA for root of this device. You'll find a procedure that used TWRP and SuperSu, however I used TWRP and Magisk and that is what I recommend."
Click to expand...
Click to collapse
Thanks for your reply. As far as I understand the info on this in other threads about this non device-specific question the verity check at boot will not allow booting from an altered boot partition (compared to OEM). If you flash Magisk it will always alter the OEM boot partition which is why the bootloader needs to be unlocked to allow for the boot to happen.
@jrchester, I guess you are quite lucky that your phone works with root eventhough the bootloader status says locked. However, this can probably not be reproduced from what I know and from what @kenarp reports.
Definitely incorrect. See more recent posts of mine on another XDA Forum Developer thread. Two other users recently confirmed the exact same process worked for them.
Ref: https://forum.xda-developers.com/t/...zenfone-3-ultra-zu680kl.3565595/post-86634507
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk
Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?
Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs
sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.
QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.