Does anyone have the oeminfo for C675?
Please help if you have one. I don't see it in the full-OTA zip as well...
Thanks!
balamu96m said:
I don't see it in the full-OTA zip as well...
Click to expand...
Click to collapse
oeminfo cannot be obtained from the firmware, only from the phone (e.g. TWRP backup).
-Alf- said:
oeminfo cannot be obtained from the firmware, only from the phone (e.g. TWRP backup).
Click to expand...
Click to collapse
Cool! If anyone has a TWRP backup for C675 oeminfo that will be great!
balamu96m said:
Cool! If anyone has a TWRP backup for C675 oeminfo that will be great!
Click to expand...
Click to collapse
Btw, a few years ago, it was possible to use the Oeminfo-tools+0.13.exe application by @k1ll3r8e to read and edit oeminfo (only 64 MB version). But I don't know if it still works. Try asking the author.
Exactly! I found this 2021 updated version and I'm trying it...will update on the progress.
GitHub - EtoTen/oeminfo-huawei: Unpack and repack Huawei oeminfo
Unpack and repack Huawei oeminfo. Contribute to EtoTen/oeminfo-huawei development by creating an account on GitHub.
github.com
I was able to edit the 'region' to 'hw/in' and 'all/in' and tried flashing the modified oeminfo.....in both the cases dload method to flash stock firmware doesn't work...any idea how to flash the stock ROM for C675 in this case?
balamu96m said:
I was able to edit the 'region' to 'hw/in' and 'all/in' and tried flashing the modified oeminfo.....in both the cases dload method to flash stock firmware doesn't work...any idea how to flash the stock ROM for C675 in this case?
Click to expand...
Click to collapse
And what says fastboot?
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
balamu96m said:
tried flashing the modified oeminfo.
Click to expand...
Click to collapse
Successfully? If so, your bootloader locks again.
-Alf- said:
And what says fastboot?
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
Successfully? If so, your bootloader locks again.
Click to expand...
Click to collapse
Yes, it was successful and it relocks.....I unlocked it again after every trial...
I changed only the vendor country....let me try changing build number as well...
Code:
Fastboot> fastboot oem get-build-number
...
(bootloader) :ANE-AL00 8.0.0.111(C00)
OKAY [ -0.000s]
finished. total time: -0.000s
PS D:\Android\Minimal ADB and Fastboot> fastboot oem get-product-model
...
(bootloader) ANE-AL00
OKAY [ 0.000s]
finished. total time: 0.000s
Fastboot> fastboot getvar vendorcountry
vendorcountry: all/in
finished. total time: -0.000s
Fastboot> fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.016s
Fastboot> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-AL00 8.0.0.113(C00)
OKAY [ 0.016s]
finished. total time: 0.016s
PS D:\Android\Minimal ADB and Fastboot>
This is the stock rom I'm trying to flash - Huawei P20 Lite ANE-AL00 ANE-AL00I hw in HLRCF Anne-AL00I 9.1.0.112(C675E5R1P3T8) Firmware 9.0.0 r3 EMUI9.0.1 05015CDW
Looks like I need to change build number to something like: 9.1.0.112(C675E5R1P3T8) to make it work....is that correct?
balamu96m said:
This is the stock rom I'm trying to flash - Huawei P20 Lite ANE-AL00 ANE-AL00I hw in HLRCF Anne-AL00I 9.1.0.112(C675E5R1P3T8) Firmware 9.0.0 r3 EMUI9.0.1 05015CDW
Looks like I need to change build number to something like: 9.1.0.112(C675E5R1P3T8) to make it work....is that correct?
Click to expand...
Click to collapse
in my opinion you need to overwrite oeminfo correctly, build number will be corrected automatically. And don't forget that you currently have an Oreo there...
Related
I tried to restore and reinstall ROM in numerous ways, including adb, fastboot and sdcard. I even tried Funky Huawei.
Currently I can get to eRecovery and to TWRP. Fastboot works without problem. But that's about it, boot sometimes goes to Lineage boot splash, which I used prior the Magisk update.
Thanks for help in advance
Here is info from fastboot:
fastboot oem get-product-model:
<bootloader> CMR-AL09
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem get-build-number:
(bootloader) :CMR-AL09 8.0.0.122(C432)
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-system_version
FAILED (remote: The reason of failed input oem_nv_item error!)
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
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
Click to expand...
Click to collapse
fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
Click to expand...
Click to collapse
brazoayeye said:
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
Click to expand...
Click to collapse
Look here:
https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
https://forum.xda-developers.com/t/huawei-p20-lite-bricked.4331729/
https://forum.xda-developers.com/t/p20-lite-bootloop.4230037/post-84447333
brazoayeye said:
I downloaded the USB driver from here
Click to expand...
Click to collapse
install Hisuite on a computer and try again with Minimal ADB.
From https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.144s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.148s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.145s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem battery_present_check
...
(bootloader) 3326mv
OKAY [ 0.015s]
finished. total time: 0.019s
Click to expand...
Click to collapse
I cannot enter in the recovery
Is there a way to extract data from the phone before trying with erase user data?
Thanks
brazoayeye said:
Is there a way to extract data from the phone before trying with erase user data?
Click to expand...
Click to collapse
Nope bro.
I cannot even erase userdata
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
What should I do to try to unbrick it?
brazoayeye said:
I cannot even erase userdata
What should I do to try to unbrick it?
Click to expand...
Click to collapse
I gave you a link, you didn't read, did you?
IMO it's hardware problem, so board FW won't help you...
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i_plevra said:
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Click to expand...
Click to collapse
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
alonsoj636 said:
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
Click to expand...
Click to collapse
This smartphone is a Japan-only model for a company called au, but probably a global version is available. The size is a little different but the base is redmi note 10 5g I just checked and it seems to be 5g I'm not confident I'll use miflash. It's a hassle to borrow a phone from a family member, stick a sim in it and have to receive an authentication SMS.
pihpih95 said:
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
Click to expand...
Click to collapse
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
now I can't use Windows for some reasons so am using m1 mac, this pc can't use the miflash so am trying GSI boot in a while
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
big problem...
your device is locked which means that flashing anything (vbmeta , recovery) or use MiFlash Tool will not be possible because unlocked bootloader is compulsory
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
do you still have mi recovery, or only have fastboot?
LR7875 said:
do you still have mi recovery, or only have fastboot?
Click to expand...
Click to collapse
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
i_plevra said:
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
Click to expand...
Click to collapse
and does fastboot oem unlock or fastboot oem unlock_critical work
LR7875 said:
and does fastboot oem unlock or fastboot oem unlock_critical work
Click to expand...
Click to collapse
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
have u apply to unlock bootloader through official method ?
i_plevra said:
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...oken-verify-failed-reboot-the-device.4300755/ this is for redmi note 10 pro but is worth to read. maybe it can help
Hello,
I have bought Huawei P20 Lite, but it is demo mode unite, is there chance unistall demo mode? Because, my older P20 Lite died, bude I want to use still use it, bude seller did not tell that is demo unit.
Pls help
Thank you
erik.aragorn said:
Hello,
I have bought Huawei P20 Lite, but it is demo mode unite, is there chance unistall demo mode? Because, my older P20 Lite died, bude I want to use still use it, bude seller did not tell that is demo unit.
Pls help
Thank you
Click to expand...
Click to collapse
how did your old p20 lite die? if it is the screen only you can swap motherboards
MB is dead, I need swap MB, but this MB is on Demo Mode, and hard reset is not possible too.
erik.aragorn said:
Hello,
I have bought Huawei P20 Lite, but it is demo mode unite, is there chance unistall demo mode? Because, my older P20 Lite died, bude I want to use still use it, bude seller did not tell that is demo unit.
Pls help
Thank you
Click to expand...
Click to collapse
I am dying to know how you obtained a device stuck in demo mode. Please elaborate!
erik.aragorn said:
Hello,
I have bought Huawei P20 Lite, but it is demo mode unite, is there chance unistall demo mode? Because, my older P20 Lite died, bude I want to use still use it, bude seller did not tell that is demo unit.
Pls help
Thank you
Click to expand...
Click to collapse
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.
Some might fail, so don't worry about it.
Timmmmaaahh!I found phone with broken display, good price for MB - 40€, seller send me it, and wualla. When I see this, only facepalm....
-Alf- said:
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.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
Thank you I will try it today, or tomorrow
erik.aragorn said:
Timmmmaaahh!I found phone with broken display, good price for MB - 40€, seller send me it, and wualla. When I see this, only facepalm....
Click to expand...
Click to collapse
Why would a private seller purposely activate demo mode? That makes no sense.
Well the seller probably have picked up this from the trashbin outside a mobile phone store, seen it has demo mode, and gone on ebay to enjoy scamming people.
-Alf- said:
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.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 9.1.0.397(C432E7R1P7)
OKAY [ 0.015s]
finished. total time: 0.016s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.014s]
finished. total time: 0.015s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.013s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-CUSTOM_VERSION
...
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
OKAY [ 0.015s]
finished. total time: 0.016s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
OKAY [ 0.016s]
finished. total time: 0.017s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s