So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
Related
Boot loop
Moto x 1060 rooted on 4.2.2 with TWRP 2.7.7.1 installed. I tried to restore. TWRP says restore completed but when I try to reboot into the loop I go. I can access TWRP but nothing else. I have two TWRP recoveries but neither works. My computer doesn't see the phone when connected, so I can't flash. Any help would be greatly appreciated.
Clownlike said:
Boot loop
Moto x 1060 rooted on 4.2.2 with TWRP 2.7.7.1 installed. I tried to restore. TWRP says restore completed but when I try to reboot into the loop I go. I can access TWRP but nothing else. I have two TWRP recoveries but neither works. My computer doesn't see the phone when connected, so I can't flash. Any help would be greatly appreciated.
Click to expand...
Click to collapse
why do u tried to restore if u have TWRP??
try to put in fastmode and flash the firmware again clean
or put in twrp and wipe cache,userdata and dalvik cache
hope that helps u
When I restore with TWRP it shows successful. Then when I boot it goes into a loop. I have 2 recoveries and they both do that. MY computer does not recognize it so I cannot flash.
Clownlike said:
When I restore with TWRP it shows successful. Then when I boot it goes into a loop. I have 2 recoveries and they both do that. MY computer does not recognize it so I cannot flash.
Click to expand...
Click to collapse
Your computer should recognize it in fastboot mode (NOT TWRP) - you need to be the bootloader screen (AP Fastboot Mode). Follow the guide in general "Return to 100% stock" to flash the entire SBF for your carrier. DO NOT ATTEMPT TO DOWNGRADE. Only flash the version you are currently on or higher.
Everything you need is in that thread, including the necessary drivers. If your phone isn't getting recognized it is either because you do not have the drivers installed, OR you are trying to connect when booted in to TWRP. Once again, this is wrong. You restore using your PC from the BOOTLOADER screen, NOT TWRP.
101
When I am in boot loader mode and try to connect with RSD Lite the phone is seen as "fast boot" connected but nothing I flash works. I have done this before and the phone was recognized but after installing TWRP it is not, nor can I flash anything, it says failed.
Thanks Sam. I got RED lite to work and all is well. Again, many thanks
Clownlike said:
Thanks Sam. I got RED lite to work and all is well. Again, many thanks
Click to expand...
Click to collapse
Excellent! Glad to help. As you probably already know, you can now flash TWRP back on and re-root. Good Luck! :good:
P.S. I sent you a private message - please check your PMs.
samwathegreat said:
Excellent! Glad to help. As you probably already know, you can now flash TWRP back on and re-root. Good Luck! :good:
P.S. I sent you a private message - please check your PMs.
Click to expand...
Click to collapse
I cannot flash or install SuperSu or TWRP. I don't really want to install TWRP because that caused the original problem. I need SuperSu but when I try to install it says "there is no SU binary installed". Phone says device is unlocked and Status code 3 and I get the bootloader unlocked warning screen. Should I reflash 4.2.2 and start over?
Clownlike said:
I cannot flash or install SuperSu or TWRP. I don't really want to install TWRP because that caused the original problem. I need SuperSu but when I try to install it says "there is no SU binary installed". Phone says device is unlocked and Status code 3 and I get the bootloader unlocked warning screen. Should I reflash 4.2.2 and start over?
Click to expand...
Click to collapse
TWRP does not cause problems - likely your issue was un-related. You cannot install SuperSU without TWRP. You do need to flash TWRP - use the latest version from here: http://techerrata.com/browse/twrp2/ghost
After you flash it, type: fastboot reboot-bootloader and immediately boot into TWRP. Click exit and it will offer to root for you.
If you insist, you can flash stock recovery back on afterwards which will remove TWRP.
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.
Is it possible to install TWRP with your device running the Nougat beta ?
The recovery is separate from the firmware. So I don't see why it wouldn't be possible. Root on the other hand I wouldn't know but I suppose the SuperSU beta zip file flashed with custom recovery would get the phone rooted.
If it was a kernel being flashed then that would matter as it affects the firmware (as it replaces the stock kernel).
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
FedoraMan said:
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
Click to expand...
Click to collapse
I tried to install the custom recovery using adb, however my phone can't be detected ?
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
FedoraMan said:
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
Click to expand...
Click to collapse
Already tried this, since installing the Nougat beta my PC only recognises my phone when in recovery mode. I installed TWRP but phone still boots into the original erecovery and not TWRP
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
FedoraMan said:
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
Click to expand...
Click to collapse
Yes installed with fastboot, I manually booted into recovery (volume up + power button) right after flashing it. I thought flashify requires root ??
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
FedoraMan said:
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
Click to expand...
Click to collapse
Yeah, I just flashed the update using the dload method. The main reason I want to install TWRP is so i can downgrade. I've tried using the dload method to downgrade however it doesn't work.
For the dload method, I think you have to flash stock recovery first
FedoraMan said:
For the dload method, I think you have to flash stock recovery first
Click to expand...
Click to collapse
I am currently using stock recovery and it still won't let me downgrade, the update reaches 51% then an error occurs. Would it be possible to flash downgrade firmware using fastboot ?
I believe you can, but you should check online to see if it is.
FedoraMan said:
I believe you can, but you should check online to see if it is.
Click to expand...
Click to collapse
I will check and try this method, I'll get back to you with the results
Ok. Good luck!
Same problem here, I installed a leaked Nougat beta for the Honor 8 via TWRP and when I tried to get back to TWRP it wouldn't let me. I've tried to flash it again via fastboot but I can't boot into it :/
I have this problem too after Flashing Nougat.
I have already flashed twrp recovery via fastboot, installation complete. But I cant boot into recovery mode.
I have never had this kind of problem before. If you tried a cold boot (Hold volume up + power), try typing "adb reboot recovery" instead (or the other way around, if you've done that)
Hello.
I came from z3.
For z3 to get in recovery with N u have to hold down vol button and insert cable. Charger or PC
Sent from my EVA-L19 using XDA-Developers mobile app
I don't know if this works, but I was looking around in HiSuite (huawei's phone thing app on pc) and saw a ROM flashing option. Try that.
Hey guys so I'm panicking right now, so I just unlocked the bootloader, flashed TWRP and rooted my phone but now the phone won't boot it's just stuck at the boot icon with the two circles chasing each other, am I screwed and is my phone useless now ?
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. Your phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Anova's Origin said:
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. You phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Click to expand...
Click to collapse
Okay so can you tell me how to remove 2.78 before I flash 2.79 ? thanks
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Anova's Origin said:
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Click to expand...
Click to collapse
My phone isn't showing up on my pc as a removable storage and when I type adb devices my phone isn't showing up either
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Anova's Origin said:
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Click to expand...
Click to collapse
I managed to flash 2.79 but I don't think it worked, still stuck booting, will leave it for a few minutes though to see if anything changes, any suggestions if that wasn't the issue ?
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Anova's Origin said:
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Click to expand...
Click to collapse
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
stefinho said:
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
Click to expand...
Click to collapse
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus.
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
Click to expand...
Click to collapse
Thanks, will try that now.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Click to expand...
Click to collapse
DUDE, it worked thank you so much man really appreciate the help