Installed stock 7.1.1 (nmf26f) from google.
Flashed twrp 3.0.2.3
Booted into twrp
All working ok.
Boot into android and setup all goes well.
reboot into twrp and all I get is the "No Command" screen.
Ive used http://forum.xda-developers.com/showpost.php?p=69945075&postcount=952 for the boot.img and repeated the above but still "No Command" screen.
Also tried to modify build.prop but it doesn't stick on reboot.
anyone help ?
flash twrp again
Enviado desde mi Nexus 6P mediante Tapatalk
It may be an encryption issue, but I'm really not sure. I'm still running DP2 because I'm on Verizon and iffy about flashing the new image. But I did have the same issue on the developer preview and modifying the boot image did work for me. It could be the boot.img you're using. They way I would get TWRP to stick was actually by flashing Supersu which I think modifies the boot.img. If you're interested in rooting, I'd try doing that and see if it sticks
5haddex said:
Installed stock 7.1.1 (nmf26f) from google.
Flashed twrp 3.0.2.3
Booted into twrp
All working ok.
Boot into android and setup all goes well.
reboot into twrp and all I get is the "No Command" screen.
Ive used http://forum.xda-developers.com/showpost.php?p=69945075&postcount=952 for the boot.img and repeated the above but still "No Command" screen.
Also tried to modify build.prop but it doesn't stick on reboot.
anyone help ?
Click to expand...
Click to collapse
Twrp will be overwritten at first boot. To maintain it, you have to flash SuperSu.
Cheers
Sent from my interstellar 6P!
5haddex said:
Installed stock 7.1.1 (nmf26f) from google.
Flashed twrp 3.0.2.3
Booted into twrp
All working ok.
Boot into android and setup all goes well.
reboot into twrp and all I get is the "No Command" screen.
Ive used http://forum.xda-developers.com/showpost.php?p=69945075&postcount=952 for the boot.img and repeated the above but still "No Command" screen.
Also tried to modify build.prop but it doesn't stick on reboot.
anyone help ?
Click to expand...
Click to collapse
I'm seeing the same on a Pixel and Pixel XL. Re-fastbooting twrp will load TWRP. Re-flashing SuperSU doesn't help. On the next attempt to enter twrp, "No Command" reappears. At that point, I can hold the power button and tap volume up to bring up the factory recovery, but TWRP is gone.
snovvman said:
I'm seeing the same on a Pixel and Pixel XL. Re-fastbooting twrp will load TWRP. Re-flashing SuperSU doesn't help. On the next attempt to enter twrp, "No Command" reappears. At that point, I can hold the power button and tap volume up to bring up the factory recovery, but TWRP is gone.
Click to expand...
Click to collapse
Had this problem before. I don't know it will work with you, but after flashing TWRP, I used fastboot reboot recovery command from the command prompt and TWRP stuck.
snovvman said:
I'm seeing the same on a Pixel and Pixel XL. Re-fastbooting twrp will load TWRP. Re-flashing SuperSU doesn't help. On the next attempt to enter twrp, "No Command" reappears. At that point, I can hold the power button and tap volume up to bring up the factory recovery, but TWRP is gone.
Click to expand...
Click to collapse
Spoke too soon. Problem solved. I should have read the instructions more carefully. This is for a Pixel with the new partition layout, so it may not apply to the 6P. My 6P is still on MM so I can't comment.
The issue with the two Pixels:
Chainfire's post linked below describes the proper procedure. In short, you fastboot boot the twrp image, then you must flash the twrp.zip to get it to stick. After that, you reboot into recovery and flash SuperSU.
TWRP + SuperSU.ZIP
See Dees_Troy's post linked below for the links to download both the twrp img and zip files.
- reflash stock boot.img
- fastboot boot /path/to/twrp.img
- TWRP install twrp.zip
- reboot into recovery
- TWRP install supersu.zip
You will end up with both SuperSU and TWRP.
https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Click to expand...
Click to collapse
snovvman said:
Spoke too soon. Problem solved. I should have read the instructions more carefully. This is for a Pixel with the new partition layout, so it may not apply to the 6P. My 6P is still on MM so I can't comment.
The issue with the two Pixels:
Chainfire's post linked below describes the proper procedure. In short, you fastboot boot the twrp image, then you must flash the twrp.zip to get it to stick. After that, you reboot into recovery and flash SuperSU.
Click to expand...
Click to collapse
You're right. It doesn't apply to 6P. After flashing twrp, just install SuperSu zip and TWRP will remain.
Sent from my interstellar 6P!
Related
Hi,
In order to update my phone to oxygenOS 2.2. I flashed oxygenOS 2.1.1 full rom and installed the OTA update for 2.2. Because of this the phone switched back to stock recovery. So I tried to install TWRP recovery through fastboot. The installation was successful but after reboot, it looks like the phone is keep switching back to stock recovery. I have tried this many times but same result everytime.
Note1: I did turned on the USB debugging before this.
Note2: Bootloader is unlocked.
Any help would be great. Thanks in advance!!
When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery
Akhil701 said:
When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery
Click to expand...
Click to collapse
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.
Dreckk said:
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.
Click to expand...
Click to collapse
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.
pitrus- said:
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.
Click to expand...
Click to collapse
Did that many times, but it keeps getting entering in the default recovery.
What happens when you boot twrp with fastboot instead of flashing?
Also probably shouldn't flash an ota 2 versions different than the full. If that was the full version you already had, should have flashed 2.1.2 ota then the 2.2.0 ota.
I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.
Chris_el said:
I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.
Click to expand...
Click to collapse
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.
khaos64 said:
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.
Click to expand...
Click to collapse
Hmm i'll give that a shot when I get home from work. Thanks.
Chris_el said:
Hmm i'll give that a shot when I get home from work. Thanks.
Click to expand...
Click to collapse
fastboot boot /path/to/twrp
then Swipe to allow modifications!
Yash98 said:
fastboot boot /path/to/twrp
then Swipe to allow modifications!
Click to expand...
Click to collapse
I get the error "FAILED remote: dtb not found'
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
x0nar said:
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
Click to expand...
Click to collapse
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You have to install marshmallow firmware first.
Best option would be to go back to the working TWRP version, flash oxygenos, reboot to Oxygen once, flash new recovery in fastboot, reboot recovery, flash rom
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't know if this does anything different, but here's what worked for me
1. Ensure that device enters into fastboot mode
2. "fastboot flash recovery recovery.img"
3. **IMP** After your flashing is successful, directly enter the device into recovery mode by pressimg Power (+) Vol Down button.
4. Now a TWRP prompt shall appear asking your permit for modifications, swipe yes.
Note that: I'm not sure if this makes a difference, but earlier I rebooted after Fastboot and then entered into recovery, but the key was to directly enter into recovery after fastboot.
Let me know if that works for you.
I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (