Database Info

My own Mi 4c journey

My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:

MIUI 7.2.1.0 without firmware update.

how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....

tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.

I hope you can make modified rom 7.2.1.0 without bootloader.

ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.

welcome aboard, my dear friend!

Looks to me, we got another developer. Good

ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:

ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them

Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has

Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!

wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:

Failed to flash twrp in nougat 7.0

Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?

RAHUL3387 said:
Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?
Click to expand...
Click to collapse
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??

It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.

hassanjavaid8181 said:
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??
Click to expand...
Click to collapse
Thank you so much for responding. It doesn't give me any error while flashing it, going to bootloader using cmd and fastboot flash recovery twrp.img, it shows ok successful but after that i entered fastboot boot twrp.img... it's stuck in your device is booting now. I have used every available twrp in official website.. American and European ones. Nothing worked.

RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
Thank you so much for responding. Will try and get back to you with the result.

RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.

RAHUL3387 said:
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.
Click to expand...
Click to collapse
Nothing hard to do dude, the important is that it works now

Help me with my P8 Lite 2017 please

Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong

Chricap said:
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Click to expand...
Click to collapse
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong

Austinredstoner said:
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Click to expand...
Click to collapse
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem

Chricap said:
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Click to expand...
Click to collapse
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed

Austinredstoner said:
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Click to expand...
Click to collapse
Yes, I still have the TWRP installed, precisely version 3.4.0-0, since I could not find a working ROM I tried to debrand it (it was brand Tim) and I think I have done a damage to follow that guide, now I do not not even install the stock rom anymore. I don't know what to do at this point, I would leave the custom rom alone and reinstall its stock rom, at least debrand ...

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.

My story and a couple of questions

Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray

rbahr said:
Hi All,
I have a new-to-me Oneplus 7 Pro. I have been trying to get Lineage with MicroG running. Well it has been quite the adventure and I have it to the point where I have Lineage running fine, and go to reflash TWRP and have bricked the phone, which takes a bit of time to get back to the point of having Linage running again. Specifics:
Lineage version: lineage-19.1-20221219-microG-guacamole.zip
TWRP Versions: I have found that twrp-3.6.1_11-0-guacamole.img works since my phone is at Android 11.
My questions are:
Are TWRP versions tied to Android versions?
When I am trying to get the last version of TWRP installed I have tried 2 approaches:
fastboot flash recovery
fastboot flash boot
Neither worked, phone always ends up bricked. I have used:
TWRP-3.5.1-guacamole-Nebrassy-3.img
twrp-3.6.1_11-0-guacamole.img
twrp-3.6.2_11-0-guacamole.img
I also have tried to boot the images 1st using: fastboot boot twrp-3.6.1_11-0-guacamole.img
and that bricks things.
What am I doing wrong?
Thanks
Ray
Click to expand...
Click to collapse
If you look at the official installation page for your phone, you will see that Lineage OS 20 and 19.1 are supported. So you should reinstall Lineage OS 18.1 again, and then follow the steps on this page. Don't bother reinstalling GAPPS until after you upgrade it.
If for whatever reason you don't want an Android version higher than 11, let me know.

I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray

rbahr said:
I specifically don't want GAPPS or anything remotely Google related. I had tried OS 20 and found that I had a problem installing apps - probably user error, but I don't need the latest and greatest. I am currently at Android 11.
I will read through the instructions, although the number of tutorials I have gone through is craze.
Can you tell me what the relationship between TWRP and Android version is, and are you able to sus out what I did wrong with my efforts to get TWRP loaded over the lineage 19 version I was using?
Thanks
Ray
Click to expand...
Click to collapse
rbahr said:
I have been trying to get Lineage with MicroG running
Click to expand...
Click to collapse
So I guess you don't want GAPPS, just MicroG. Definitely read through the instructions I gave you, as they are the official installation and upgrade instructions.
I would recommend installing Lineage OS 20, because it is the version that is being maintained right now.
I will attempt to guide you through the steps, but I need to know what your situation is right now: Is your bootloader unlocked? What OS do you have installed right now? What recovery are you using? etc.

I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray

rbahr said:
I appreciate your help. Currently I am looking at a freshly updated phone with Android 11, and Oxygen 11.0.9.1.GM21AA.
The phone is a GM1917
Bootloader is unlocked and I am in developer mode. I have adb and fastboot loaded on my computer. I also have a working version of msm as I have bricked this thing 6 or 7 times...
Several times now, I have done the following:
Install TWRP
Install Lineage
Try and reflash TWRP <-- consistently fails at this point, gets stuck in a boot loop in the bootloader screen
Thanks
Ray
Click to expand...
Click to collapse
"Try and reflash TWRP" what do you mean, update the OS over TWRP?

I mean trying to re-install TWRP after installing Lineage

rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
OK. Can you try following the installation instructions and skip the unlock bootloader step? Do so at your own risk, because the steps say you have to be on Android 12 first. If you do follow them, just make sure you follow them very carefully.

rbahr said:
I mean trying to re-install TWRP after installing Lineage
Click to expand...
Click to collapse
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.

Honkette1738 said:
To my knowledge the guides that are provided on the TWRP site don't work for Android 12 and 13. From what I've heard, you have to root your phone and then install TWRP through Magisk.
Click to expand...
Click to collapse
The guides I linked to point to the official Lineage OS instructions, right?

ethical_haquer said:
The guides I linked to point to the official Lineage OS instructions, right?
Click to expand...
Click to collapse
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work

Honkette1738 said:
Yeah, but I was just saying how they should probably reflash TWRP instead of how TWRP's site says to, which doesn't work
Click to expand...
Click to collapse
This build uses Lineage OS Recovery instead of TWRP.

ethical_haquer said:
This build uses Lineage OS Recovery instead of TWRP.
Click to expand...
Click to collapse
I know, but TWRP can be installed with Android 13 custom roms according to the TWRP thread.