I have a Huawei P9 Lite and i have installed twrp and android 7.0 on it. Now I want to install Google assistant, but when i try to boot in twrp recovery (volume down + power b) it shows me the screen where it says ''Installing update'' and then freezes at 5 % so i have to hold my power button to power off the phone.
If I dont try to run in the twrp, phone works just fine.
I apologize for my bad english.
Hi there,
I will move your thread in the correct forum dedicated to Huawei P9 Lite for more relevant answers.
Good luck
Bump..
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.
KashifSMalik said:
Just to state that I am in the same boat here; as I am facing the same issue. Here's what happened in my case (using a guide found here at XDA-Developers):
-- unlocked the bootloader
-- booted to bootloader and flashed twrp
-- used adb to reboot to recovery (adb reboot recovery)
-- used twrp recovery to flash nougat update (two zip files, one ~1300mb and second ~680mb)
-- had some errors that were expected, the guide said ignore them and reboot after both zips have been flashed.
-- the flash overall was successful as the phone booted in emui 5 with android nougat. However, there was no virtual keyboard; so decided to do a factory reset
-- rebooted to recovery, but this time, the phone booted to huawei erecovery
-- did a factory reset, but to no avail
-- now, i can't boot into twrp to flash anything else. booting into bootloader and using fastload to flash recovery image is successful, but the phone does not boot to twrp recovery; remain stuck on "your phone is booting up" (or something similar).
My phone is not bricked, as basic telephony, wifi and built-in apps are working fine. But, without a keyboard, its pretty useless for everyday use. Any help in this matter will be appreciated.
Click to expand...
Click to collapse
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
Did that and it worked thanks!
Claleale said:
Your twrp is gone.You need flash revolution recovery from Badwolfye,that is for nougat!
Click to expand...
Click to collapse
This seems helpful; but how can I flash recovery if I can't boot to fastboot?
[Update] Oh, got to fastboot, trying the suggested recovery now.
Fixed
Fixed using the suggestion above. Thanks.
Related
Hi there.
I used my OP2 with Oxygen OS for a while, so today I decided to switch to kingmercians H2OS.
I must say I had fastboot OEM unlocked, TWRP 2.8.7.0 installed and 100% working.
so I took a backup of my OxygenOS via TWRP, then wiped and flashed kingmercians H2OS.
played with it for some minutes, then I didn't find it worth the upgrade.
and now my hell comes.
I didn't read that I had to flash a revert to lollipop script .zip
so I rebooted into TWRP, went to "restore", and selected my Oxygen OS backup I previously made.
restore was successfully, and swiped to reboot.
then phone didn't start. I am stuck at boot [the one with oneplus logo and powered by android] and nothing changes.
I tried to enter recovery with buttons combo [power + volume down], but nothing happens, phone just starts at boot logo.
I can only enter in fastboot mode, nothing more.
I also tried re-flashing TWRP from fastboot, but with no clue accessing it [fastboot command says it successfully transferred TWRP .img file, but I cannot enter it].
is there any way I can get my OP2 to work once more?
thanks to anyone who wants to help me!
Hello, try using the method in this link. I had the same problem yesterday after trying hydrogen os and comming back to oxygen os and it solved it.
forums.oneplus.net/threads/return-op2-to-100-stock-unbrick-soft-bricked-op2-oxygenos-2-1-1-fastboot-images.388967/#post-13718486
Give me a feed-back !
Good luck
karimfilal said:
Hello, try using the method in this link. I had the same problem yesterday after trying hydrogen os and comming back to oxygen os and it solved it.
forums.oneplus.net/threads/return-op2-to-100-stock-unbrick-soft-bricked-op2-oxygenos-2-1-1-fastboot-images.388967/#post-13718486
Give me a feed-back !
Good luck
Click to expand...
Click to collapse
thanks a lot for for your reply!
I followed your link, but file hosted on mega was missing [link broken].
do you have any mirror?
Why dont you try 1st aid... Or since you try to install MM flash twrp 3.0.0.0
fastboot flash recovery recovername.img
fastboot boot recoveryname.img
zipalign said:
thanks a lot for for your reply!
I followed your link, but file hosted on mega was missing [link broken].
do you have any mirror?
Click to expand...
Click to collapse
The link in mega is working i've just tried it !
lummujaj said:
Why dont you try 1st aid... Or since you try to install MM flash twrp 3.0.0.0
fastboot flash recovery recovername.img
fastboot boot recoveryname.img
Click to expand...
Click to collapse
solved using firstaid.
thanks a lot!
Exodus rom, No recovery
Hi
I used the fix, and get the TWRP on my OP2, but I'm Running on the exodus rom, build 06/10/2016. And after entering recovery mod, and reboot, The phone stay on the exodus logo, then after a few minutes, it restarted. So I get recovery, but now I can't use the phone.
Again, used the Twrp to flash the boot image, and restart. So far so good, but again, I lost recovery mode.
Im I doing something wrong?
I changed the twrp in the fix to get the 3.0.2.0 version, but again, enter recovery and system don't load. So I flashed boot, and recovery, but again, just get one of the two of them.
Tried the TWRP Manager to install it, but It says I already have another versiĆ³n or something gone wrong. (yes the manager says TWRP is not installed)
Tried flashify to install TWRP, downloaded, flashed, but again there is no recovery.
Can someone help me please
Thanks
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
I really need help here. New to rooting androids, will pay BTC for whoever can help me.
I started off fine, unlocked my bootloader, flashed to TWRP and installed supersu. * I WAS ABLE TO BOOT INTO SYSTEM HERE *
I then tried to flash some other stuff and got stuck where it would only boot to TWRP.
Downloaded the stock firmware to flash it (XT1625) and ran all the commands.
Still everytime I reboot it goes into recovery mode.
Any help?
I have tried to do factory reset directly from phone menu. This got me into TWRP. I have selected factory reset again.
Then I was able to boot only to TWRP, not system.
I have fixed it by booting into booloader (power + vol downs) and to select START. Then it started to system OK.
Not sure if this is your case.
okplshelpthanks said:
I really need help here. New to rooting androids, will pay BTC for whoever can help me.
I started off fine, unlocked my bootloader, flashed to TWRP and installed supersu. * I WAS ABLE TO BOOT INTO SYSTEM HERE *
I then tried to flash some other stuff and got stuck where it would only boot to TWRP.
Downloaded the stock firmware to flash it (XT1625) and ran all the commands.
Still everytime I reboot it goes into recovery mode.
Any help?
Click to expand...
Click to collapse
^this works !
novakmi said:
I have tried to do factory reset directly from phone menu. This got me into TWRP. I have selected factory reset again.
Then I was able to boot only to TWRP, not system.
I have fixed it by booting into booloader (power + vol downs) and to select START. Then it started to system OK.
Not sure if this is your case.
Click to expand...
Click to collapse
Thank you very much for your tutorial which helped a lot.
What did you do to keep it from booting into recovery upon the next reboot? Mine goes into recovery-loop again once I do regular reboot from the system. There might be a software switch somewhere.
Thanks alot
KlausR said:
Thank you very much for your tutorial which helped a lot.
What did you do to keep it from booting into recovery upon the next reboot? Mine goes into recovery-loop again once I do regular reboot from the system. There might be a software switch somewhere.
Thanks alot
Click to expand...
Click to collapse
Hello, I didn't observe such issue. Reboots from system are ok for me.
Download the correct firmware for your phone, if it is AMZ variant then download AMZ firmware.
Hello, ive unlocked my bootloader on my h870 and ive flashed twrp. when ive just flashed it i was able to boot into twrp but now everytime i try to boot into it it wil wipe all my data with the stock lg recovery mode can someoneone please help me? Thanks! Just got the phone a few hours ago
You have to install a custom rom or root to make twrp permanent, if you don't do that it will install always after the first boot the stock recovery.
mprovi_15 said:
You have to install a custom rom or root to make twrp permanent, if you don't do that it will install always after the first boot the stock recovery.
Click to expand...
Click to collapse
Ok but how can i install root or a custom rom when i cannot boot into twrp?
aaflan88 said:
Ok but how can i install root or a custom rom when i cannot boot into twrp?
Click to expand...
Click to collapse
You need to reflash twrp with the bootloader like the first time.
mprovi_15 said:
You need to reflash twrp with the bootloader like the first time.
Click to expand...
Click to collapse
I understand that mprovi but hen again TWRP doesn't boot unfortunately
aaflan88 said:
I understand that mprovi but hen again TWRP doesn't boot unfortunately
Click to expand...
Click to collapse
When you have flashed twrp, you do the buton combination to enter twrp, if you fail to enter twrp a the phone boots into system the stock recovery will be reflashed so you have to reflash twrp.
Try making these:
When you are in the bootloader after flashing twrp press button down+ power button. When the screen turns off quickly stop pressing power button and quickly press again until the lg logo appear.
When the lg logo appear stop pressing power button, quickly press again and stop pressing the power button and press again quickly until you see twrp logo.
These method works for me for booting twrp easily
The stock recovery appears but you have to select the factory reset option and it will boot into TWRP
mprovi_15 said:
When you have flashed twrp, you do the buton combination to enter twrp, if you fail to enter twrp a the phone boots into system the stock recovery will be reflashed so you have to reflash twrp.
Try making these:
When you are in the bootloader after flashing twrp press button down+ power button. When the screen turns off quickly stop pressing power button and quickly press again until the lg logo appear.
When the lg logo appear stop pressing power button, quickly press again and stop pressing the power button and press again quickly until you see twrp logo.
These method works for me for booting twrp easily
Click to expand...
Click to collapse
Unfortunately still not succeeded after trying all the solutions i've found here
Hey, i have the same Problem, my TWRP broke, i can't boot into recovery and my Device ist not listed in fastboot mode. Can someone help me out?
I get the ring in windows when i plugin but its not recognizing.. Can someone pls help me out?
Okay, I'm going to try to explain it, and see if I can succeed where others have not.
You install TWRP by booting to bootloader and using fastboot to push a new recovery:
Code:
fastboot flash recovery twrp.img
It seems like you accomplished that successfully. The next step is to immediately boot to recovery; do not boot the phone to system first. You will get the factory prompts for wiping data, but it will not actually wipe your data this time. Instead it will boot to TWRP.
Now, while you are in TWRP, you need to either root (flash Magisk) or install a custom ROM. If you do not, your next boot to system will remove TWRP and restore the stock recovery. If that happens, then the data-wiping prompts the next time you boot to recovery are real and the phone will wipe. So you MUST - must must must - root or install a custom ROM while you have TWRP up, in order for TWRP to persist.
If you have already experienced this problem, you need to start over at the beginning; flash TWRP again, and then follow the rest of these directions.
Maybe this will help clear up the problem for you guys.
dwasifar said:
Okay, I'm going to try to explain it, and see if I can succeed where others have not.
You install TWRP by booting to bootloader and using fastboot to push a new recovery:
Code:
fastboot flash recovery twrp.img
It seems like you accomplished that successfully. The next step is to immediately boot to recovery; do not boot the phone to system first. You will get the factory prompts for wiping data, but it will not actually wipe your data this time. Instead it will boot to TWRP.
Now, while you are in TWRP, you need to either root (flash Magisk) or install a custom ROM. If you do not, your next boot to system will remove TWRP and restore the stock recovery. If that happens, then the data-wiping prompts the next time you boot to recovery are real and the phone will wipe. So you MUST - must must must - root or install a custom ROM while you have TWRP up, in order for TWRP to persist.
If you have already experienced this problem, you need to start over at the beginning; flash TWRP again, and then follow the rest of these directions.
Maybe this will help clear up the problem for you guys.
Click to expand...
Click to collapse
Oh my god, i really really thanks for your reply, you're so fre*king good. U made my day.
Guys a little help
I only manage to see the TWRP welcome screen and the the phone automatically reboots to system
I can't get to see the TWRP menu at all!!
WTF is going on?
I have repeated the process many many times and always the same. What i am missing here?!?!?
me too when it boots in twrp only showing logo then it reboots in system what are wedoing wrong?
Got the same problem. I unlocked Bootloader, checked if unlocked (yes). After flashing TWRP i see the TeamWin Screen and phone boot again. There is no TeamWin Menu.
A try with an older TWRP-Version and flashing via fastboot with another PC does not work too.
Anybody an idea?
Did you guys manage to fix it?
Matt.
Hey, for me worked to flash TWRP 3.1.1.0.
3.2.1.0 & 3.2.2.0 still doesn't work.
Greetz
MiR4G3 said:
Hey, for me worked to flash TWRP 3.1.1.0.
3.2.1.0 & 3.2.2.0 still doesn't work.
Greetz
Click to expand...
Click to collapse
With 3.2.1.0, 3.2.2.0 and 3.2.3.0 it only briefly shows the TWRP screen and then boots into system anyway.
With 3.1.1.0 the key combination to boot into TWRP as with the other versions above simply doesn't work, again it directly boots into system without even showing the TWRP screen.
I'm stuck with a resetted phone because of this bull****, because some instructions said "oh, the reset dialog will not really reset your data..." - yeah thanks for nothing, buddy.
So what now?
EDIT: I got it working using TWRP 3.1.1.0, but the same version from the OFFICIAL site didn't work, as I described above.
The only 3.1.1.0 TWRP that works with my phone is the one from this Link: http://downloads.codefi.re/rashed/g6/
(which is linked ... somewhere here in the Forum, don't remember which thread)
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
abstractartemis said:
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
Click to expand...
Click to collapse
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
ashyx said:
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
Click to expand...
Click to collapse
So just keep flashing it until i can boot to twrp recovery basically?
abstractartemis said:
So just keep flashing it until i can boot to twrp recovery basically?
Click to expand...
Click to collapse
What's stopping you boot to Download mode?
ashyx said:
What's stopping you boot to Download mode?
Click to expand...
Click to collapse
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
abstractartemis said:
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
Click to expand...
Click to collapse
If you can flash twrp then not booting to twrp must be pilot error.
It MUST be done immediately after flashing in odin.