I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.
Related
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.
coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2
Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.
Finally got around to unlocking my device with SunShine and was looking forward to installing a Moto X rom. Installed PhilZ recovery and set about cleaning the phone state to I could install rom. Unfortunately, I couldn't connect to the phone with ADB in PhilZ while trying to sideload the rom. I reboot my phone to try again and now I can't seem to get past the unlocked bootloader warning. Holding Vol+ and Power isn't taking me to recovery. Fastboot cable doesn't either. Any ideas?
zefyx said:
Finally got around to unlocking my device with SunShine and was looking forward to installing a Moto X rom. Installed PhilZ recovery and set about cleaning the phone state to I could install rom. Unfortunately, I couldn't connect to the phone with ADB in PhilZ while trying to sideload the rom. I reboot my phone to try again and now I can't seem to get past the unlocked bootloader warning. Holding Vol+ and Power isn't taking me to recovery. Fastboot cable doesn't either. Any ideas?
Click to expand...
Click to collapse
Hold vol- and power for 3 secs then let go of vol- keep holding power for another 3secs then let go. That should get you to bootloader. Then scroll using vol-, use vol+ to select. If you plan on running ghost (Moto x) roms only then you need to use Phils touch ghost build and cm12 patch.
Did you nandroid your stock rom, if so restore and boot up then just plug in the phone and transfer roms/gapps. I never used adb sideload as it is easier just to download directly to the phone...just don't wipe internal storage
Yeah, it's always super difficult to get my phone into recovery for some reason. I backed up my original files, but removed them when trying to get the new rom installed by accident -.-
EDIT: finally got Mini into recovery but the same issue with not being seen by adb is here. I'm not sure how to proceed as Moto Device Mgr is installed and when I plug/unplug the device I hear a chime.
going to use fastboot to start from scratch and get rid of philz. thanks anyway guys.
you cannot ADB from Philz... or at least mine doesnt let me either.
I wonder how you made out with this issue.
I wanted to say, you're doing it wrong. I run the Moto-X ROM on my Maxx. Piece of cake.
You do must use Philz recovery. From your booted stock ROM connect your phone to your PC and copy the ROM, gapps and CM11 Patch, (SuperSU also) to your phone into the Download folder. To boot into fastboot is simple, press and hold vol- and pwr, I do about 5 secs and release the pwr button. Vol- to recovery and press vol+ to select.
Install zips from there, ROM, then gapps, then patch, then SuperSU. All done.
Hello, I bought a OnePlus one (came with CM11 - 4.4.4) and followed the standard steps to root it
1) unlock bootloader - successful, phone got factory reset, checked the status using fastboot
2) Flash custom recovery (TWRP) using fastboot - always "okay" message
3) The phone DOES NOT boot to recovery after this - it gets stuck at the 1+ logo, or remains stuck for a few seconds and goes to normal reboot. -I've tried using fastboot to reboot phone while holding down volume button
Please help! i've look this problem up and haven't found a solution.
I tried 2.7.0.0, and the latest 2.8.5.1, along with 2.8.6.0, along with trying to use the one plus tool kit. Using the toolkit, even flashing the stock recovery, then booting it didn't work.
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
kenboyles72 said:
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
Click to expand...
Click to collapse
I tried this, same result
ak14523 said:
I tried this, same result
Click to expand...
Click to collapse
As the other posted mentioned you have to fastboot flash twrp (2.8.6.0) then power off phone and use volume down + power button combo to get to recovery. Its flashing but if you boot to OS it will be overwritten by CM recovery hence booting directly will alleviate that
Boot into os, enable dev options by tapping the build number a bunch of times in settings-about phone section, go back and go into settings-developer options, make sure "update cyanogen recovery" is unchecked. Flash recovery again, and like people have said, power off the phone and use volume down and power buttons together to boot into recovery.
Thanks for the quick replies guys. I have tried all the above s and none of them have worked
Should I try unlocking the bootloader again?
I recommend going to this guide and following it closely: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
As for which version of TWRP to use, I recommend this version: https://www.androidfilehost.com/?fid=24391638059059048
Hi i own an honor 8 FRD-L09 and it's rooted , so the other day i updated the EMUI from 4.1 to 5.0 and my xposed installer said frame work is not intsllad and then i checked my supper su and it said my phone was not rooted and that this point i was what!!
so tried to boot up to the TWRP recovey and gusses what i cant and frist it showed my the the phone recovey options not the custom TWRP that i installed before. i flased The TWRP Recovey in to my phone and wrote the commoade [adb reboot recovery] so it would boot the TWRP That i just flashed but gets stuck on your devie is booting now for 20 min!!! so i thought and this moment hey what not factory rest your phone and everthing mabye the then i can re root my phone but once agian it got stuck on the same screen as when i tried boot TWRP [ YOUR DEVICE IS BOOTING NOW] So a this point i gave up and i wonder did this happedn to you guys who updated ther honor 8 and can you re root you phone again?
oh P.S when i hold the power and volume down buttom my phone turns on when i hold the power and volume up buttom for tre sec it goes to the honor 8 revory mode not the twrp and its saying download the new version of the recovey and its fails evey time and when hold the power and the volume buttom simultaneously i think it't trying to boot the TWRP recovey but it get's stuck on you deviec is booting now screen.
and soryy for my english the my frist languages
i too faced the same problem. some one please help
While your phone is plugged into a computer with a USB cable, hold down volume down + power until your phone enters the bootloader. From there, flash the TWRP from this thread:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
After flashing, hold down volume up and reboot with 'fastboot reboot'. Once you see your phone is booting message, let go of volume up and it should load TWRP. If it freezes and doesn't load after 3-5 minutes, try the official TWRP from twrp.me (for Marshmallow devices) since your Nougat flash may be messed up. If neither works, then flash the stock recovery from bootloader and follow the instructions to do a force-update with the full stock system image.
Telperion said:
While your phone is plugged into a computer with a USB cable, hold down volume down + power until your phone enters the bootloader. From there, flash the TWRP from this thread:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
After flashing, hold down volume up and reboot with 'fastboot reboot'. Once you see your phone is booting message, let go of volume up and it should load TWRP. If it freezes and doesn't load after 3-5 minutes, try the official TWRP from twrp.me (for Marshmallow devices) since your Nougat flash may be messed up. If neither works, then flash the stock recovery from bootloader and follow the instructions to do a force-update with the full stock system image.
Click to expand...
Click to collapse
Mine won't boot to TWRP and when I use the EMUI boot screen its saying it can't connect to Huawei erecovery servers. So I can't even wipe the root at this point. Any ideas?
Many Thanks!
Telperion said:
While your phone is plugged into a computer with a USB cable, hold down volume down + power until your phone enters the bootloader. From there, flash the TWRP from this thread:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
After flashing, hold down volume up and reboot with 'fastboot reboot'. Once you see your phone is booting message, let go of volume up and it should load TWRP. If it freezes and doesn't load after 3-5 minutes, try the official TWRP from twrp.me (for Marshmallow devices) since your Nougat flash may be messed up. If neither works, then flash the stock recovery from bootloader and follow the instructions to do a force-update with the full stock system image.
Click to expand...
Click to collapse
Well this worked for me, after a day of googling. the twrp-3.1.1-1-frd.img worked, it may have been following the instructions about "fastboot reboot, while holding the volume up.
hey guys.. having the same issue..
I have DUK-L09C432B183 bootloader unlocked and phone u locked..
I downloaded twrp and side loaded with adb/fastboot
but when I reboot (fastboot reboot) it doesn't enter twrp recovery but emui recovery menu.. any suggestions?
(I tried fastboot reboot whole holding volume down.. didn't work)
ok [EDIT] i could finally get TWRP installed .. i backup everything on external SD
then i flashed MAGISK.zip (v14) and from there phone will show HONOR and jsut now it booted into HUAWEI Erecovery and gives me 2 options "factory data reset "Q or Download latest version and recovery !
any suggestions how i can ROOT it ? should i keep on try with MAGISK or ? thank you guys !
SECOND EDIT
so i did FACTORY data reset.. then i ADB side loaded twrp emmc .. then i installed magisk 13.3 .. rebooted and everythign goodf ! i've twrp and device is rooted !!
all good
Telperion said:
While your phone is plugged into a computer with a USB cable, hold down volume down + power until your phone enters the bootloader. From there, flash the TWRP from this thread:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
After flashing, hold down volume up and reboot with 'fastboot reboot'. Once you see your phone is booting message, let go of volume up and it should load TWRP. If it freezes and doesn't load after 3-5 minutes, try the official TWRP from twrp.me (for Marshmallow devices) since your Nougat flash may be messed up. If neither works, then flash the stock recovery from bootloader and follow the instructions to do a force-update with the full stock system image.
Click to expand...
Click to collapse
Thank you so much for linking to that image file! I was looking on the internet for days!
Telperion said:
While your phone is plugged into a computer with a USB cable, hold down volume down + power until your phone enters the bootloader. From there, flash the TWRP from this thread:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
After flashing, hold down volume up and reboot with 'fastboot reboot'. Once you see your phone is booting message, let go of volume up and it should load TWRP. If it freezes and doesn't load after 3-5 minutes, try the official TWRP from twrp.me (for Marshmallow devices) since your Nougat flash may be messed up. If neither works, then flash the stock recovery from bootloader and follow the instructions to do a force-update with the full stock system image.
Click to expand...
Click to collapse
Hi,
If I used the official TRWP 3.1.1 first and it didn't work, can I just go ahead and flash the TWRP using the modified twrp.img at the above link to see if that works?
Not able to get into TWRP recovery, stuck on "Your device is booting now..."
Hey everyone,
I just unlocked my bootloader and now want to flash TWRP and SuperSU. My Phone is already Nougat with Emui 5.
The Problem is that I'm just not able to enter the recovery. When pressing volume down + power or trying "adb reboot recovery" in the command line, the phone starts in the "unlocked bootloader warning screen". But not like in the normal warning screen it doesn't give me options but just shows a white line saying "Your device is booting now..." and thats where it gets stuck. Only gets hotter...
The fun thing is I already was in the recovery but wasn't able to flash the SuperSU (r275). Maybe it was not compatible with Nougat. TWRP just couldn't mount various things. After reflashing the recovery below instead of some other version (don't know anymore) I'm not able to enter the recovery again.
Feels like I searched the whole Internet and there is nearly nobody with the problem or a solution. Tried this as well: https://forum.xda-developers.com/honor-8/help/honor-8-boot-to-twrp-recovery-lost-root-t3567462. It seems like nobody who published a Honor 8 + Nougat + TWRP + SuperSU "How To" acutally tried it himself.
I used this TWRP https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Please help me I can't use WhatsApp because I need to restore it with Titanium (Database way doesn't restore all chats... Other problem)
Thanks everybody I just can't stand this anymore
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
sysak said:
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
Click to expand...
Click to collapse
Thank you I got it!
So I got my L09 with Nougat/Emui 5 on it. Then just used TWRP from https://forum.xda-developers.com/showpost.php?p=70228949&postcount=252 (bootable, think ist ist 3.0.2.0) then flashed 3.1.1.0 from https://forum.xda-developers.com/honor-8/development/twrp-t3566563 (bootable) and finally flashed SuperSu from first Link again. Other SuperSU versions (like the phh r275) WERE NOT flashable.
Magisk is the most compatible root solution for the Honor 8 on Nougat. The only thing that doesn't work (seamlessly) is MagiskHide, but the root itself works and flashes fine from TWRP.
I have tried to flash twrp multiple times to no success. I have tried multiple variations of the tool but for some reason when I go try to boot into recovery it takes me to erecovery which fails to do anything.
Are you sure about button combination
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
sysak said:
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
Click to expand...
Click to collapse
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Dalg1991 said:
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Click to expand...
Click to collapse
Try adb reboot recovery in command line on your PC when phone is turned on
0mrwhatsupguy0 said:
Try adb reboot recovery in command line on your PC when phone is turned on
Click to expand...
Click to collapse
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Few problems with Binary SU and BusyBox
My phone seems to be rooted. Titanium Backup works but I have to accept every App instalation manually. With other settings restoring gets stuck. Also SuperSU reminds me every time that my BinarySU needs an actualisation but fails if it tries. And finally BusyBox just isn't able to get itself installed.
I'm thinking about restoring stock firmware, update to Nougat, and flash the two TWRP Versions and SuperSU again but hate to spend ours on my phone. OnePlus One rooting was sooo easy...
Dalg1991 said:
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Click to expand...
Click to collapse
Is there a number of times you have to do it? How should I transition from this stupid "Your device is an enemy of the state" screen to something that will connect to adb?