I am not a developer, but would like to consider myself an advanced user.
After unlocking the bootloader, I have installed custom ROMs on three different devices at different times. I have also installed the stock ROM. But have never locked the bootloader back.
However, on the current device (that was looping through the bootloader), I installed the stock ROM (RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC.xml) and locked the bootloader. Successfully updated it to the official OTA Lollipop 5.1.
After that, I just tried my luck to install Ubuntu Touch (ported actually for Moto G [falcon] by h2o64, based on this thread). I unlocked the bootloader again for this. The install was 'successful' (there were no errors surprisingly), but the device obviously did not boot.
Now, I wanted to reinstall the stock firmware on the device. This time however, it fails at this command:
sudo fastboot flash partition gpt.bin
Here's the result >
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.087s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.667s
I have used fastboot in Linux all the other times I said I installed custom and stock ROMs.
However, I tested with mfastboot on Windows 10 as well, with no luck.
I am also able to successfully install TWRP recovery on the device and erase "system", "cache" and "userdata" using fastboot. However, cache and dalvik cache removal fails on TWRP.
Finally, although the partition flash command (which I personally understand as creating the partition table - correct me here please) and the motoboot.img flash command failed, I ran the rest of the commands and successfully installed the stock ROM mentioned above. However, this time, the "fastboot oem lock" command fails.
Any suggestions would be of great help... (it's not my phone)
i tried to install twrp in my Xiaomi mi a3 but the command not worked, i tried to change the slot to b, so i execute the command, but still nothing. I use mi flash Tool to redo a clean install of the system without first replacing the slot equal to b, also the procedure locked the bootloader. Now I don't know what to do anymore, I ask you for help!
RattlyFern41846 said:
i tried to install twrp in my Xiaomi mi a3 but the command not worked, i tried to change the slot to b, so i execute the command, but still nothing. I use mi flash Tool to redo a clean install of the system without first replacing the slot equal to, also the procedure locked the bootloader. Now I don't know what to do anymore, I ask you for help!
Click to expand...
Click to collapse
Does this command work for you ?
fastboot flashing unlock
fastboot flashing unlock_critical
RizwanH20 said:
Does this command work for you ?
fastboot flashing unlock
fastboot flashing unlock_critical
Click to expand...
Click to collapse
response of the first command:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
response of the second command:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Hi everyone!
I want to install TWRP on a P20 Lite with the main goal to install LOS16 and possible other custom ROMs. Therefore I was following the official guide on LOS.
However when I try to boot/flash the TWRP image-file with fastboot i receive the following error:
Problem
Code:
$>fastboot flash recovery twrp.img
Sending 'recovery' (14946 KB) OKAY [ 0.396s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
$>fastboot boot twrp.img
Sending 'boot.img' (14946 KB) OKAY [ 0.376s]
Booting FAILED (remote: 'invalid command')
fastboot: error: Command failed
Error is shown in admin command line as well.
Furthermore I get the following error which let me think that it is more of a fastboot problem.
Code:
$>fastboot getvar version
getvar:version FAILED (remote: 'invalid command')
$>fastboot oem device-info
FAILED (remote: 'invalid command')
fastboot: error: Command failed
Specs
Phone: Huawei P20 Lite ANE-LX1
Build:9.1.0.377(C432E7R1P7)
EMUI-Version 9.1.0
Bootloader unlocked - PHONE Unlocked, FRP unlocked (via PotatoNV method with same adb/fastboot installation).
Adb:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Info
Same error with adb/fastboot from two different PCs (Win10). Adb and fastboot seem to work in general. For example both show the device in List of devices attached and i can reboot and boot via adb and fastboot.
As I understand this post it is not possible to flash twrp directly on android 9.
However I tried the twrp file linked in the mentioned post and several images linked in this forum (this, this) + the one from twrp-anne and got the same error fastboot: error: Command failed on all.
Does anybody know or has a hint what might be the problem? Any help appreciated.
Best regards
I had the same issue.
You have to use the command: fastboot flash recovery_ramdisk twrp.img
yellowzebra said:
As I understand this post it is not possible to flash twrp directly on android 9.
Click to expand...
Click to collapse
Hello, please read carefully :
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
Click to expand...
Click to collapse
-Alf- said:
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
Click to expand...
Click to collapse
- eRecovery and Recovery are two different things .
That worked!
Thank you very much. Both of you for the fast answer
I am currently researching before asking more noob questions. Have some thoughts. Especially on difference between eRecovery and Recovery and why commands as fastboot oem device info where not working before the recovery_ramdisk. Might return later.
Thx!
Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Quantumstate said:
Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Click to expand...
Click to collapse
Sounds like you need to flash stock Motorola firmware.
I never thought an app could do such damage to a phone even after reinstalling firmware.
I've now also lost all of my Signal SMS history (Havoc 4.12) because in Permissions the only ones available for Signal are Media Only or None. It needs Files permission to restore the backups, but it is just not an option.
It's worse now. I installed Stock using my instructions over here, but I installed Android 11, not having seen Beetle's post below. In TWRP I got all kinds of permission denied errors on /data/. So I then downloaded Android 10 from here, and
# fastboot flash partition gpt.bin
...which went fine. But then
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.414s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
No idea what is wrong. The partitions should have been written. My phone's down hard now. Booting into fastboot I do not get the normal way it looks, but a mostly blank screen with Start in the center, and text at bottom acknowleging it's connected. And it does answer up to # fastboot devices. I've downloaded the stock image twice and same issue.
I can't find an older Android 10, in the hope that it will fix this. I believe that Android 10 is required for all versions of Havoc, but I can't even get to Stock at this point. Feel like drinking but won't,
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.385s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this. I suspect this happened because I tried to roll back from stock Android 11 to 10. I've tried going back to 11 and every which way.
Looks like this phone is ruined. I've tried everything I can think of. out of ideas.
Yep, did a complete fastboot flash reinstall of Stock 11, and still the earpiece does not work. Phone is the default calling app.
This phone is unusable except in speakerphone. I've ordered another Moto G Power 2020 as it's so good otherwise, even without call recording. But AVOID CallX!
Beetle84 once said to not install Stock 11 then Havoc, that it must be Stock 10, but it is unclear whether that applies to the current Havoc 4.12 which is based on Android 11?
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Quantumstate said:
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Click to expand...
Click to collapse
That's not good. May I suggest supporting the efforts of the Pine64 folks?
Quantumstate said:
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this.
Click to expand...
Click to collapse
Did you try wiping metadata entirely?
I had the same problem with the bootloader refusing to allow downgrading the bootloader after installing Motorola's Android 11 firmware. Even so LineageOS is running fine on the device's Slot A right now. Read my post over here.
I did something like: (Exact steps weren't noted. Sorry, no desire to retest on a now working device used by a family member.)
Booted into the bootloader and flashed Motorola's Android 11 stock firmware from XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on Slot A, minus vbmeta and super
fastboot set_active a
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot oem fb_mode_clear
Rebooted into fastbootd (fastboot reboot fastboot) and flashed LineageOS fastbootd images from lineage-18.1-20211219-UNOFFICIAL-FASTBOOTD-sofiar.zip
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
Returned to the bootloader (fastboot reboot bootloader) and wiped data
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Rebooted (fastboot reboot) into LineageOS, it booted successfully and runs fine. Rooting wasn't tested. Before trying LineageOS fastbootd images I installed crDroid through TWRP and booted it with success. It had some weird bugs unfortunately, most importantly being unable to serve as a working phone. My family member was very happy with an older version of crDroid from around June on the Android 10 firmware.
I fixed the /medadata error by (in TWRP)
- Unmount /metadata
- Disable MBR
- Format /metadata.
Problem is metadata was encrypted and 11 couldn't tell from 10.
Now all the /loop's on inactive slot b are inaccessible. I could keep jacking with it but ran out of time. And running Stock in slot a I find I still have the earphone problem so gave up and ordered another phone. It should never be possible for an app to do this kind of damage.
Yes I've noticed the Pine64 project, although one thing I require is a water-resistant phone. There will come a point, in view of the awful changes in Android 12, where I may move to a Pine phone. As it is, for years I've run no gapps, do not use the Play store, nor anything else G**gle except the OS. And I choke the OS off with AFWall+ in F-Droid.
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?