Hi,
I have done a lot of rooting etc but a while since and not hit this before.
Unlocked the Mi9 with tool (it says unlocked on reboot).
Flashed Twrp_3.3.0_Cepheusv12 by extracting recovery.img and fastboot flash recovery recovery.img
Says it has installed OK but I can't get in to TWRP, I hold down the volume up button and then hold power till it restarts but either loops back or if I leave it, just goes in to stock ROM (which I am trying to get rid of !).
Any clues ?
Related
Hi,
I'm very new to rooting and such and only followed guides a read forum posts to get to where I am now.
My phone is rooted with stock ROM and SU, the bootloader is unlocked but no S-OFF (don't think it's possible on the mini 2 yet anyway). The new OTA update last night installed when I got home and charged my phone, then the phone just shut off and every time I tried to boot it would go straight into TWRP without showing splash screen or bootloader (even when holding power and the volume down button). When it's in this state the touch screen doesn't work and the power button only locks the phone. Holding power + vol down in this state doesn't do anything.
I have to let the power drain completely to get the phone to boot back up but it immediately boots back into recovery and then I can use ADB to force the bootloader to appear, but when I flashed the stock recovery that I found in these boards, it messes up the screen and all it shows is static with some artifacts. I have to let the power drain again to get back into the bootloader, and from the bootloader I can get the android OS to boot but I'd like to fix this completely.
I guess I should also mention that even after flashing the stock recovery the phone will still boot back into TWRP after I let the power drain so I think that means that the stock recovery isn't taking?
The twrp problem you mentioned is known, hope it'll be fixed soon. Are you sure you typed the right command to flash stock recovery? Fastboot flash recovery recovery.img?
If you get stuck, the combination is power button and volume up, not volume down...
gibihr said:
The twrp problem you mentioned is known, hope it'll be fixed soon. Are you sure you typed the right command to flash stock recovery? Fastboot flash recovery recovery.img?
If you get stuck, the combination is power button and volume up, not volume down...
Click to expand...
Click to collapse
Unfortunately I was using the wrong ADB command, I was typing "fastboot boot recovery.img". This seems to have fixed the problem so far but I have yet to try rewriting TWRP back to the phone and I probably won't until theres a fix or unless I need to.
Thank you for your help.
Fierfly said:
Unfortunately I was using the wrong ADB command, I was typing "fastboot boot recovery.img". This seems to have fixed the problem so far but I have yet to try rewriting TWRP back to the phone and I probably won't until theres a fix or unless I need to.
Thank you for your help.
Click to expand...
Click to collapse
I had the same problem. It happens when I reboot with my phone when charging.
You can reboot your phone by holding vol up+power button.
Hello,
After 1.5 years on B136 I've decided to move to a Lollipop rom. I've wiped my device, flashed stock recovery from B609 and wanted to force-update from sd card .... and device didn't boot into recovery at all.
So far the only recovery that works for me is TWRP, but I can't flash stock roms with it. When I flash (with fastboot) a stock recovery (doesn't matter which, I;ve tried B133Sp01, B136, B609, B852), my device goes into bootloop or just reboots while in the recovery.
I need to rescue my phone now.
Any ideas... ?
This is as far as I get:
Extracted cust / boot / recovery and system from B136 and flashed them with fastboot.
Device reboots, shows Huawei logo, plays animation and sound. After a while - it reboots and goes into recovery.
Recovery is in chinese.
Device stays in recovery for a few seconds then reboots itself.
And on and on....
Does anyone have any clue why this device keeps rebooting itself all the time?
Update:
Since TWRP was working for me, I've tried couple custom roms. Results:
TWRP + material one test rom: flashed fine, got boot screen, got boot animation.... device reboots. After second reboot goes into recovery.
TWRP + B609 test port: same as above.
What can it be that makes my device reboot over and over again, even when in recovery?
I'm out of ideas. Please help.
Thanks.
@GawDroid, try my method,
Download B852 official ROM and copy it to root of your SD card to a new folder "dload"
It should look like this "/dload/UPDATE.APP"
Extract UPDATE.APP (on your computer) using Huawei Update Extractor (all files)
Go into bootloader (Power + Vol Down)
Now open command line and use ADB (Android Debugging Bridge) to send following commands to your phone:
fastboot flash recovery RECOVERY.IMG
fastboot flash boot BOOT.IMG
Now force update by turning off your phone, and turing him back on while holding all 3 buttons pressed down.
When screen comes on release the Power button but keep holding both Volume rockers pressed down until you see an EMUI logo.
If for any reason it fails to install, go back into recovery and do Wipe data/Factory Reset, and than try again.
Let us know how it went
Okay, I did exactly this today:
Extracted boot and recovery from B852 update.app
Flashed both with fastboot
Put dload/update.app on sd card
Started phone in force update mode (vol +, vol -, power)
Phone shows "Huawei Ascend" logo for 30 seconds and shuts down.
I cannot enter recovery either. Phone does the same as above (huawei screen, shutdown).
I have never had an EMUI 3 rom installed before, maybe that's why this recovery can't start? Just guessing...
,
Flash the boot.img first and then the update
Enviado desde mi HUAWEI P7-L10 mediante Tapatalk
Fefo64 said:
Flash the boot.img first and then the update
Click to expand...
Click to collapse
This is how I did it. First boot.img, then recovery.img, then tried to update.
Up. Any ideas why it keeps rebooting regardless of ROM, or even in recovery?
Hi guys,
My firmware is stuck on emui 4.1 and I'm trying to install a custom Rom.
Bootloader unlocked fine
adb worked fine
I've flashed twrp
However, whenever I try to reboot I get the "your phone can't be trusted" boot recovery screen instead of TWRP, so I can't root.
I've tried power and up, power and down, and power and up and down.
They either go to the recovery option screen, then boot like normal, or hangs on the normal boot screen
Any suggestions
Things repeated several times elswhere.
1. Your phone cannot be trusted because you unlocked the bootloader. If you don't like it, re-lock bootloader ;-(
2. Upon flashing TWRP, FIRST THING YOU MUST DO is rebooting to TWRP. If you don't do that, stock Recovery will ovewrite TWRP.
Find instructions in the TWRP threads how to enforce immediate booting to TWRP, upon you flashed it:
-Type on the PC: fastboot reboot -but don't press Enter yet.
-Press and keep pressing Vol+ and Power buttons together on the phone
-Press Enter on the PC and then immediately unplug USB cabel.
-When phone shows Booting, release Power but keep pressing Vol+. button
Hi,
I was trying to install Linage OS 14 on my H9L and I got it installed fine. I then tried flashing TWRP with `fastboot flash recovery_ramdisk twrp.img` I then did `fastboot reboot` and once back into Linage I rebooted into TWRP from the power menu. After this TWRP got stuck on the loading screen so I tried rebooting, the phone rebooted back into TWRP and got stuck again. I then tried getting into fastboot by plugging in the USB and holding the volume down, rebooted into TWRP still. I then managed to get out by holding the power button and the + and - volume buttons to get into eRecovery. I then tried to do reset by doing 'Install latest version over WiFi' which downloads then fails and now I can't boot up my phone and it just goes straight to eRecovery every time I boot it up. I can still get into fastboot and I've tried flashing recovery_ramdisk, ramdisk from both a system update zip and from a TWRP backup with also no luck. At this point I really just want to get back to stock.
If anyone can help I'd really really appreciate it and be forever grateful .
Thanks,
Jake
jcbod said:
Hi,
I was trying to install Linage OS 14 on my H9L and I got it installed fine. I then tried flashing TWRP with `fastboot flash recovery_ramdisk twrp.img` I then did `fastboot reboot` and once back into Linage I rebooted into TWRP from the power menu. After this TWRP got stuck on the loading screen so I tried rebooting, the phone rebooted back into TWRP and got stuck again. I then tried getting into fastboot by plugging in the USB and holding the volume down, rebooted into TWRP still. I then managed to get out by holding the power button and the + and - volume buttons to get into eRecovery. I then tried to do reset by doing 'Install latest version over WiFi' which downloads then fails and now I can't boot up my phone and it just goes straight to eRecovery every time I boot it up. I can still get into fastboot and I've tried flashing recovery_ramdisk, ramdisk from both a system update zip and from a TWRP backup with also no luck. At this point I really just want to get back to stock.
If anyone can help I'd really really appreciate it and be forever grateful .
Thanks,
Jake
Click to expand...
Click to collapse
I also cannot flash TWRP anymore.
Power down phone, then plug a USB cable into PC then phone. Whilst plug Cale into phone press and hold volume up.
This should place you into Fastboot mode.
What does it say for FRP.
If it says that is locked that would be your issue of why you can not flash anything.
Sent from my LLD-L31 using Tapatalk
A small typo above from @hacktrix2006 , Vol Up will actually bring you to eRecovery.
Vol Down will bring you to fastboot mode.
@Sparkrite , nice catch that is what i ment. When i replied i was awake for at total of 1 minute so brain wasn't fully working right.
I need help. I deleted/wiped in advanced mode in twrp the system and now I have No OS installed. I don't kow what to do now the phone does not bood except into twrp.
Use NOST
Sent from my NB1 using XDA Labs
After hours of "work" I have my phone running again. I was able to get the phone run stock recovery again and then was easy to just flash the oreo zip.
well good to know you solved the problem.
but just in case keep your phone bootloader critical unlocked so you can use NOST if you face such problems again.
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
theviking33 said:
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
Click to expand...
Click to collapse
I am at such condition too... how long battery lasts? I think it's possible to wait for the phone to fully discharge and then we may have access to recovery. right?
theviking33 said:
Just happened again. I wanted to put twrp img back on the phone and as it reboots... its stuck on "Powered by Android". I cannot flash or do anything since its stuck and does not turn off. I tried all combinations of volume/power button and hold them for minutes... just does not turn off. So its not recognized by NOST or anything. Now I am really screwed as it seems...
Click to expand...
Click to collapse
If you tried to "fastboot boot" the TWRP image: thats "normal", fastboot boot is broken on every firmware since august. You have to flash TWRP to your active boot partition to boot it. However, at least for me, when being stuck in that screen I can still use "fastboot reboot" or "fastboot reboot-bootloader" to get the phone back in a working state.
Also, if you try to flash TWRP to your active boot: Please don't flash the image from the official site, since that is unable to boot into the system normally. Use my recompiled generic TWRP boot image that you can flash, regardless of security patch version: https://forum.xda-developers.com/nokia-8/development/twrp-data-decryption-android-9-t3911411
If you did not fastboot boot an image: Hold down volume up, volume down and power for multiple minutes until the phone turns off. Then hold volume down while connecting the phone to a computer through USB, and it will start into fastboot mode. Then just revert whatever you changed and reflash the stock image.
THMSP said:
If you tried to "fastboot boot" the TWRP image: thats "normal", fastboot boot is broken on every firmware since august. You have to flash TWRP to your active boot partition to boot it. However, at least for me, when being stuck in that screen I can still use "fastboot reboot" or "fastboot reboot-bootloader" to get the phone back in a working state.
Also, if you try to flash TWRP to your active boot: Please don't flash the image from the official site, since that is unable to boot into the system normally. Use my recompiled generic TWRP boot image that you can flash, regardless of security patch version: https://forum.xda-developers.com/nokia-8/development/twrp-data-decryption-android-9-t3911411
If you did not fastboot boot an image: Hold down volume up, volume down and power for multiple minutes until the phone turns off. Then hold volume down while connecting the phone to a computer through USB, and it will start into fastboot mode. Then just revert whatever you changed and reflash the stock image.
Click to expand...
Click to collapse
It turns out that there was Pie on my partition B and I was not aware of that. Booting into TWRP wasn't working, so I flashed it and then factory reset system. And it broke the phone.
Now I tried to boot the TWRP from slot B and rebooted partition A. Now the phone is up... Thanks
Where can I find the appropriate stock boot image for my partition B? and should I fastboot it with boot_b command or what?