Related
Hello everybody. (sorry for my writing mistakes )
XT910 with stock firmware: http://savepic.org/6550017.png
IMEI - EMEA region
Worked fine.
But then...
Through BMM installed - LiquidSmooth KitKat (http://forum.xda-developers.com/showthread.php?t=2782971)
and then
"SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_ASIA_RETAIL_HKTW_CFC_HWp2b_SIGNED.xml.zip"
(I do not know why. It was not me. But I want to help restore the phone.)
When the process is finished (Successfully О_о), the phone no longer worked.
Now:
Normally mode, Recovery - not working:
Invalid Flash Mode (S) (Boot Failure)
0A.77
To return to normal mode - first press power key to poser down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X004E)
Invalid CG OTV (CG: system)
What we tried to install (AP Fastboot - RSDLite 6.1.5):
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_AUSTRALIA_NZ_CFC_HWp2b_SIGNED.xml.zip
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_AUSTRALIA_OPTUS_CFC_HWp2b_SIGNED.xml.zip
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_MEA_RETAIL_CFC_HWp2b_SIGNED.xml.zip
- SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSO2DE_HWp2b_Service1FF_fastboot.xml.zip
- SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip
- 673.94.324.XT910.AsiaRetail.en.03.xml.
- 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RTFE1007.0R_USASPDRJBRTFR_P013_A014_p2b_S1FF_fb_CFC.xml.zip (Retail FR)
- 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml.zip (Retail GB)
Always:
11/28/14 11:48:56 [Device ID: 0] 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin"
11/28/14 11:48:56 [Device ID: 0] 2/19 reboot-bootloader
11/28/14 11:49:00 [Device ID: 0] 3/19 flash mbmloader "mbmloader.bin"
11/28/14 11:49:01 [Device ID: 0] 4/19 flash mbm "mbm.bin"
11/28/14 11:49:02 [Device ID: 0] 5/19 reboot-bootloader
11/28/14 11:49:06 [Device ID: 0] 6/19 flash cdt.bin "cdt.bin_signed"
11/28/14 11:49:06 ERROR: 6/19 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL. - on device ID 0.
11/28/14 11:49:06 [Device ID: 0] 6/19 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL.
11/28/14 11:49:06 ERROR: Failed flashing process. - on device ID 0.
This metod:
1-download cdt.bin ( http://www.mediafire.com/?ua1nj6ds6r0vtue )
2-download fastboot files ( http://dfiles.eu/files/bih3tmg7b )
3-restart your phone in to bootloader ( fastboot ) mode
4-connect your phone via usb cable
5-open cmd.exe in your pc an go to fastboot files
6-flash cdt.bin via this command -------------------------------------- fastboot flash cdt.bin cdt.bin
7-restart your phone in to stock recovery
8-do triple wipe and restart your phone
Nothing helps! Can you help? What can we do?
Thanks for help...
No one has any ideas?
that's interesting: tried to remove CID and failed, because: (see picture)
Code:
Erasing CID ... INFOCommand Restricted
Wrong command?
And:
Code:
CID:5
XT910S ?
Why can not we delete CID?
Thanks for "help".
Mission completed.
Thread is closed.
did u manage to fix your i have the same problem with you please some one should help,i just want to get my phone back to normal, i have the same firmware with u
jamil1982 said:
did u manage to fix your i have the same problem with you please some one should help,i just want to get my phone back to normal, i have the same firmware with u
Click to expand...
Click to collapse
This is my script for FastBoot (0A:77 Bootloader and for XT910S)
Warning! This will remove your CID!
Use this method only when all other methods have failed.
https :// yadi .sk/d/M2EmR9HKdA3pF
unpack RAR: in C:/MyRecover/
Connect your phone (AP Fastboot mode) to PC.
Run MyRecoverV1.bat
done.
After that, you can install any firmware (RSDLite 6.1.5)
reccomend: Britain Retail 4.1.2 : https :// yadi .sk/d/zcq12jT5d44mu
After finish all task whitout errors, reboot cellphone, press Volume up, volume down and Power, and selet "BP Tools"
Get Root
Install BMM 0.3.4
Now your phone loaded automatically (without BP TOOLS)
VasyaAgPro said:
This is my script for FastBoot (0A:77 Bootloader and for XT910S)
Warning! This will remove your CID!
Use this method only when all other methods have failed.
https :// yadi .sk/d/M2EmR9HKdA3pF
unpack RAR: in C:/MyRecover/
Connect your phone (AP Fastboot mode) to PC.
Run MyRecoverV1.bat
done.
After that, you can install any firmware (RSDLite 6.1.5)
reccomend: Britain Retail 4.1.2 : https :// yadi .sk/d/zcq12jT5d44mu
After finish all task whitout errors, reboot cellphone, press Volume up, volume down and Power, and selet "BP Tools"
Get Root
Install BMM 0.3.4
Now your phone loaded automatically (without BP TOOLS)
Click to expand...
Click to collapse
Downloading Right now thank You i will give u feed back:good:
after running my MyRecoverV1.bat see what i got
---------------------------------------------------------------
Delete CID for kwyjibo jr by Vasya
---------------------------------------------------------------
Press any key to continue . . .
---------------------------------------------------------------
getvar:all FAILED (remote: unsupported command)
finished. total time: 0.008s
getvar:all FAILED (remote: unsupported command)
---------------------------------------------------------------
0A3BEC240400A007 fastboot
0A3BEC240400A007 fastboot
CID delete:
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
sending 'mbm' (512 KB)... OKAY [ 0.089s]
writing 'mbm'... OKAY [ 0.486s]
sending 'mbm' (512 KB)... OKAY [ 0.089s]
writing 'mbm'... OKAY [ 0.507s]
finished. total time: 0.596s
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.011s
rebooting into bootloader... OKAY [ 0.008s]
finished. total time: 0.009s
< waiting for device >
sending 'mbm' (512 KB)... OKAY [ 0.102s]
writing 'mbm'... OKAY [ 0.489s]
sending 'mbm' (512 KB)... OKAY [ 0.103s]
writing 'mbm'... OKAY [ 0.483s]
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
rebooting into bootloader... OKAY [ 0.007s]
< waiting for device >
sending 'mbm' (512 KB)... OKAY [ 0.102s]
writing 'mbm'... OKAY [ 0.488s]
finished. total time: 0.592s
sending 'mbm' (512 KB)... OKAY [ 0.090s]
writing 'mbm'... OKAY [ 0.508s]
finished. total time: 0.599s
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
rebooting into bootloader... OKAY [ 0.006s]
finished. total time: 0.007s
< waiting for device >
cid: 5
finished. total time: 0.018s
Press any key to continue . . .
any help please?
this is what my phone is showing
jamil1982 said:
this is what my phone is showing
Click to expand...
Click to collapse
CID not erased, for 0A:74 BootLoader try to use:
http://forum.xda-developers.com/showthread.php?t=2372614
If you want to check, removed CID or not:
Just see on last line in MyRecoverV1:
Code:
< waiting for device >
[COLOR="Red"]cid: 5[/COLOR]
finished. total time: 0.018s
When CID : DEAD - you win
If another thread not helps you:
Run MyRecoverV2 and MyRecoverV3 and again V1
it should help.
VasyaAgPro said:
CID not erased, for 0A:74 BootLoader try to use:
http://forum.xda-developers.com/showthread.php?t=2372614
If you want to check, removed CID or not:
Just see on last line in MyRecoverV1:
Code:
< waiting for device >
[COLOR="Red"]cid: 5[/COLOR]
finished. total time: 0.018s
When CID : DEAD - you win
If another thread not helps you:
Run MyRecoverV2 and MyRecoverV3 and again V1
it should help.
Click to expand...
Click to collapse
thanks i will check the link please can u give me the easy way on how to make a motorola factory cable? i have some factory cables that came with my polar 3 box whenever i connect the cable from my phone to the system the phone show white led light and my system doesnt recognize the phone so i dont know if the phone is charging or not and im afraid of loosing the power battery,but with normal cable my system recognize it but the white led light doesnt show, thank you once again
---------- Post added at 09:14 AM ---------- Previous post was at 08:45 AM ----------
strange i run all the bat but it give me the same
cid: 5
jamil1982 said:
thanks i will check the link please can u give me the easy way on how to make a motorola factory cable? i have some factory cables that came with my polar 3 box whenever i connect the cable from my phone to the system the phone show white led light and my system doesnt recognize the phone so i dont know if the phone is charging or not and im afraid of loosing the power battery,but with normal cable my system recognize it but the white led light doesnt show, thank you once again
Click to expand...
Click to collapse
Only one way for factory cable: (see picture)
jamil1982 said:
strange i run all the bat but it give me the same
cid: 5
Click to expand...
Click to collapse
Now run MyrecoverV2 and V3, then V1 for check.
VasyaAgPro said:
Only one way for factory cable: (see picture)
Now run MyrecoverV2 and V3, then V1 for check.
Click to expand...
Click to collapse
I run the V2 and V3 then Run the V1 again it showed the same thing, but I noticed its like the number has change from 0a.74 to 0A.74 and now its Showing 0A.75
jamil1982 said:
I run the V2 and V3 then Run the V1 again it showed the same thing, but I noticed its like the number has change from 0a.74 to 0A.74 and now its Showing 0A.75
Click to expand...
Click to collapse
hmm...
now - run all .bat files - V1, then 2, then 3 (after 3 NOT run again 1 !)
and finally "info.bat. (https :// yadi .sk/d/HdYWqS1gdAhfr)
Put info.bat to "MyRecovery" dir and run.
Log insert here.
VasyaAgPro said:
hmm...
now - run all .bat files - V1, then 2, then 3 (after 3 NOT run again 1 !)
and finally "info.bat. (https :// yadi .sk/d/HdYWqS1gdAhfr)
Put info.bat to "MyRecovery" dir and run.
Log insert here.
Click to expand...
Click to collapse
OHHH MY G You are Genius :good: after running Myrecover1 again it deleted the cid everything went smooth and the number on my Ap fastboot display 0A.77 then i run this 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml.zip, it run perfect without any error:laugh: then my phone restart showing Costumer error. Contact Resseller, the i off it and on it to boot menu then select Bp Tools, my phone restart, its time for me to get rid of the Costumer error. Contact Resseller if u can provide me the link i will be very greatfull thanks for everything:good::good::good:
Im rooted using this method http://forum.xda-developers.com/showthread.php?t=2298408 then install BMM Everything went ok only the Costumer error. Contact Resseller but im ok like this thank you so much
xt910 bricked and cant find firmware
Hi,
I also have xt910 razr maxx and i bricked it after installing some kind of custom rom app.
I want to flash stock firmware but all the links on internet are broken. I guess I need this one:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml.zip
Can aybody help me with a working link of this file pls, its kinda urgent.
Thanks.
VasyaAgPro said:
No one has any ideas?
that's interesting: tried to remove CID and failed, because: (see picture)
Code:
Erasing CID ... INFOCommand Restricted
Wrong command?
And:
Code:
CID:5
XT910S ?
Why can not we delete CID?
Click to expand...
Click to collapse
frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
alisonpoulose said:
frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
Click to expand...
Click to collapse
You need to make this command :
fastboot flash ramdisk "patched_ramdisk.img"
Until yours [emoji846]
failed to install twrp
fastboot flash ramdisk "patched_ramdisk.img"
where did i get this file? did i need to rename the twrp.img to patched_ramdisk.img.
failed to install twrp
i renamed twrp.img to patched_ramdisk.img then thake cmd and typed like this;;;
c:/adb>fastboot flash ramdisk patched_ramdisk.img
error: cannot load 'patched_ramdisk.img
what will i do now plz help me to find a solution:::::
failed to install twrp
now i tried it again now it shows likes this
c/adb>fastboot flash ramdisk patched_ramdisk.img
target reported max downlod size of 471859200 bytes
sending 'ramdisk (31572 KB)...
OKAY [ 1.084s]
writing 'ramdisk'....
FAILED (remote: partition error)
finished. total time: 1.095s
here the failed message changed
in previous it is (remote: patition length error)
but now it changed to remote: partition error
bro plz help me to find a solution
i hope u can clarify it
thankyou
fastboot flash ramdisk "patched_ramdisk.img"
thanku brooooo it workssssss thanks alot
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
my twrp is red in colour others are blue
bro is there is any problem with my twrp
can i change it to blue colour
plz help me
Phone: Oneplus 3T
Recovery: TWRP 3.3.0-1
OS: LOS 16.0
Flashed a bad emmc_appsboot.mbn and now my phone loops as soon as it gets to the 1+ logo.
Cannot get into recovery.
Can get into fastboot.
Bootloader has been unlocked for years. After getting the "not allowed" error, I did a "fastboot oem unlock" again, successfully.
Code:
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
$ fastboot flashing unlock
(bootloader) Device already : unlocked!
$ fastboot flashing unlock_critical
(bootloader) Device already : unlocked!
$ fastboot flash recovery twrp-3.3.0-1-oneplus3.img
target reported max download size of 440401920 bytes
erasing 'recovery'...
OKAY [ 0.010s]
sending 'recovery' (27405 KB)...
OKAY [ 0.721s]
writing 'recovery'...
OKAY [ 0.199s]
finished. total time: 0.930s
$ fastboot flash aboot firmware-update/emmc_appsboot.mbn
target reported max download size of 440401920 bytes
sending 'aboot' (1584 KB)...
OKAY [ 0.062s]
writing 'aboot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.082s
$ fastboot flash devcfg firmware-update/devcfg.mbn
target reported max download size of 440401920 bytes
sending 'devcfg' (50 KB)...
OKAY [ 0.038s]
writing 'devcfg'...
FAILED (remote: Partition flashing is not allowed)
Every partition other than recovery gives the "not allowed" error. And flashing the recovery doesn't help.
I'm stumped. I haven't been able to find any other reports online of the same problem, only people with locked bootloaders getting that error.
I know about EDL and I've been working on that angle, but getting fastboot flashing working would be easier.
Ideas? Suggestions?
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
Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly