Related
Hi!
I have unlocked bootloader, then rooted and added twrp recovery, successfully without issues.
then i tried flashing viper4android for oreo, and now it wont boot.
ive tried the viper4android uninnstaler provided in the same thred and still dosent boot.
i tried installing another dolby atmos with viper and a uninstaller, dont work either.
should factory reset fix it? it dosent in that case..
any ideas?
https://forum.xda-developers.com/android/software/sound-mod-viper4android-oreo-t3734107
and it seems i cant take backup of the system to internal storage due to twrp bug,
ive tried backinguppon a 16gb usb3.0 device thru otg adapter with fat32 it stops at 3999 and backupp fails.
i tried otg to usb with 16gb microsdcard, also stopped at 3999 and failed.
i tried usb with ntfs but the it wont backupp at all.
what can i wipe?
installing stock a solution? how? flash update.app?(in zip).
custom rom?
is there any reason to lock the bootloader again?
Maximum file size of FAT32 is only 4GB per file. Use Huawei update extractor to get img files from update.app file. Flash those to your phone using fastboot. You can relock bootloader once you are in stock EMUI. Just run fastboot oem relock *your unlock code*.
EngrVan said:
Maximum file size of FAT32 is only 4GB per file. Use Huawei update extractor to get img files from update.app file. Flash those to your phone using fastboot. You can relock bootloader once you are in stock EMUI. Just run fastboot oem relock *your unlock code*.
Click to expand...
Click to collapse
ok thx^^ what files from the update.app? dont find any boot.img.
and recovery or recovery ramdisk.. dont really know what to write in that case
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
EngrVan said:
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
Click to expand...
Click to collapse
ok thx will try ^^
EngrVan said:
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
Click to expand...
Click to collapse
flashed both, but still the same, bootloop..
flash other files??
Fixed after many hours trying to flash stock
using this!
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
614Emil said:
Fixed after many hours trying to flash stock
using this!
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
what did you use and how to start... to fix it... please share the steps...
Hi there
I think my phone is briked. I wantet to downgrade my phone to the 108 version becaus there was android auto working.
So i tried to flash the System.img from the 108 Software. I tried 2 different:
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-lx1&firmware_page=0
and the Middle east from the thread here.
Id did flash over fastboot, but after every start the Build number was still on the 112 Firmware.
So i tried the Trebel ASOP, RR and LOS. ASOP Booted but had only forceclose on every service. RR and LOS did not work.
Then i tried to flash the ramdisk, recovery, vendor kernel etc from the update.app from the 108 Firmware. No my phone is briked.
I tried to flash eveyrthing from the .112 updateapp from the Official thread but nothing happend.
Then i tried to flash every possible .img file from the .112 app but most of them gave "Error Command not allowed"
So here i Am. Bootlooping phone and i dont know what else to do.
Since the beginning i could flash every system.img but it still was on the 112 Build and suddenly it bricked. I cant get to the 112 Version back with flashing system.img because it bootloops. Same for Treble and the newest 126 Version or the old 108 Build.
The only thing booting is ASOP Treble but i cant navigate coz of the 1000 of forceclosed errors.
I formated the userpartition as i was asked from Huawei, and bevore i did those installations i did a fullwipe with EMUI.
The Recovery cant connect to the server, and yeah.. i dont know what to do next. ofc i have unlocked bootloader. I bought the Phone in Switzerland with Dual Sim. ANE-LX1.
Does anyone have another idea?
Cheers
EDIT:
After 10000 billions klicks i managed to get through the treble wizzard, even when the com.android.phone has stopped is comming every second.
At the Moment im in the About Phone Screen and i see this: (I am in the newest ASOP Treble SU with gapps)
Model: ANE-LX1
Android Version 8.1
Baseband: unknown
Kernel Version 4.4.23+ (gcc version 4.9x 20150123 (prerelease) (GCC))
Fri Mar 9 09:51:47 CST 2018
Build Number ANE-LX1 8.0.0.112(c432) <------- WTF ?!?
I hope this informations is something to work with.
SIM CARD is not readable.
Edit2:
I connected it to HI SUit. It says my device running properly on the .112 Version (WTF i got Treble installed)
I cant connect anything. How the hell can i get rid of this ****ing wong Build number??
Same for Checking Updates. .112 should be newest (its not its 126) Any ideas?
Edit3:
Can only Flash with fastboot. Twrp cant mount the partitions. Trying to installing the zip or adb sideload gives me an error code or command not allowed :\
i think the best way is
download a FULL-Update for your build
https://forum.xda-developers.com/9-lite/help/huawei-honor-firmware-download-t3790327
read this https://forum.xda-developers.com/hon...flash-t3778085
if you understand and have the know how : good luck
with this way i have my Ho9L reflash to stock-rom
you have to know what you're doing
use Magisk (search inside xda the thread)
this work by me better as SuperSU (with less problem's)
use this twrp, it's work WITH encryption
ttps://forum.xda-developers.com/huawei-p20-lite/development/recovery-testing-t3783587
if you understand what i am write - you can reset your phone to "delivered-state" and beginning by zero (initial-setting's) and
what ever you flash - you have a chance to reset your phone
first look on bootloader-screen if
- bootloader unlocked
- FRP unlock
THIS is essential !
last tip: let the fingers from custom-rom if this not expressly build for OREO
OREO is other as NOUGAT ! very different !
Relock your bootloader before trying an Erecovery...
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
haidermiz said:
I'm getting this error when I'm trying to extract UPdate.app of anE-LX1 8.0.0.108(C185)
https://ibb.co/k0HmGy
Click to expand...
Click to collapse
go to settings, untick all options that have "verify" in it, and try extract again.
heindrix said:
go to settings, untick all options that have "verify" in it, and try extract again.
Click to expand...
Click to collapse
thanks it worked
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
haidermiz said:
When i did fastboot flash vendor vendor.img it says
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460706 KB)...
OKAY [ 18.084s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
Tried then phone was stuck at installing update 5% after 5 mins there was a screen android written on it then again it booted to erecovery i factory reset data, wiped cache then again it rebooted and it's finally open now thanks
heindrix said:
Hi there, if you have TWRP, you could flash system and vendor using TWRP. boot into TWRP, choose install, choose use image file, and flash system.img to system, and vendor.img to vendor.
Click to expand...
Click to collapse
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
haidermiz said:
I did that a installed stock rom after that I tired to reset data it said failed, it failed at 20% then I WIPED CHAHE and now when It opened I sign in and downloaded snapchat but it's noy opening and in settings about phone there's no model number mentioned it says unknown I don't know what to do
Click to expand...
Click to collapse
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
heindrix said:
if you could, please provide screenshot so i can see it more clearly.
after you flashing the rom, one thing you must do is to format the data and cache through emui erecovery, as long as you're not format the data and cache successfully, the rom will not works properly.
for another reference, please refer to my other post here : https://forum.xda-developers.com/ma...0-pro-help-t3776050/post76916307#post76916307
Click to expand...
Click to collapse
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
ajbn7 said:
Greetings, I downloaded the rom of my Huawei p20 EML-L09 and it has two Update.app
How and in what order should I install them?
Udpate.app that weighs 4.62gb and
update_EML-L09_hw_la.app which weighs 1.5gb
Thanks a lot.
Click to expand...
Click to collapse
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
-Alf- said:
Hi,
this guide is two years old, if you want to recover your phone, download Service ROM from androidhost.ru website, and flash it using dload method .
Which EMUI version are you running? Your region is C605 ?
Click to expand...
Click to collapse
Correct, my region is 605. I already downloaded the latest version available for download on that page which is 8.1.
Before my phone went into brick, it had version 9.1
And bring those two update.app
ajbn7 said:
Before my phone went into brick, it had version 9.1
Click to expand...
Click to collapse
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
-Alf- said:
For 9.1 you can download
https://androidhost.ru/2bCG
Unpack .zip archive , find dload file and simply transfer it to the SD card, without unpacking it! (instructions can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo.
Note: Service ROM L-29 contains both version - L-29 & L-09 .
Click to expand...
Click to collapse
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Click to expand...
Click to collapse
Are you sure?
I'm really sorry, but most of the packages are universal.
ajbn7 said:
Are there any risks if I try to install version 8.1?
Click to expand...
Click to collapse
It may brick your phone definitively.
ajbn7 said:
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Yes, you can.
ajbn7 said:
I struggled so hard to download the file, and to my surprise it does not include the software version for the L-09, only for the L-29
Are there any risks if I try to install version 8.1?
Another thing, the Huawei p20 does not have a micro sd slot, I guess I should do it through a USB OTG?
Click to expand...
Click to collapse
Okay, I definitely don't get the 9.1 for Eml-09 for free.
So last query (I hope), what is less risky, install Rom 8.1 which is for my region and exact model, or install Rom 9.1 with my region but for model L-29 or install a Rom 9.1 for my model but with a different region?
Thank you for your support.
ajbn7 said:
what is less risky?
Click to expand...
Click to collapse
L29 EMUI 9.1 C605. Even if it succeeds the phone will not work correctly.
Most probably you will get the wrong model or in build number "system_0.46 (xxxx)" . HiSuite will not recognize your device (and no OTA update).
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
sentavn said:
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Click to expand...
Click to collapse
Any Ideas?
HOW I FIXED:
I downloaded this EMUI 5 Nougat, Thanks to bozka1:
https://androidhost.ru/5SZ
I extracted UPDATE.APP file using Huawei Update Extractor.
I was trying to flash everything via fastboot: BOOT.img, RECOVERY.img, RECOVERY2.img, CUST.img, SYSTEM.img but nothing helped me.
I found out what you can flash via fastboot here:
https://forum.xda-developers.com/general/general/huawei-fastboot-commands-t3850123
There was no hope for me, so I tried to flash USERDATA.img
fastboot flash userdata USERDATA.img
Click to expand...
Click to collapse
And then cmd promped something unusual:
target reported max download size of 471859200 bytes
sending 'userdata' (24576 KB)...
OKAY [ 0.646s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.401s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then I proceeded to flash: BOOT.img, RECOVERY.img, RECOVERY2.img and CACHE.img
I didn't flash SYSTEM.img because I flashed it before like 1500 times.
My phone didn't work yet so I used the DLOAD method because RECOVERY finally worked, so I shut down the device and used three buttons combo:
First holding Volume Up, Volume Down and then pressing Power Button.
There is a documentation in the firmware I downloaded, SDcard must be in exFAT format.
Thank You bozka1.
voltzero2 said:
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
Any Ideas?
Click to expand...
Click to collapse
What is your original location, C461?
Which oeminfo you have flashed?
bozka1 said:
What is your original location, C461?
Which oeminfo you have flashed?
Click to expand...
Click to collapse
My original location is C432, I don't remember flashing any oeminfo
voltzero2 said:
My original location is C432, I don't remember flashing any oeminfo
Click to expand...
Click to collapse
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
bozka1 said:
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
Click to expand...
Click to collapse
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
voltzero2 said:
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
Click to expand...
Click to collapse
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
bozka1 said:
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
Click to expand...
Click to collapse
It says its unlucked:
https://imgur.com/a/LEDKWFr
I hope this link works
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
So I'll have to wait a little before I'll download Service ROM, my internet connection isn't the greatest, but I flashed Your TWRP and unfortunately it doesn't work;
If I hold the Power button and Volume Up - the same story as before, I see the loading TWRP screen and nothing happends,
If I let the device to boot up and then press only the Volume Up button - it says "Your device is booting up" and nothing happens.
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
EDIT:
I did some testing and Your TWRP doesn't boot at all on my device, I flashed another one, Catuva21 3.1.1 Nougat, and that is the one that I had before - it is booting but never loads.
voltzero2 said:
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
Click to expand...
Click to collapse
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
bozka1 said:
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
Click to expand...
Click to collapse
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
voltzero2 said:
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
Click to expand...
Click to collapse
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
bozka1 said:
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
Click to expand...
Click to collapse
Yeah, I've done it already, unfortunately nothing changed. How about BOOT.img? Can this influence something?
EDIT:
I also wonder about just following the steps in my first post, I've got UPDATE.APP for Oreo, but I don't know if it will only make it worse.
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
Do I have to install oeminfo to be able to use the "three buttons combo"? Because I tried it today and it doesn't work, phone is just stuck at "Your device is booting.." screen, guess I'm out of luck
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
voltzero2 said:
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
Click to expand...
Click to collapse
You're welcome
Hi help me
Bozka1
My huawei mate 10 lite is brick stock on erecovery what can i do now
Lj08 said:
My huawei mate 10 lite is brick stock on erecovery what can i do now
Click to expand...
Click to collapse
Hi, have you tried to do something with your phone? Can you provide some info?
voltzero2 said:
Hi, have you tried to do something with your phone? Can you provide some info?
Click to expand...
Click to collapse
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Lj08 said:
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Click to expand...
Click to collapse
Alright, so did it just happened randomly or did you tried to do something with your phone? Did you unlocked bootloader or flashed custom recovery etc? You need to explain what happened, that's quite important if you want someone to help you.
I installed EMUI 9 on my p20 lite and didn't like it, so I tried one of the openkirin 9.0 beta roms. There was some features that didn't work so I decided I wanted to go back. I followed the guide on openkirin's website about going back to stock by flashing system.img, ramdisk.img, kernel.img and recovery_ramdisk.img however trying to flash ramdisk.img gives "partition length get error". Now, the phone only is able to boot into fastboot and eRecovery mode. In eRecovery the options to backup and to factory reset are grayed out however, and the "update to latest version" doesn't work. When I plug the charger in from being turned off it shows the white error screen with error 10 (boot image) and error 2 (load failed). I have a suspicion that flashing kernel.img is what causing the problem, but I don't really know enough to be sure and I don't want to do anything to make it worse since it seems like this should be fixable.
This is the only phone I have which properly worked so any help is greatly appreciated.
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
ars_chelsea said:
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
Click to expand...
Click to collapse
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Afifus said:
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Click to expand...
Click to collapse
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Tried Oreo build 150 for ane-lx1c432 and ane-lx1c782 since those are the only models my phone could be.
Although, when I do the get-build-number command in fastboot it still says I'm on a Pie build. I'm gonna try doing a Pie build and I'll get back to you.
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Yeah, pie didn't work either.
Afifus said:
Yeah, pie didn't work either.
Click to expand...
Click to collapse
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
ars_chelsea said:
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
Click to expand...
Click to collapse
I got it off of firmware finder. Are those not signed?
Afifus said:
I got it off of firmware finder. Are those not signed?
Click to expand...
Click to collapse
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
ars_chelsea said:
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
Click to expand...
Click to collapse
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Afifus said:
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Click to expand...
Click to collapse
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
yassine2217 said:
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
Click to expand...
Click to collapse
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Afifus said:
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Click to expand...
Click to collapse
great happy for you
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205