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..
So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
galaxynote2 said:
So I've used CRHA for weeks, yet OEM unlock never appeared. I found this post to bypass the wait time, so I've flashed the rom again with a full wipe, followed the how-to and got the Oem Unlock option. Yay!
Installed TWRP and I found that data wasn't being detected, so I've flashed the Dm_verity and encryption disabler, rebooted prompted me to wipe the data and right after the device got into a boot loop with the Logo splash screen and a little legend saying that "Only official binaries are allowed". Reflashing stock is the only fix I found so far. I've also noticed that even after the device is OEM Unlocked, the RMM State is still "prenormal"
TLDR: I'm able to bypass the OEM Unlock wait time, I can install TWRP, I can flash the dm-verity fix, yet I'm unable to wipe my phone because of this problem.
Does anyone have a suggestion? What am I doing wrong?
Click to expand...
Click to collapse
What post shows you how to bypass? Please link it and I will help. I've never seen such a post despite countless searches and watching the boards.
But regardless, if you are getting the only official binaries screen, your haven't fully bypassed rmm. It sounds like whatever you did is letting you have custom recovery but not custom boot, as the dmv fix modifies there boot image, despite it not being needed on these devices. If what I'm saying is true, I can probably fix it, but I need this bypass guide to test
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll
Hey guys,
just received this phone from a friend and am trying to fix it.
I can boot into system, which crashes about 1sec after displaying the first welcome animation after the boot screen and just reboots then.
I can also boot into Recovery and Fastboot but the bootloader is LOCKED. To unlock it I would have to first add the account in developer settings, but I cant reach that screen at all.
What are my options here? Flashing official roms via MIFlash is not doing anything (4sec flash, green success message but no reboot, and no change) and I cant flash anything else due to the locked BL?!
Ordinary folk can't flash fastboot ROMs with a locked bootloader. It can only be done by EDL flashing, which requires an authorised account.
You need to open the back and use the test pin method to put the phone in EDL mode. The location of the pins are near the battery, a YouTube video will show you the exact location and which pins to bridge.
Despite numerous guides suggesting it's possible for anyone to EDL flash the phone using Qualcomm tools, I've never yet heard of anyone getting it to work. The only way to EDL flash is via an authorised account. You will need to ask on the K20 Pro telegram group for details of someone who has an authorised account. Depending on who you find, you'll need to pay between $20 - $40 US. They will then arrange a time with you when they can remote onto your PC and flash the phone for you, with their account.
I gave the same advice on here a couple of weeks ago and they found someone to do it for $22 fairly quickly.
[Bricked] TWRP doesn't mount flash drive, PC doesn't recognise in fastboot, TWRP doesn't work with MTP
I've wiped my phone, no realising TWRP doesn't actually work with MTP or a flash drive. I've been using the flash drive when it was booted, before the wipe. So the port is fine. Flashing a recovery via fastboot just leads to an infinite loop of...
forum.xda-developers.com