Hello. When I woke up this morning, I picked up the phone, I got to Instagram, and after 3 minutes the phone vibrated and reset. And then he entered the loop and started to reset constantly, he sees the text huawei, after a while it vibrates and is reset. Although I have 2-year files in it, I still said I should save the phone and agreed to the factory reset. But I entered and saw that the factory reset part is gray out inactive. It doesn't react when I click it. I entered the download latest version and recovery section and made the wifi settings. somehow it becomes a perpetrator when it comes to certain percentages. Then, after turning the phone on and off, it fails to load this time when it is 100% somehow. As you can understand, I could neither download and install or reset the factory. I would be very happy if anyone who knows I need help or has lived before and conveys their experiences ..
error: "getting package info failed"
The phone is like the first day. No changes were made. not made root
hardware has not changed recently. it took no blow
phone information:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
(bootloader) :ANE-LX1 9.1.0.374(C432E7R1P7)
OKAY [ 0.012s]
finished. total time: 0.012s
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
Thank you
onur3372 said:
the factory reset part is gray out inactive
Click to expand...
Click to collapse
Hello, eMMc memory might be dead...
Just to be sure - turn off your phone, press and hold for at least 10 seconds both Volume buttons + Power, and post the result.
-Alf- said:
Hello, eMMc memory might be dead...
Just to be sure - turn off your phone, press and hold for at least 10 seconds both Volume buttons + Power, and post the result.
Click to expand...
Click to collapse
thanks for the answer. Hold down the volume up, volume down + power keys: waiting for a while. trying to confirm the data and the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery Menu:
onur3372 said:
thanks for the answer. Hold down the volume up, volume down + power keys: waiting for a while. trying to confirm the data and the result:
View attachment 5274635
Recovery Menu:
View attachment 5274639
Click to expand...
Click to collapse
Okay, try this way out:
- Download Service ROM
- Unpack .zip package , transfer dload folder (can be found in "Software) without unpacking it (!) to the SD card
- Turn off the phone and
onur3372 said:
Hold down the volume up, volume down + power keys
Click to expand...
Click to collapse
-Alf- said:
Okay, try this way out:
- Download Service ROM
- Unpack .zip package , transfer dload folder (can be found in "Software) without unpacking it (!) to the SD card
- Turn off the phone and
Click to expand...
Click to collapse
I'm sorry I couldn't understand some of them. Should I assign the software file to the dload folder in the sd card? Or should I put the dload folder in the software into the sd card?
onur3372 said:
put the dload folder into the sd card
Click to expand...
Click to collapse
Instructions can be found in ReleaseDoc folder
-Alf- said:
Instructions can be found in ReleaseDoc folder
Click to expand...
Click to collapse
Unfortunately it didn't happen. same error again. Should I understand that the emmc is broken?
onur3372 said:
Should I understand that the emmc is broken?
Click to expand...
Click to collapse
it's just my opinion, but I'm not an expert, just a android/huawei fan...
-Alf- said:
it's just my opinion, but I'm not an expert, just a android/huawei fan...
Click to expand...
Click to collapse
but you gave information like an expert. so thank you.I hope there are some other ideas and I hope they can help.
Related
i convert mx player to system app using luckeypatcher then it hangs i press the power button to restart the phone and its not booting still on huawei mediapad screen,,i tried recovery buttons still not work and also sd card upgrade firmware not working also..please help me.
up
download this firmware it's the stock one : from here
- Copy the extracted “dload” folder (containing Update.app file) to the main directory of your external SD Card.
- Next, turn off your device and insert the SD card.
- Reboot into forced SD upgrade mode by holding Vol Up + Vol Down + Power buttons at the same time until you see some text on the screen.
- It’ll take a few minutes to complete the update. After that, it will automatically shut down and reboot into the new OS.
Does not work for me
Tried diffrent SD cards and formattings and diffrent ways of holding the buttons, the problem occurred after a downgrade to stock rom from a rooted and bootloader unlocked rom.
i have same problem, please ant help?
i have same problem, please any help? i am unable to boot the tab , it only vibrates and still shows blackscreen.
bigal1337 said:
Does not work for me
Tried diffrent SD cards and formattings and diffrent ways of holding the buttons, the problem occurred after a downgrade to stock rom from a rooted and bootloader unlocked rom.
Click to expand...
Click to collapse
You cant
The reason why its because youve been very badly damaged the motherboard.... It happened to me before and the only you can do is to buy another one or if you have dat warranty of yours if its not Damn month.... Then you can tell that youve been installed to much stuffs into your internal storage...... I felt sorry for myself when it was happened to me..... Because it was stuck to that crappy logo.... I tried to drain it but sadly when i turn it on again.... It repeats the same method facking crap!!!!? Again the only you can do right now is to buy or to give to the manufacturer to where you buy it particularly with the warranty in you hand... Hope you have it with the box of it..... Sorru for your loss..?
Techpromaster said:
The reason why its because youve been very badly damaged the motherboard.... It happened to me before and the only you can do is to buy another one or if you have dat warranty of yours if its not Damn month.... Then you can tell that youve been installed to much stuffs into your internal storage...... I felt sorry for myself when it was happened to me..... Because it was stuck to that crappy logo.... I tried to drain it but sadly when i turn it on again.... It repeats the same method facking crap!!!!? Again the only you can do right now is to buy or to give to the manufacturer to where you buy it particularly with the warranty in you hand... Hope you have it with the box of it..... Sorru for your loss..
Click to expand...
Click to collapse
i got it to work again by saving the Dload folder in the memory card, then i held down volume up, volume down and power button all together
manyaro said:
i convert mx player to system app using luckeypatcher then it hangs i press the power button to restart the phone and its not booting still on huawei mediapad screen,,i tried recovery buttons still not work and also sd card upgrade firmware not working also..please help me.
Click to expand...
Click to collapse
how to do
Completely Stack
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to get root my New T1, But seems deadly trouble.
Is there any way?
I want to replace the hard disk,
how to fix my huawei t1-a21w
please help me
C:\Users\PC1\Downloads\Android Multi Tools v1.02b gsmforum>fastboot flash cust "C:\Users\PC1\Downloads\Android Multi Tools v1.02b gsmforum\CUST.img"
target reported max download size of 266338304 bytes
sending sparse 'cust' (259909 KB)...
OKAY [ 9.498s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 9.509s
C:\Users\PC1\Downloads\Android Multi Tools v1.02b gsmforum>fastboot flash recovery "C:\Users\PC1\Downloads\Android Multi Tools v1.02b gsmforum\RECOVERY.img"
target reported max download size of 266338304 bytes
sending 'recovery' (12984 KB)...
OKAY [ 0.425s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.432s
C:\Users\PC1\Downloads\Android Multi Tools v1.02b gsmforum>
please help me.. stuck on fastboot mode . i cant flash recovery
hi,
i have my lg d620r stuck in fastboot mode, i found some guides that reflash via fastboot a dump of all the partitions(imei excluded, obv), and i'm here if someone knows where I could find them, or if someone would be so nice to provide me these files
link to the guide(in italian):https://www.tuttoandroid.net/forum/threads/fix-brick-no-recovery-mode-no-download-mode.37272
https://forum.xda-developers.com/g2-mini/development/bootstack-kk-l-unknown-baseband-imei-t3142805
How did you get stuck in fastboot mode?
DrAcula04 said:
How did you get stuck in fastboot mode?
Click to expand...
Click to collapse
it did it by itself, very strange situation
Vagelis1608 said:
https://forum.xda-developers.com/g2-mini/development/bootstack-kk-l-unknown-baseband-imei-t3142805
Click to expand...
Click to collapse
this does work with a modified aboot and a modified recovery
i'm on stock aboot and with no recovery, that's why i need the dumps
mg95tux said:
this does work with a modified aboot and a modified recovery
i'm on stock aboot and with no recovery, that's why i need the dumps
Click to expand...
Click to collapse
I thought you would figure out that you can extract the contents and flash them via fastboot.
If I was you, I would find the laf partition to get download mode working and flash a kdz.
Vagelis1608 said:
I thought you would figure out that you can extract the contents and flash them via fastboot.
If I was you, I would find the laf partition to get download mode working and flash a kdz.
Click to expand...
Click to collapse
i noticed that the guide I found uses .img files, while files in the link you sent me uses .bin
i can use them anyway or i risk a full brick?
mg95tux said:
i noticed that the guide I found uses .img files, while files in the link you sent me uses .bin
i can use them anyway or i risk a full brick?
Click to expand...
Click to collapse
Just find the laf partition to fix download mode and flash a kdz.
Partition backups (usually taken with dd) are the same no natter the extension (img, bin, or even no extension).
Vagelis1608 said:
Just find the laf partition to fix download mode and flash a kdz.
Partition backups (usually taken with dd) are the same no natter the extension (img, bin, or even no extension).
Click to expand...
Click to collapse
tried with these, but fastboot seems useless, it says
Code:
sudo fastboot erase laf
erasing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.002s
and
Code:
sudo fastboot flash laf laf.bin
target reported max download size of 536870912 bytes
sending 'laf' (16896 KB)...
OKAY [ 0.678s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.680s
do you have some suggestion for me how to flash these?
Are you sure you cant get in download mode?
Pull out the battery for a few seconds, put it back in, hold the Vol+ , then insert a USB cable to your PC and the other end to your phone (while holding Vol+)
Make sure that the USB is capable of data transfer, not just charging.
Vagelis1608 said:
Are you sure you cant get in download mode?
Pull out the battery for a few seconds, put it back in, hold the Vol+ , then insert a USB cable to your PC and the other end to your phone (while holding Vol+)
Make sure that the USB is capable of data transfer, not just charging.
Click to expand...
Click to collapse
this is the result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mg95tux said:
this is the result
Click to expand...
Click to collapse
Try to follow this, but instead of flashing the partitions it says, flash the laf partition.
https://forum.xda-developers.com/showthread.php?t=2582142
Vagelis1608 said:
Try to follow this, but instead of flashing the partitions it says, flash the laf partition.
https://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
doesn't work, i'll try to find a qhsbulk how-to short the processor, and this will be the last chance
mg95tux said:
doesn't work, i'll try to find a qhsbulk how-to short the processor, and this will be the last chance
Click to expand...
Click to collapse
Good luck
Vagelis1608 said:
Good luck
Click to expand...
Click to collapse
In the end, It was the Memory
It's completely gone, so rip g2mini
Thanks for your help!
mg95tux said:
In the end, It was the Memory
It's completely gone, so rip g2mini
Thanks for your help!
Click to expand...
Click to collapse
Do you mean that the NAND chip was wiped?
It can't be, because if it was then the device wouldn't turn on at all.
Vagelis1608 said:
Do you mean that the NAND chip was wiped?
It can't be, because if it was then the device wouldn't turn on at all.
Click to expand...
Click to collapse
If nand chip is wiped/destroyed, the phone will boot a stub fastboot from the chipset, like a "last resource"
And i'm sure nand is gone, since when i put the phone in qhs loader and i checked the nand, It said " dimension 2TB".... Which is the max value that a nand chip could ever have... And It is for sure really too big for this phone
mg95tux said:
If nand chip is wiped/destroyed, the phone will boot a stub fastboot from the chipset, like a "last resource"
And i'm sure nand is gone, since when i put the phone in qhs loader and i checked the nand, It said " dimension 2TB".... Which is the max value that a nand chip could ever have... And It is for sure really too big for this phone
Click to expand...
Click to collapse
If it was destroyed, then it wouldn't start at all.
There are probably more reasons to it, but the first one I can think of is that the aboot partition (secondary bootloader) would be gone and it would only show an empty battery warning, if anything.
When this broken fastboot 'mode' shows up, it means that the dtb of the partition you are trying to boot is faulty, possibly along with the rest of the partition.
dtb holds the device drivers, I believe.
So, the NAND chip is probably good.
Hey,
I have unlocked the bootloader in Honor 7C (LND-L29). (dcunlocker)
I was looking on the internet and I can not find anywhere.
twrp does not work on this phone. It can not be installed by the command flash recovery twrp.img
How do you install root? Kingroot does not work
remkac96 said:
Hey,
I have unlocked the bootloader in Honor 7C (LND-L29). (dcunlocker)
I was looking on the internet and I can not find anywhere.
twrp does not work on this phone. It can not be installed by the command flash recovery twrp.img
How do you install root? Kingroot does not work
Click to expand...
Click to collapse
Sup,
Before proceeding, enable "manufacturer mode" on your phone. This is done by entering in dial pad code *#*#2846579#*#* select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode". Then connect it to PC and Hisuite for drivers.
flash TWRP made by Augustoandro, flash Supersu
Greetz
Leak1337 said:
Sup,
Before proceeding, enable "manufacturer mode" on your phone. This is done by entering in dial pad code *#*#2846579#*#* select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode". Then connect it to PC and Hisuite for drivers.
flash TWRP made by Augustoandro, flash Supersu
Greetz
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastboot flash recovery TWRP_Honor7C_LND-L29.img
target reported max download size of 534773760 bytes
sending 'recovery' (4896 KB)...
OKAY [ 0.144s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.183s
remkac96 said:
fastboot flash recovery TWRP_Honor7C_LND-L29.img
target reported max download size of 534773760 bytes
sending 'recovery' (4896 KB)...
OKAY [ 0.144s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.183s
Click to expand...
Click to collapse
Ok, have you tried the multitool? MultiTool Honor 7
Step by step Tutorial look if you have done everything and try it with the tool. Tutorial
Leak1337 said:
Ok, have you tried the multitool? MultiTool Honor 7
Step by step Tutorial look if you have done everything and try it with the tool. Tutorial
Click to expand...
Click to collapse
We managed to install, but internal memory in twrp does not work.
After several attempts to repair twrp. The system does not turn on in the phone. He is now trying to install the rom from the new version using Huawei eRecovery
I also tried to upload the twrp from this topic: https://4pda.ru/forum/index.php?s=&showtopic=909546&view=findpost&p=78962423
After uploading by multitool, it does not even turn on twrp.
If someone has uploaded root on this phone, let them write in what way. I've tried many options and still nothing of it.
Sorry my bad english.
remkac96 said:
I also tried to upload the twrp from this topic: https://4pda.ru/forum/index.php?s=&showtopic=909546&view=findpost&p=78962423
After uploading by multitool, it does not even turn on twrp.
If someone has uploaded root on this phone, let them write in what way. I've tried many options and still nothing of it.
Sorry my bad english.
Click to expand...
Click to collapse
All twrp installed by me does not load internal memory.
Can uh tell me how you unlocked the bootloader?
Hey man, its great to hear this first of all that you successfully unlocked the bootloader,
Please tell how you unlocked it.
Thanks in advance for you help.
Hi everyone! I'll explain my problem with this phone, sorry for any error because i'm italian and a complete android noob!
My girlfriend gave me her P20 lite which looks like it's bricked. She said that the phone was charging and she was speaking on the phone and suddenly the phone shut down.
Trying to reboot the phone was useless: it showed the huawei logo and then it just rebooted again. The phone only did this while under charge. If I unplug the usb cable it just tried to boot up, showed the huawei logo, shut down and then a green screen with red and blue boxes showed up for 1 second.
I tried to boot the phone with Volume up + power to enter recovery and this screen showed up: https://imgbb.com/zQ76Ywx
I tried to do option 1 and 2 but in both cases the phone just rebooted with the huawei logo and continued to reboot.
Booting the phone while pressing Volume down + power brought me in fastboot mode: https://imgbb.com/dmHQxB0
I understood that PHONE Locked and FPR Lock means that the bootloader is locked. I assume this is normale because my girllfriend is not into modding. The phone was 100% stock.
In fastboot mode i was unable to do anything. So I rebooted, unplugged the cable and just like before the green screen came up: https://ibb.co/sFWmgZv
Next step was connecting the phone to HiSuite: nothing to do, the phone was not recognised.
I tried to download a modified HiSuiteConfig.xml with support for P20 Lite, put the phone into fastboot and perform a system reset: nothing to do, it said that the phone was not supported. After trying this, The phone changed behaviour. It doesn't show anymore the huawei logo while booting, I can only see a black screen with a red led flashing followed by the green screen with red and blue boxes and continues with this loop. I am not able anymore to boot with volume up + power but only in fastboot mode.
Last thing I tried was the testpoint mode:
I downloaded this IDT Tool with firmware: https://mega.nz/file/jEoWRSAZ#sltXiQMt3kNNIEbq30WYuJTme0AoZMKRpbEtMu3-Mx4
I downloaded this driver for testpoint mode: https://androidfilehost.com/?fid=17248734326145712518
I recoreded a small video to show all the step i did:
Please note this: at the beginning the phone is connected in fastboot mode and is recognised by windows as "Android Composite ADB Interface"
Then, I reboot the phone and shortcircuiting the testpoint: the phone is recognised as "HUAWEI USB COM 1.0(COM5)"
When I start the procedure with IDT Tool after the first completed the step the phone disconnect and reconnect itself and is once again recognised as "Android Composite ADB Interface". Is it the correct behaviour?
However, the procedure fails and I couldn't find anything about error 39 of IDT Tool.
Sorry for the long message, but I wanted to explain carefully what happened.
Do you have any suggestion?
EXTRA INFO: I installed fastboot on my pc with this tool: https://forum.xda-developers.com/t/...s-adb-installer-v1-4-3.2588979/#post-48915118
I run the following commands:
fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot oem get-build-number
...
(bootloader) :ANE-LX1 9.1.0.381(C432E7R1P7)
OKAY [ -0.000s]
finished. total time: -0.000s
pspmaster said:
green screen with red and blue boxes
Click to expand...
Click to collapse
pspmaster said:
black screen with a red led flashing
Click to expand...
Click to collapse
Probably HW issue (emmc memory dead, out of order, or in r /o mode).
If in the process of installing the board firmware you get an error like on the screen, this confirms a memory error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was watching the video I posted above at 0.25x speed and yes, just before failing with error 39 e can see this message. So it is an hardware issue memory related and is not fixable. The only solution would be to change the entire motherboard correct?
pspmaster said:
The only solution would be to change the entire motherboard correct?
Click to expand...
Click to collapse
I'm not sure bro, I don't work in a service center, it's just my hobby... Complete motherboard replacement is too expensive if you don't have a phone warranty. But it is possible to replace only the emmc memory, ask the service center, or google it. Good luck!
of course mate, thank you for your support!
I think I will pass, changing the whole board is too expensive and changing the memory chip is far beyond my capabilities. The official service center would be too expensive considering the value of the phone.
Hello!
My goal is to install the last official build of Lineage OS for ANE-LX3 which is version 16 (android 9) that I downloaded from: https://archive.org/details/lineageos20210217 (specifically https://archive.org/download/lineag...lineage-16.0-20210215-nightly-anne-signed.zip)
I did the testpoint method to unlock my bootloader and was trying to follow the Lineage OS guide from here: https://wiki.lineageos.org/devices/anne/install using latest TWRP (3.7.0).
There are issue with the guide, such as mentioning that Volume Down + Power is used to enter fastboot but it's actually Volume Up + Power (as mentioned everywhere in this forum lol) and also to use fastboot flash recovery <recovery_filename>.img but actually one must use fastboot flash recovery_ramdisk <recovery_filename>.img. Also, when I tried to follow the Format Data step, it would always hang after displaying 'done.'. Despite that issue I carried on and it successfully sideloaded the LineageOS zip as per the guide but after rebooting it would not boot into it, it would just hang on the black and orange text screen with 'Your device is booting now...'.
I started deleting more things to try to make it work and I think I deleted too much, because after doing a Advanced Wipe on everything, I started having the TWRP bootloop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding Power button to try to turn the unit off only cycles it and boots into TWRP logo screen.
Holding Volumn Up + Power no longer goes into eRecovery, instead it leads to the TWRP logo screen.
TWRP logo screen remains frozen, it does not show the slider nor does any tap or buttons work.
At the TWRP logo, I can see my device with adb as in recovery mode.
Fastboot has no apparent issues, so I tried rewriting TWRP to recovery_ramdisk a bunch of times, which succeeds, but it keeps freezing at the TWRP logo.
Did some searching and found this post which sounded like a similar situation https://forum.xda-developers.com/t/from-locked-bootloader-to-lineage-os-19-0-on-ane-lx3.4414089/ so I tried to follow this guide: https://www.getdroidtips.com/huawei-p20-lite-ane-lx3-firmware/ downloading the android 8 images from there, placing the DLOAD contents (tried both zipped and unzipped) onto an SD card (for example /dload/UPDATE.APP, etc.), however holding Volume Up + Volume Down + Power doesn't appear to do anything, let alone load anything from DLOAD folder.
Have not tried disconnecting the battery yet, more comfortable with a software solution but if that's what it comes down to I can try that.
Any help would be appreciated!
Thank you
Ironsmith9 said:
TWRP (3.7.0).
Click to expand...
Click to collapse
Ironsmith9 said:
Format Data
Click to expand...
Click to collapse
this is a deadly combination on stock EMUI 9 .
It's impossible to install Oreo dload ROM running EMUI 9. The problem is that dload method reguire stock Recovery on EMUI9.
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Btw, what is you region? (Cxxx).
-Alf- said:
this is a deadly combination on stock EMUI 9 .
Click to expand...
Click to collapse
oh man what have i done
-Alf- said:
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Click to expand...
Click to collapse
this worked!!! thank you!
-Alf- said:
Btw, what is you region? (Cxxx).
Click to expand...
Click to collapse
i'm not sure actually, how do i check this?
Ironsmith9 said:
how do i check this
Click to expand...
Click to collapse
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Ironsmith9 said:
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Click to expand...
Click to collapse
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
-Alf- said:
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
Click to expand...
Click to collapse
Woohoo! LineageOS is installed and booting now!
I wasn't really interested in the dload method. I was just trying to use that to reset everything to some good old state so I can go back into TWRP and try to get LineageOS installed.
What I ended up doing was switching my data partition from f2fs to exFAT which seemed to do the trick for some reason?! It was just a wild guess on my part and I wonder if it'll cause issues in the future (I'll create a new thread if it does). But so far so good!
O.K., midnight here
Ironsmith9 said:
exFAT
Click to expand...
Click to collapse
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
-Alf- said:
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
Click to expand...
Click to collapse
Understood, ok I'll try that out! Thanks Alf!