Hello
I have unlocked the boot loader
Booted into the bootloader "adb reboot bootloader"
I flashed twrp successful using fastboot
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (17524 KB)...
OKAY [ 0.402s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.567s
BUT when I try to boot into the recovery it doesn't work
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
I dont want to use the keycombo to try to get into twrp for the first since its tricky and if I fail I have to start over again?
rpsweb said:
Hello
I have unlocked the boot loader
Booted into the bootloader "adb reboot bootloader"
I flashed twrp successful using fastboot
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (17524 KB)...
OKAY [ 0.402s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.567s
BUT when I try to boot into the recovery it doesn't work
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.421s
I dont want to use the keycombo to try to get into twrp for the first since its tricky and if I fail I have to start over again?
Click to expand...
Click to collapse
If you don't want to use the combination then give up, it's the only way to boot in twrp the first time.
I talked some nice folks in #twrp on freenode irc chat for the h850 you to have to use version 3.0.2.1 most of guides refer to a earlier that won't stick
Sent from my LG-H850 using XDA-Developers mobile app
3.0.2.0 doesn't work.
3.0.2.1 works for me but only for one time, if I leave TWRP I don't have it anymore.
dymosilesia said:
3.0.2.0 doesn't work.
3.0.2.1 works for me but only for one time, if I leave TWRP I don't have it anymore.
Click to expand...
Click to collapse
Root the phone then you can flash twrp in andriod
dymosilesia said:
3.0.2.0 doesn't work.
3.0.2.1 works for me but only for one time, if I leave TWRP I don't have it anymore.
Click to expand...
Click to collapse
Thanks for this tip! I just saw this solution on another site too. However, where did you get 3.0.2.1? The TeamWin site shows 3.0.2 is the latest for the H850. Do you choose another device on their site? Could you post the version that you used here?
It's now posted and 3.0.2.1 and it fixed it for me! Thanks!!
https://dl.twrp.me/h850/
@rpsweb yeah that's right. I forgot about flashify. Thanks
Hey guys, newbie to installing custom ROMs so be gentle with me.
Someone gave me a rooted Xperia Z Ultra at Android 4.3.1. I previously wiped the device back to factory settings because the previous user didn't want their old data on it.
I wanted to install the latest ROM for it, so I found this thread and decided to give it a go:
https://forum.xda-developers.com/xp...elopment/rom-marshmallow-6-0-z-ultra-t3224321
I downloaded the image files and booted into fastboot mode.
ran the fastboot commands to install each img file and reboot the device. See below:
=====================================================
fastboot flash boot boot.img"
sending 'boot' (9856 KB)...
OKAY [ 0.318s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.979s
fastboot flash cache cache.img"
sending 'cache' (5800 KB)...
OKAY [ 0.191s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.204s
fastboot flash system system.img"
sending 'system' (601241 KB)...
OKAY [ 18.878s]
writing 'system'...
OKAY [ 43.825s]
finished. total time: 62.710s
fastboot flash userdata userdata.img"
sending 'userdata' (137490 KB)...
OKAY [ 4.346s]
writing 'userdata'...
OKAY [ 9.231s]
finished. total time: 13.583s
=========================================================
Once it rebooted it never came back up again. I waited about 30 minutes just to be sure. The computer still recognizes it and I can boot into fastboot mode, but the phone never boots back into regular boot mode anymore.
Wondering if anyone has any thoughts on this?
Thanks
Bump!
deeeyewhy said:
Hey guys, newbie to installing custom ROMs so be gentle with me.
Someone gave me a rooted Xperia Z Ultra at Android 4.3.1. I previously wiped the device back to factory settings because the previous user didn't want their old data on it.
I wanted to install the latest ROM for it, so I found this thread and decided to give it a go:
https://forum.xda-developers.com/xp...elopment/rom-marshmallow-6-0-z-ultra-t3224321
I downloaded the image files and booted into fastboot mode.
ran the fastboot commands to install each img file and reboot the device. See below:
=====================================================
fastboot flash boot boot.img"
sending 'boot' (9856 KB)...
OKAY [ 0.318s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.979s
fastboot flash cache cache.img"
sending 'cache' (5800 KB)...
OKAY [ 0.191s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.204s
fastboot flash system system.img"
sending 'system' (601241 KB)...
OKAY [ 18.878s]
writing 'system'...
OKAY [ 43.825s]
finished. total time: 62.710s
fastboot flash userdata userdata.img"
sending 'userdata' (137490 KB)...
OKAY [ 4.346s]
writing 'userdata'...
OKAY [ 9.231s]
finished. total time: 13.583s
=========================================================
Once it rebooted it never came back up again. I waited about 30 minutes just to be sure. The computer still recognizes it and I can boot into fastboot mode, but the phone never boots back into regular boot mode anymore.
Wondering if anyone has any thoughts on this?
Thanks
Click to expand...
Click to collapse
If the ZU had 4.3 on it, its possible you have to flash the latest stock rom. I think I recall reading something about needing to flash the latest stock at least once before flashing any mm or nougat rom.
Flash the 4.4.4 ftf with flashtool. Then install xzu dual recovery by nut. After that install whatever ROM/mod you like.
hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Try this
cappone said:
hi, have some difficulties to flash twrp.img
i try fastboot flash recovery recovery.img but i get this error
Code:
B:\Download\Compressed\platform-tools-latest-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (52396 KB)...
OKAY [ 5.923s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 5.947s
phone is unlock debug is enable and signature app verification is disable
P.S thx in advance
Click to expand...
Click to collapse
Hi there,
was wondering did you put the recovery file into the installation folder of ADB
yes, thats not the the problem, i manage to root my phone but cant to write TWRP, i get the same msg tried many toolkits and results is the same...
Since Oreo: Partition names have changed and "recovery" changed to "recovery_ramdisk".
Try:
fastboot flash recovery_ramdisk twrp.img
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
hdano said:
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Click to expand...
Click to collapse
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
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:
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
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
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-BD 1.0.0.40(log)
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.022s
C:\adb>
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
finished. total time: 0.018s
C:\adb>
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.021s
hdano said:
any ideas
Click to expand...
Click to collapse
maybe the following will help you:
- Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Note: you do everything at your own risk, I hope that's clear
Hi Alf,
thanks for reply,
worked like a charm !
Phone booted in official rom, was working well.
But..
If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB ,
but after downloading phone shows install error.
I did factory reset and cache clear, same result, can not install.
So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip
but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed"
After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-(
Now not booting again, stuck in this error.
So how can I update to some new sw ?
Do I have to use some special version to go higher?
Or is it some other problem?
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said:
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet
Click to expand...
Click to collapse
Yes, service ROM lock the bootloader , it's normal.
hdano said:
FRP locked,
Click to expand...
Click to collapse
You can unlock FRP manually in Developer options - "Enable OEM unlock".
Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
hdano said:
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
Click to expand...
Click to collapse
Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said:
This ***** sucks
Click to expand...
Click to collapse
Try to install .174 Service ROM via dload method.
If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot.
You can use this tutorial . Use downloaded .174 ROM. Extract and flash
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
Note: cust.img can be found in update_ane-L21_hw_eu
Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.893s]
writing 'kernel'...
OKAY [ 0.388s]
finished. total time: 1.286s
C:\adb>fastboot flash ramdisk RAMDISK.IMG
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.602s]
writing 'ramdisk'...
OKAY [ 0.075s]
finished. total time: 0.681s
C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.208s]
writing 'recovery_ramdisk'...
OKAY [ 0.169s]
finished. total time: 1.381s
C:\adb>fastboot flash system SYSTEM.IMG
target reported max download size of 471859200 bytes
sending sparse 'system' 1/8 (460799 KB)...
OKAY [ 19.946s]
writing 'system' 1/8...
OKAY [ 3.866s]
sending sparse 'system' 2/8 (424020 KB)...
OKAY [ 17.042s]
writing 'system' 2/8...
OKAY [ 2.164s]
sending sparse 'system' 3/8 (458375 KB)...
OKAY [ 18.384s]
writing 'system' 3/8...
OKAY [ 2.219s]
sending sparse 'system' 4/8 (460418 KB)...
OKAY [ 18.557s]
writing 'system' 4/8...
OKAY [ 2.213s]
sending sparse 'system' 5/8 (425536 KB)...
OKAY [ 17.164s]
writing 'system' 5/8...
OKAY [ 2.157s]
sending sparse 'system' 6/8 (457971 KB)...
OKAY [ 19.231s]
writing 'system' 6/8...
OKAY [ 2.855s]
sending sparse 'system' 7/8 (460016 KB)...
OKAY [ 19.003s]
writing 'system' 7/8...
OKAY [ 3.147s]
sending sparse 'system' 8/8 (192362 KB)...
OKAY [ 7.791s]
writing 'system' 8/8...
OKAY [ 1.015s]
finished. total time: 156.792s
C:\adb>fastboot flash cust CUST.IMG
target reported max download size of 471859200 bytes
sending 'cust' (139283 KB)...
OKAY [ 5.096s]
writing 'cust'...
OKAY [ 0.794s]
finished. total time: 5.894s
C:\adb>fastboot reboot
rebooting...
Now the only I can get is this, no way to get in eRecovery
hdano said:
Now the only I can get is this, no way to get in eRecovery
Click to expand...
Click to collapse
Chinese??? Wow...
As I said before,
-Alf- said:
turn off the phone, then flash .174 Service ROM
Click to expand...
Click to collapse
Have you tried bro?
-Alf- said:
Chinese??? Wow...
As I said before,
Have you tried bro?
Click to expand...
Click to collapse
how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said:
how? I can not get in eRecovery, only that chinese recovery or what it is....
Click to expand...
Click to collapse
Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again,
Board sw 1.0.0.39 , and
-Alf- said:
Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Click to expand...
Click to collapse
But I can not get it to work state, 3 button combo always fails.
Can I just simply flash all needed files by fastboot ot TWRP ?
What are all the necessary files for phone to boot up?
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
what else?
Can I just simply flash some custom ROM that will boot up after TWRP flash ?
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (24790 KB)...
OKAY [ 0.660s]
writing 'erecovery_ramdisk'...
OKAY [ 0.128s]
finished. total time: 0.796s
hdano said:
what else?
Click to expand...
Click to collapse
Nothing.
But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...).
hdano said:
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
Click to expand...
Click to collapse
Running working stock firmware it's impossible.
hdano said:
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
Click to expand...
Click to collapse
I’ve exactly the same as your issue.
But I’ve no service and dual iemis are right!
What could be the problem, did you solve yours?
Or even were you having same no service issue while you were on this case?
My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools.
Also using howta8 to change oeminfo.
It was changed ok to c185 but still no service and software not installed.
I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder