I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
Hey guys,
I just got my 1+3T and I immediately installed a custom ROM on it.
It works fine, but I cant get TWRP to stick.
When I reboot into recovery via ADB or advanced power menu the phone screen goes black with a white LED on top.
The phone is encrypted and I disabled force encrypt, but the only way for me to get into the recovery is to use fastboot command (booting recovery from fastboot mode doesnt work either), which works just fine.
When the phone gets stuck with the white LED my device manager shows the phone as "Qualcomm 9008". (I installed the drivers just in case I ever brick it)
Im using the latest 3.0.3.0 TWRP.
Any help is much appreciated!
/edit!
I managed to get it working! For everyone who may have the same problem, here is what I did.
I looked up the TWRP thread and found this:
jcadduono said:
DECRYPTION NOT WORKING?
If your device isn't decrypting in TWRP, chances are you still have the old crypto key format from the 3.5.1 release firmware.
You can solve this by updating to 3.5.3 and changing your boot up password in your device OS's settings.
By changing your password after updating to 3.5.3 or newer, your OS will rewrite your crypto key to be compatible with TWRP.
You are free to disable your password after this if you don't want one, and TWRP will decrypt with the default password.
Click to expand...
Click to collapse
So I wiped the whole phone, downloaded and flashed the latest OxygenOS from the offical website, set a startup password and rebooted.
Deleted the password, booted into fastboot and reflashed TWRP. Now TWRP stays and I can boot into it from fastboot mode.
If you are on 4.0 or 4.0.1...Try the latest twrp 3.0.3.1 beta..
hi guys bought a 3t today,
whilst trying out the new beta i wanted to flash freedom,
so i downloaded the toolkit and twrp wouldnt work , after different twrp the twrp was encrypted with a password which i hadnt set.
but i read that changing my pin password to a written password might work which i did change (standard password i use for majority of things)
well the phone will not start now, it will start with dm verity is nor started in enforcing mode, will boot load and then ask for a password which my password doesnt work...
so ive tried going into recovery which just doesn't work literally restarts the phone straight away
tried installed stock recovery and twrp via fastboot but nothing works
the bootloader is locked and will not unlock via typical fastboot commands or even the toolkit....
going out of my mind
i cant even wipe via fastboot
oh and NO the phone is not stolen!!!
fixed had to follow the mega unbrick post but took a few attemps
Encryption f* up your phone when moving between different encryption libraries recoverys, almost the most common fault experienced on this phone due to dm verity enforced encryption per default.
Sorry if this information is written somewhere else, but I couldn't find it...
I tried to install MAGISK on my Huawei Mediapad (Honor) X2.
I uninstalled SuperSU via script, flasht the boot.img, and installed Magisk.
There was an error first, about boot partition too small, and after reboot, my phone asks for a "NCK to unlock SIM network".
I flashed Magisk again (no errors this time) but it still asks for a NCK I do not have. (SIM Cards Pin does not work).
Because I wanted to use my phone again, I flashed a complete backup of my phone I had made prior to installing Magisk.
But... the phone STILL asks for NCK, so I cannot use my SIMcard!
Can anyone help me?????
Just reflashed with stock firmware (B212)... STILL asks for Network NCK
Tried everything, but still asking for Network NCK! Can no one help me???
Hi, I'm sorry if there already are too much people whining for help after doing something stupid, but I really need your help.
So I tried to install a custom ROM (Evolution X) on my Xiaomi Mi 9T Pro. I installed TWRP, which I opened with cmd on pc. It doesn't open using a button combo. But I (then) didn't think that could be a problem. Instead it opens Mi-Recovery. I installed the custom ROM zip file on the phone. After I first tried to reset the phone from TWRP, the files got encrypted. So I also installed the Magisk and something named Disable-Force-Encryption-Treble zip files, I've seen a video in which they said that would fix that. So after flashing those two zip files, I again reset the device. The custom ROM file isn't flashed. But it ended up in a bootloop. As soon as I Googled bootloop, I see search results of that Magisk is causing it, so I think that is the case.
Now I don't know what to do. I can't acces TWRP, since I need to open it with a pc. I can open fastboot on the phone, but can't acces it with PC, since USB-Debugging is disabled because of the reset. I also tried to do something with MiConnect, but my phone can't connect with it. And the phone isn't rooted (I think, I did flash Magisk, what causes the bootloop I believe, but I don't think that that roots the phone).
I think I can solve it by uninstalling Magisk, but how? Or do you have any other suggestions?
I really need help, it's my daily driver and can't miss it. I'm new with these things so I don't know that much about it. Thank you in advance.Hi, I'm sorry if there already are too much people whining for help after doing something stupid, but I really need your help.
So I tried to install a custom ROM (Evolution X) on my Xiaomi Mi 9T Pro. I installed TWRP, which I opened with cmd on pc. It doesn't open using a button combo. But I (then) didn't think that could be a problem. Instead it opens Mi-Recovery. I installed the custom ROM zip file on the phone. After I first tried to reset the phone from TWRP, the files got encrypted. So I also installed the Magisk and something named Disable-Force-Encryption-Treble zip files, I've seen a video in which they said that would fix that. So after flashing those two zip files, I again reset the device. The custom ROM file isn't flashed. But it ended up in a bootloop. As soon as I Googled bootloop, I see search results of that Magisk is causing it, so I think that is the case.
Now I don't know what to do. I can't acces TWRP, since I need to open it with a pc. I can open fastboot on the phone, but can't acces it with PC, since USB-Debugging is disabled because of the reset. I also tried to do something with MiConnect, but my phone can't connect with it. And the phone isn't rooted (I think, I did flash Magisk, what causes the bootloop I believe, but I don't think that that rooted the phone).
I think I can solve it by uninstalling Magisk, but how? Or do you have any other suggestions?
I really need help, it's my daily driver and can't miss it. I'm new with these things so I don't know that much about rooting, custom ROM and these things. And I'm new to XDA Developers, so sorry if I do something wrong.
Thank you in advance.
Download Xiaomi Flash Tool, download the lastest firmware for your device, install Xioami drivers via Xiaomi Flash Tool, connect your device in fastboot mode, flash the firmware and you're good to go
THIS WILL WIPE YOUR DEVICE!
Tijn#46 said:
Hi, I'm sorry if there already are too much people whining for help after doing something stupid, but I really need your help.
So I tried to install a custom ROM (Evolution X) on my Xiaomi Mi 9T Pro. I installed TWRP, which I opened with cmd on pc. It doesn't open using a button combo. But I (then) didn't think that could be a problem. Instead it opens Mi-Recovery. I installed the custom ROM zip file on the phone. After I first tried to reset the phone from TWRP, the files got encrypted. So I also installed the Magisk and something named Disable-Force-Encryption-Treble zip files, I've seen a video in which they said that would fix that. So after flashing those two zip files, I again reset the device. The custom ROM file isn't flashed. But it ended up in a bootloop. As soon as I Googled bootloop, I see search results of that Magisk is causing it, so I think that is the case.
Now I don't know what to do. I can't acces TWRP, since I need to open it with a pc. I can open fastboot on the phone, but can't acces it with PC, since USB-Debugging is disabled because of the reset. I also tried to do something with MiConnect, but my phone can't connect with it. And the phone isn't rooted (I think, I did flash Magisk, what causes the bootloop I believe, but I don't think that that roots the phone).
I think I can solve it by uninstalling Magisk, but how? Or do you have any other suggestions?
I really need help, it's my daily driver and can't miss it. I'm new with these things so I don't know that much about it. Thank you in advance.Hi, I'm sorry if there already are too much people whining for help after doing something stupid, but I really need your help.
So I tried to install a custom ROM (Evolution X) on my Xiaomi Mi 9T Pro. I installed TWRP, which I opened with cmd on pc. It doesn't open using a button combo. But I (then) didn't think that could be a problem. Instead it opens Mi-Recovery. I installed the custom ROM zip file on the phone. After I first tried to reset the phone from TWRP, the files got encrypted. So I also installed the Magisk and something named Disable-Force-Encryption-Treble zip files, I've seen a video in which they said that would fix that. So after flashing those two zip files, I again reset the device. The custom ROM file isn't flashed. But it ended up in a bootloop. As soon as I Googled bootloop, I see search results of that Magisk is causing it, so I think that is the case.
Now I don't know what to do. I can't acces TWRP, since I need to open it with a pc. I can open fastboot on the phone, but can't acces it with PC, since USB-Debugging is disabled because of the reset. I also tried to do something with MiConnect, but my phone can't connect with it. And the phone isn't rooted (I think, I did flash Magisk, what causes the bootloop I believe, but I don't think that that rooted the phone).
I think I can solve it by uninstalling Magisk, but how? Or do you have any other suggestions?
I really need help, it's my daily driver and can't miss it. I'm new with these things so I don't know that much about rooting, custom ROM and these things. And I'm new to XDA Developers, so sorry if I do something wrong.
Thank you in advance.
Click to expand...
Click to collapse
same thing happened.to me. now i have the chinese rom and it sucks. twrp only boot loops to itself any other rom will.not boot love to know.how to.ditch miui and have my apps working again