Database Info

How to update my H60-L04 from Kitkat 4.4.4 Custom ROM to latest EMUI/Android

Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas

derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Download the firmware you want to try (LP or MM), use huawei update extractor to extract recovery, boot, Cust and system images from UPDATE.APP (you will get it from firmware). Meanwhile make a dload folder in your SD card and copy update into it.
Flash the images to your phone using fastboot.
Fastboot Flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash Cust Cust.img
Fastboot flash system system.img
Press and hold power, vol up, vol down until the phone reboots. Let go of power but keep pressing the other two for 5,6 sec more. A forced update will start.
YOU WILL LOSE ALL YOUR DATA SO MAKE A BACKUP BEFORE DOING THIS.

derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Just make sure you full unroot your device and flash stock recovery before updating. Or you will end up with a bootloop.
You may use Multitool app.

Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0

derMelas said:
Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0
Click to expand...
Click to collapse
No problem. It is always a good idea to factory reset after a new ROM. And wipe clean SDcard.

unable to install twrp over 3.1.1.1 on mi4c (trying to go from android 7.1 to 8 or 9)

Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys

Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.

I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!

if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）

celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip

Basic Help

So Guys ..
What happened was that a few days ago basically a month I was on 10.3.7 miui then I unlocked the bootloader and installed twrp recovery in the recovery I rebooted after wiping some partition and then my system got destroyed . I tried fastboot flashing 10.2.7 but I got the message that anti rollback version is greater than my device I was very scared because my phone was unusable .. so I submitted my device to service centre and they returned the device in working condition. They left the bootloader unlocked so.Then I upgraded to 10.3.9 . Now I have an unlocked bootloader but I don't know whether it would be safe using anti rollback. And if yes would it be possible to help me install pixel experience and a detailed procedure to install twrp also I don't know would it be safe given the current anti status . I want to install pixel experience but I'm ****ting in my pants about recovery please help

WorstNightmare said:
So Guys ..
What happened was that a few days ago basically a month I was on 10.3.7 miui then I unlocked the bootloader and installed twrp recovery in the recovery I rebooted after wiping some partition and then my system got destroyed . I tried fastboot flashing 10.2.7 but I got the message that anti rollback version is greater than my device I was very scared because my phone was unusable .. so I submitted my device to service centre and they returned the device in working condition. They left the bootloader unlocked so.Then I upgraded to 10.3.9 . Now I have an unlocked bootloader but I don't know whether it would be safe using anti rollback. And if yes would it be possible to help me install pixel experience and a detailed procedure to install twrp also I don't know would it be safe given the current anti status . I want to install pixel experience but I'm ****ting in my pants about recovery please help
Click to expand...
Click to collapse
Anti rollback mechanism is activated when you try flashing an older version of MIUI while running a newer one!
No the anti rollback won't affect you unless you are planning on flashing an older MIUI from the current one!
Try Peter's TWRP(https://forum.xda-developers.com/re...pment/unofficial-twrp-3-3-1-proper-t3933531), it's much easier to install and less of a hassle running too! (Use 'flashboot flash recovery peter.img) substitute peter with whatever the file name is...
Now once TWRP is installed and the device boots perfectly, boot into TWRP and format the os partitions.
Now flash the PE ROM zip ( it has inbuilt gapps)
Your device should boot into PE now.

Naveenthemi said:
Anti rollback mechanism is activated when you try flashing an older version of MIUI while running a newer one!
No the anti rollback won't affect you unless you are planning on flashing an older MIUI from the current one!
Try Peter's TWRP(https://forum.xda-developers.com/re...pment/unofficial-twrp-3-3-1-proper-t3933531), it's much easier to install and less of a hassle running too! (Use 'flashboot flash recovery peter.img) substitute peter with whatever the file name is...
Now once TWRP is installed and the device Botts perfectly, boot into TWRP and format the os partitions.
Now flash the PE ROM zip ( it has inbuilt gapps)
Your device should boot into PE now.
Click to expand...
Click to collapse
Could you please specify which os partitions please

WorstNightmare said:
Could you please specify which os partitions please
Click to expand...
Click to collapse
System, data and the cache partitions

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers

Question Bricked trying to install LineageOS

Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks

Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.

So I managed to install twrp but couldn't install lineage or anything out of it...

I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks

if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me

Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.

Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks

It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.

Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.

marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible

Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks

So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks

Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.