TWRP 3.5.1 Aquaris X2 - BQ Aquaris X2 / X2 Pro ROMs, Kernels, Recoveries,

Hello guys.
I'm looking to build LOS 17 for our device, however I though it might be nice to have a fully working twrp before attempting that.
So this is still a work in progress, but I got it booting.
Here's the recovery: https://mega.nz/file/rcR0GDqQ#0dxLkJhpAwM3cTaZo7-abetNLGlspC4E-EIafnTNNMc
You can try it by going to bootloader ( full stop and volume down + power btn). Indeed it seems that rebooting to bootloader via "adb reboot bootloader" isn't really working
once in bootloader, run "fastboot boot recovery.img"
You will notice there is no "flash" command, so it should not alter any of your partitions.
For reference, if anything goes wrong, here is the last known working recovery (not made by me):
https://androidfilehost.com/?fid=4349826312261701358
Looking forward to your experience !

this version doesn't work to me, however everything was fine with the 3.3.1

Related

Bootloader Flash from TWRP (anything flash?)?

I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not:
Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there. Stupid problem to have right here, lol.
Any thoughts/help is appreciated. TIA.
Okay, so I got around the issue. I'm not sure if TWRP is supposed to be able to fastboot or ADB but mine would not, I was under the impression that I could fastboot or ADB in recovery. Maybe that was just a mistake on my part thinking that.
My workaround:
- Reboot into the bootloader (not TWRP recovery), 3 finger reset, power off, then power button + vol up + vol down until you get the OEM Android bootloader screen (unplug if plugged in, it didn't seem to want to go into bootloader when it was plugged in - maybe I just didn't wait long enough, but unplug if it doesn't want to go into the bootloader).
- From here I was able to fastboot, "fastboot devices" listed it
- I then flashed the bootloader: "fastboot flash bootloader bootloader-hammerhead-hhz12h.img" (may differ if you wan to flash different bootloader)
- I then rebooted into bootloader: "fastboot reboot-bootloader"
- I then flashed recovery: "fastboot flash recovery openrecovery-twrp-2.8.5.2-hammerhead.img" (may differ for different version of recovery)
- I then used vol up/vol down to select "reboot recovery", and hit the power button
- TWRP booted and from there, now that I have the hhz12h.img bootloader flashed I could install the ROM, so I wiped data/dalvik/cache/system again, installed the ROM, installed Gapps, and rebooted, good to go.
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Primokorn said:
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Click to expand...
Click to collapse
Got it. For whatever reason I could not get ADB to see the device while I was in TWRP. I tried the ADB sideload feature in 'advanced' but it just waited and waited and waited forever. I believe ADB is set up properly on my system because it works fine on ROM. Not sure what the deal is with that, but I don't have much reason to go into ADB in recovery anyway aside from this issue, so it's [hopefully] not a big deal.
As for flashing the recovery, yeah, bad habit I guess. On my old phone (Fascinate Galaxy S 1), if you had custom recovery and had to 3-finger reset to bootloader because your phone wouldn't turn on or was bootlooping or whatever the recovery was boned, had to re-odin flash it. So it's stuck in my memory now that if I had to 3 finger it I better flash recovery. I'll try to knock myself out of that habit .
Thanks!
Syndacate said:
Is there a TWRP zip-install hhz12h bootloader I can use?
Click to expand...
Click to collapse
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Wakamatsu said:
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Click to expand...
Click to collapse
Thanks, I'll snag that just in case I ever have a fastboot outage or I'm on a system w/o ADB/fastboot or something.
ldubs said:
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Haha, I didn't even look at the dates, I just went to the "Tools/Utilities" page for the Nexus 5 and it was the top link....I didn't think too much on it, just figured top link = most recent = latest.
http://forum.xda-developers.com/showthread.php?t=2511507
I'll dig around for a thread which has latest and flash that on there, can't expect old versions to work flawlessly, now can we?
EDIT:
That actually might have just been a copy/paste error on my part, as I had the old TWRP lying around for fastboot and copy/pasted the name from that. I used TWRP (ROOT) app to install and I chose latest (or so I thought). Now I have literally NO idea which one I was using -_-.
No worries glad you got it sorted. You can flash an image file in twrp now BTW.
Sent from my Nexus 5 using Tapatalk

Unbrickable tf300t

Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.
Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74
Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you
What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.
Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.
I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.
Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?
OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.
Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !
Thanks. Have fun with your tf300.

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

android phone can boot without working recovery?

Hello guys,
I've unlocked the bootloader of my smartphone. I want to flash TWRP recovery, but my phone is not supported, thus I should test a TWRP image compiled for similar devices (i.e. same SoC) and pray that everything will work.
I read around that "fastboot boot twrp.img" doesn't work, so I have to flash it. However, if the twrp doesn't work properly, will the phone boot? or does a "corrupted/not working" recovery cause a brick?
Suppose that pressing the power and volume buttons will display an error message like "illegal opcode" instead of TWRP (i.e. TWRP is completely not working and it doesn't boot).
Nrin said:
Hello guys,
I've unlocked the bootloader of my smartphone. I want to flash TWRP recovery, but my phone is not supported, thus I should test a TWRP image compiled for similar devices (i.e. same SoC) and pray that everything will work.
I read around that "fastboot boot twrp.img" doesn't work, so I have to flash it. However, if the twrp doesn't work properly, will the phone boot? or does a "corrupted/not working" recovery cause a brick?
Suppose that pressing the power and volume buttons will display an error message like "illegal opcode" instead of TWRP (i.e. TWRP is completely not working and it doesn't boot).
Click to expand...
Click to collapse
Typically if the bootloader is unlocked it should be safe to test. However finding one that will work might be painstaking. You could always compile your own twrp from source, though.
Sent from my KYOCERA-C6745 using Tapatalk

Honor 6x (BLN-L24) Twrp overwritten by Default Bootloader

I have a Honor 6x (BLN-L24) with EMUI 5+, Android Nougat, all updated. It is the U.S. edition. I unlocked the Bootloader, installed ADB / Fastboot tools and can flash the correct TWRP recovery image (3.1.1-0-berlin.img) but everytime I try to reboot into recovery, the standard EMUI recover overwrites TWRP and I just end up in the EMUI recovery.
I've looked at every forum I can find, articles, etc... but can't wrap my head around this one. If anyone with a similar experience and/or with a solution could help, I'd be most grateful.
Thank you!
I agree with with Rommco05. He IS correct, as I wondered the same thing till I realized to try unplugging it. Also make sure its the Power AND up buttons at same time. If you happen to hold only the up button it will take you to the erecovery feature where it trys hooking to WiFi for updates , which wont help you either.
Still doesn't work
Thanks for the responses. Unfortunately, unplugging doesn't do it either with the key combination you suggested. The following article is helpful for key combinations but alas, it still won't load into TWRP.
It is really strange as I can't even get past "Your device has been unlocked and can't be trusted" screen now. It just stays there...
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Also, when I try to download "Latest Version and Recovery" from "Huawei eRecovery", I'm getting "Getting package info failed". I
Try OpenKirin twrp from recoveries section here on 6X forums
etmartinkazoo said:
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Click to expand...
Click to collapse
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Key combination timing?
galapagos said:
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
This is helpful, thank you. I found a page "Key Combinations Clarified for Honor 6x" which has a number of key combinations but nothing is helpful in my case that I know of. Do I use these key combinations imediately after the flash?
Is there a specific tutorial or guide that was helpful for you? I'd be grateful for any further assistance.
Thanks.
Rommco05 said:
You need enter to recovery? TWRP?
Click to expand...
Click to collapse
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Finally got Twrp installed. Rooted and installed custom Rom (lineageos) but when I reboot after flash screen, it's just blank...
If I were you, I would go completely back to stock and start over. Once you fastboot flash TWRP, it is imperative that you reboot back into TWRP before booting into the OS. Also, bootloaders don't overwrite recoveries. They are separate partitions, so your title is a bit misleading.
Regardless, you must still have stock recovery on your device since it is "defaulting" to that instead of TWRP. Like I said, it is extremely important to boot into recovery after you first flash it.
fastboot flash recovery recovery.img
let it do it's thing.
fastboot reboot recovery OR you can do it manually in TWRP right after the flash.
Have you tried rebooting to recovery from the system?
Connect your device to your computer, enable USB Debugging, and run
Code:
adb reboot recovery
from Windows CMD or Linux Shell, or any other one you prefer.
If this works, then you are doing the recovery key combination wrong.
Cheers
I'm having the same issue as OP. I have a BLN-L24 from Best Buy in the US. Reverted to emui 4.1 and android 6, unlocked bootloader, flashed twrp-3.2.1-0-berlin.img, and it keeps booting into huawei erecovery.
I didn't get any info on what the OP actually did to get twrp installed.
FWIW, there is no "fastboot reboot recovery"
FWIW2, you can't turn off the honor 6x from the bootloader. the best you can do is a hard reboot.
etmartinkazoo said:
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Click to expand...
Click to collapse
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
hexag1 said:
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
Click to expand...
Click to collapse
RedSkull fixed my problem!

Categories

Resources