Database Info

Messed up big time?

Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?

Simple mate...
Download cm rom zip
Reboot into recovery
Mount ur storage
Put cm rom zip somewhere
Install that rom zip via recovery(twrp is recovery not the boot loader )
Flash gapps (optional if u want google services n apps) (u can do this later also)
Reboot

forstyy said:
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Click to expand...
Click to collapse
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol

doctor_droid said:
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
Click to expand...
Click to collapse
What do you mean lol?

Lethargy said:
What do you mean lol?
Click to expand...
Click to collapse
Like cwm has an option to mount storage...
Similarly does twrp has same option too?

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
As in browse files on a PC or what?

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED

forstyy said:
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
Click to expand...
Click to collapse
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Lethargy said:
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
Click to expand...
Click to collapse
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
Click to expand...
Click to collapse

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
Just push a cm rom made for ur hammerhead...

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)

Lethargy said:
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Click to expand...
Click to collapse
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Its the bootloader fastboot is what's used in the bootloader. And yeah, flash a custom recovery then you're good to go!

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Welcome to flashing world...now since u know how to revive ur phone... U will definately mess up it again...

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
Mount storage only works on a non-fuse /sdcard. Meaning either:
- device has removable sdcard
- device is not using fuse for internal storage.
Nexus 5 meets neither.
Sent from my Nexus 5 using Tapatalk

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
My thoughts exactly
sent from my thumbs

Same here I've messed my n5 up about 5 times these Google images come In handy

Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:

forstyy said:
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
Click to expand...
Click to collapse
The N5 is basically the best contemporary phone to soft brick or break. The support and tools available are great.

[Q] Stock OPO soft bricked after turning off at night.

Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.

Anybody?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when I hit Apply Update and then use storage as option.

moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....

jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.

moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...

jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.

moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?

geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.

moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?

geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.

moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb

geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.

moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb

geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this

geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.

moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here

There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.

tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.

[Recovery]TWRP 3.1.1-0 LG G5 H840

DO NOT FORMAT YOUR MICRO SDCARD INSIDE TWRP RECOWERY
WARNING: If you want tho use /data and internal sdcard first have to format data in stock recovery This will wipe your internal storage, and factory reset your phone!
encryption is not supported yet
To flash this img to your phone use fastboot
Code:
fastboot flash recovery twrp-x.x.x-x-h840.img
+new test build with encryption support
source code https://github.com/synescu/twrp_lg_h840
1.Unlocking the bootloader.
1.1Get the latest drivers: ( http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 )
1.2Get ADB fastboot. If you hate installing huge files for just a few commands, you have 3 options:
-MINIMAL ADB and fastboot: (https://forum.xda-developers.com/showthread.php?t=2317790 )
-15 seconds ADB Installer v1.4.3: (https://forum.xda-developers.com/showthread.php?t=2588979 )
-SDK Platform-Tools coming directly from google: (https://developer.android.com/studio/releases/platform-tools.html )
I personally went with the “15 seconds ADB Installer v1.4.3”, because it installs also a Google driver, which might, or might have not helped out in the process to follow.
1.3Follow the instructions at the official LG unlocking page ( https://developer.lge.com/resource/mobile/RetrieveBootloader.dev ), just keep in mind that after step 1.2 you have adb ready to go @ your main drive C:\adb. You go to that folder shift + right click and open a command prompt at that location, the rest is trivial.
2.Updating to the latest official stock android.
2.1Get the latest kdz from: (https://lg-firmwares.com/lg-h840-firmwares/ ). As far as I know you can go for any of those firmwares, but it is advisable to use one from your region (Europe, South America, Middle East). As mentioned above my LG G5 H840 is the newest European model, totally unbranded. So I took the 20c for Spain. This is as high as you can get at present moment.
2.2 Flash with LGUP 1.14 and UPPERCUT 1.0.0, both available at: (http://downloads.codefi.re/autoprime/LG/LG_G5 )
2.3 Reboot and do a quick setup. I recommend to have your sim card, SD card out at this moment, do not connect to wireless networks, all of this you will have plenty of time to do later, besides whatever you set at this point will be lost in the next step.
3.Get TWRP and root
3.1TWRP. As a courtesy of synescu, we have 2 versions: a regular one and such with encryption support. It took me long to realize that only the one with encryption would work on a latest H840 installed with v20c. So I guess if you have an old phone and possibly firmware 10a/b/c/d, than you can try “twrp3.1.1-0-h840.img”, otherwise go straight to “twrp_encryption-h840.img”. If you use the one without encryption support you will find no way to root the phone, because it can not see the SD card, or any USB flash attached and also if you connect the phone to a PC with MTP mode, or any other mode you won’t be able to browse both (internal and external) memories on that phone.
3.1.1Put on a SD card following files: 1) latest stable SuperSU 2.79 2) no-verity-opt-encrypt.zip from here (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip ) and just in case although not mandatory “twrp_encryption-h840.img”.
3.1.2Put in the C:\adb folder the “twrp_encryption-h840.img” and the stock recovery from here (https://forum.xda-developers.com/attachment.php?attachmentid=4149809&d=1494791791 ). The stock recovery is necessary in case you make a mistake and have to do a factory reset.
3.1.3Turn off the phone.
3.1.4Boot into stock recovery (holding volume down + power, at LG logo releasing power shortly and than pushing power again).
As a side note here, after I unlocked the bootloader I’ve got that annoying message on start-up that the phone is untrusted. With G4 H815 it was a small message in the upper corner, this time around it is a huge message in the middle of the screen. LG, for the love of god! After all the playing, I have now also a message screen, which I call “Options Menu”, it shows right after the nagging untrusted message. Although esthetically ugly, I have an easy way to go to recovery and fastboot in each and every regular power on, or restart. As said the Options Menu is showing up for 5 sec after the untrusted nagger. If you click the volume up, or down you get to the options (Power off, Restart, Recovery, Fastboot ), otherwise after 5 sec the phone would boot normally. I don’t know if this is the expected behavior of the phone, or did I trigger it somehow, but now I don’t have to use the combo buttons for anything.
Back from the side note. The new stock recovery is a white screen with 2 options for No and Yes. Go for YES and than YES again, after both YES the phone will be factory reset and will reboot. Do not allow it to boot though, because the userdata will be encrypted at this point and you will have to repeat the reset again. Use the combo buttons for recovery, which will bring you to the “Options Menu”, or Volume up and plug in the phone into the PC. Yet again there is hardly any time so maybe plugin in won’t be fast enough, so just keep pressed the combo buttons, also change with volume up and power, or remove the battery and start again. In any event do not let it boot until it brings you to the “Options Menu”
3.1.5In the Options Menu pick fastboot and plug the phone to the PC
3.1.6Open command prompt in adb and flash TWRP ( fastboot flash recovery twrp_encryption-h840.img ) you might be ok also to do factory reset from adb with this command (fastboot –w ), but unfortunately I forgot already if I did it, when it finally worked for me
3.1.7Disconnect from the PC and pull the battery out, or just keep the buttons combo pressed. It is possible that you see the old stock recovery (white screen YES/NO), which might have stayed somehow in memory. Do not perform further resets, just keep pressing the button combo and it will reboot eventually to the Options Menu.
3.1.8There you go 3 times volume down and power to pick recovery. Follows a reboot of the bootloader, nagging screens, but eventually it loads TWRP.
3.2Root.
3.2.1For some reason even after the factory reset, the data partition keeps an encrypted flag. So you can not write to it. Stock recovery should have reset it to non-encrypted, but it does not do it correctly, I guess. Therefore you go to Wipe, pick only the Data check box and go to change format in the bottom. Change the format to FAT and than back to EXT4
3.2.2Go to the SD card and flash no-verity-opt-encrypt.zip and SuperSu. Yes I know, that SuperSu is supposed to install also no-verity, but I like to flash both just in case.
3.2.3Do NOT wipe anything in TWRP at this point. Reboot only!!!!! Once the phone has booted in v20c you can go back to TWRP, Wipe and make all the backups you like
Thanks to @svetloslav for this complex post

Thanks a lot.
Can't wait to flash!!

YESS finally we have root on the SE thank you very much man

Hi all. When I try to flash recovery, fastboot give me that message:
target reported max download size of 536870912 bytes
sending 'recovery' (15089 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
Any suggestion? Thanks
Solved: I had not extracted the .img from the .tar archive

synescu said:
For now external sd card is mounted as internal. De only way you can flash something for now When I would have more time I will try to fix this and upload the source to github. I rooted the phone and installed the supersu and no verity zip
source code https://github.com/synescu/twrp_lg_h840
Click to expand...
Click to collapse
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?

bob8x said:
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
Click to expand...
Click to collapse
I'm booting this vith android 7.0
6.0 must boot just fine. didn't tried encryption but I'm pretty sure that doesn't work
Build compiled from Omni 6.0 sources
Sent from my LG-H840 using Tapatalk

Thank you very much for your precious time my friend. Good work

Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?

Wire1122 said:
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Click to expand...
Click to collapse
Yes internal storage it's properly mounted now
Sent from my LG-H840 using Tapatalk

Anyone can confirm if encryption works?
Sent from my LG-H840 using Tapatalk

synescu said:
Anyone can confirm if encryption works?
Click to expand...
Click to collapse
I have flash it succesffully. But how can I yest if it works?

I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H840 using Tapatalk

Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs

Wire1122 said:
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
In Order to use data first you have to factory reset your phone using the stock recovery
Sent from my LG-H840 using Tapatalk

How? Stock recovery? Where is it? I'm noob and rooted with supersu

My log

Wire1122 said:
My log
Click to expand...
Click to collapse
stock h840-recovery.img

I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
Why would you think that you would keep TWRP after flashing stock recovery? Also, why would you flash stock recovery after flashing TWRP and SuperSU? You either have TWRP or stock recovery, not both. Also, don't ever recommend flashing stock recovery after modifying system in any way unless you reflash whole stock system as stock. Anyways, all you need to do to get TWRP back is use the :
fastboot flash recovery TWRP.img

[SOLVED] Mi A1 BOOTLOOP

THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:

Thanks
---------- Post added at 08:37 PM ---------- Previous post was at 08:19 PM ----------
a question only with that ROM or can I download the latest stock ROM

Dualitydark said:
a question only with that ROM or can I download the latest stock ROM
Click to expand...
Click to collapse
Only with that ROM bro, because the EFS file was backed up from that ROM

I just created this account to say thank you for this solution.
My MI A1 got bricked/in bootloop after the newest update.
I couldn't flash it via MiFlash with a simple stock ROM, I needed to unlock it via the unlocker app of that MIUI thing.
With flashing successfully after, I got the same old bootloop screen.
Then I ran through the steps up until 8.
After that, I rebooted, and the phone started up normally.
So in case people managed to flash their device and do your method, there's no need to flash it again and for TWRP 3.3.1 to solve bootloop issue.
At least for me it wasn't needed.
Once again, thank you very much!!! :good::good::good:

Fantastic. Thanks friend.

My phone just got in to boot loop when I tried to reboot from magisk app. I successfully flashed stock firmware from miflash tool but still stuck on boot loop.
(my phone is bootloader unlocked)

alkoka said:
I just created this account to say thank you for this solution.
My MI A1 got bricked/in bootloop after the newest update.
I couldn't flash it via MiFlash with a simple stock ROM, I needed to unlock it via the unlocker app of that MIUI thing.
With flashing successfully after, I got the same old bootloop screen.
Then I ran through the steps up until 8.
After that, I rebooted, and the phone started up normally.
So in case people managed to flash their device and do your method, there's no need to flash it again and for TWRP 3.3.1 to solve bootloop issue.
At least for me it wasn't needed.
Once again, thank you very much!!! :good::good::good:
Click to expand...
Click to collapse
Me too! Infact, I tried to flash pixel experience and phone was stuck in bootloop, thanks to this guide I was able to make phone working again!
You are a true hero, thank you so much!

it is showing waiting for device

Hi all,
Just sharing my experience. I own two Mi A1 phones (I just love this model and I thought I'd get a spare)
On my first Phone, I got involutarily upgraded to Pie and it wass hell to get it back. I followed a guide here and flashed someone else's EFS partition. That feels dirty to me so I decided to do things properly with my spare phone.
Here's what I did:
- Booted into the OS the phone shipped with (Nougat, good times!)
- Unlocked bootloader and booted into TWRP
- Did a FULL BACKUP. This is what I didn't do with my first one! It's CRUCIAL that you back up your phone first thing when you get it. Don't even connect to wifi, just unlock the bootloader and back it up with TWRP! IF you don't, you will NEVER be able to get back to how things truly were out of the factory. Of course you need to copy the backup to your PC for safe keeping.
- Now I went my merry way installing Lineage os, eventaully upgrading to Pixel Experience (Android 10, which turns out I hate).
- I wanted to get back to stock rom. So I booted into TWRP and did a full restore.
- Unfortunately, It boot looped.
- Flashed EFS and Boot again (from my backup). No luck, no effect.
- Flashed a stock Oreo image (V9.6.8.0.ODHMIFE) using Mi flash Tool and the "clean all and lock" option (I regretted doing this because I realized I wasn't sure if I'd be able to get fastboot again after oem lock, but it turned out fine)
- After flashing it, It was still boot looping! Panic.
- Tried booting into fastboot and succeeded (yay)
- Did a fastboot oem unlock and luckily The bootloader got unlocked no problem.
- Phone finally booted! Hooray.
Just putting this in writing for future reference in case anyone is wondering about the steps to take.

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
OP, all the links are expired ....What do?

my tissot Bootloop android one logo restart
tissot my bootloop. until androidone logo restarts.
can't flash with stock rom.
I've tried flash with miflash.
both edl mode and testpoint flash are successful but still the same.
but I can install twrp and custom rom, no problem.
i just wanna go back to stockrom
if there are friends here who can provide a solution.
thank you
sorry bad english

Hello everyone.
I am asking for your help.
I tried to follow the procedure described step by step until the end.
But the device keeps rebooting in a loop.
It boots up correctly, I can perform a few steps of the initial configuration and then it reboots.
What else can I try to do?
I don't have backups of my device.
Thanks in advance.

surferstory81 said:
Hello everyone.
I am asking for your help.
I tried to follow the procedure described step by step until the end.
But the device keeps rebooting in a loop.
It boots up correctly, I can perform a few steps of the initial configuration and then it reboots.
What else can I try to do?
I don't have backups of my device.
Thanks in advance.
Click to expand...
Click to collapse
[FASTBOOT][OTA] Xiaomi Mi A1 OTA & FASTBOOT Images
I just find and collect all available OTA and Fastboot links for Xiaomi Mi A1 How to extract OTA link: https://forum.xda-developers.com/showpost.php?p=74828109&postcount=2 Tool to unpack OTA images...
forum.xda-developers.com

GOD BLESS YOU

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
Sorry but I have a question
I didn't take a backup from my twrp and now I can't do anything
I just wanna ask that rom you uploaded here is custom rom? I mean I should install it with TWRP or I have to install this rom with mi Falsh tool ?
And what do you mean to flash TWRP ?
We didn't do that at first ?
I'm confused

Hey bro i really breaked my phone
I forgot to flash twrp at the end and my phone only vibrate after flashing
Plz help me

you're my hero man...
solved my problem so far...
now i can flash custom rom again....

tunhan9x said:
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM)
And I would like to share how to RESOLVE it.
**your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot mode. Type "fastboot oem unlock")
1) Download Stock MIUI 9.6.8
2) Download TWRP_fastboot_only (This TWRP only run ONE TIME, to Restore EFS and Install Official TWRP 3.3.1). Unzip it, we need boot-recovery.img file
3) Download TWRP 3.3.1
4) Download EFS_TWRP for MIUI 9.6.8
5) Download and Install minimal_adb_fastboot_1.4.3
6) Run "Minimal ADB and Fastboot" in your Desktop. Type "fastboot boot " and drag boot-recovery.img file (in step 2) to Command Prompt window. It will complete your command, like this "fastboot boot "...\boot-recovery.img". Press Enter
7) When the TWRP start up, connect your phone to PC. Unzip file EFS_TWRP, and copy to folder TWRP in your phone.
8) Go to Restore in TWRP and choose Backup folder, restore *Boot* and *EFS* and swipe
9) Now flash Stock MIUI 9.6.8 (in step 1) and TWRP 3.3.1 (in step 3)
10) Everything is OK now! Congrats. :good:
Click to expand...
Click to collapse
Kindly explain process 9 in details. I don't know how to flash.

Get this error.
My phone is stuck in bootloop and cannot unlock bootloader.
Anyone have a solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have flash stock from via Testpoint but when I boot into TWRP my touch screen is reversed. How can I fix it?

[RECOVERY][UNOFFICIAL] TWRP 3.6.1 for UMIDIGI F1 and F1 Play [11/04/2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an UNOFFICIAL TWRP recovery for the UMIDIGI F1 and F1 Play
Builded from scratch
Whats Working :
- Decryption
- Backup / Restore
- ADB
- MTP
- OTG
- Flash System Image and Vendor Image also
Known Bugs :
- I think none
Instructions :
Using SP Flash tool
- Open flash_tool.exe from sp flash tool folder ( you can download it from here)
- Choose MT6771_Android_scatter.txt from UMIDIGI Stock Firmware
- Tap on Recovery and Choose TWRP-3.6.1-XX.img
- Click on Download and Reboot your Phone and plug your usb cable and press in Volume up button
-Wait to finish and enjoy
Using Fastboot ( you need Fastboot to do that)
- Power off
- Press on Power+Volume up button to boot up to Fastboot
- Execute "fastboot flash recovery TWRP-3.6.1-XX.img"
- Wait to Finish And Execute "fastboot reboot recovery"
- Enjoy
Using Another Recovery
- Copy TWRP-3.6.1-XX.imgto SD Card
- Press Install and Choose TWRP-3.6.1-XX.img and Choose Recovery
- Wait to Finish And Reboot to Recovery
- Enjoy
Downloads :
F1 : https://www.mediafire.com/file/91k98oii8ab7j1l/TWRP_3.6.1-F1.img/file
F1 Play : https://www.mediafire.com/file/dn8mzk8bpulvqig/TWRP_3.6.1-F1_Play.img/file
Device Tree : https://github.com/shadowofleaf96/android_device_umidgi_f1/tree/TWRP9.0
Credits :
- PeterCxy
- UMIDIGI
if you consider Donating
Thanks​

@Shadow Of Leaf, Thanks for your work.
I tried to flash the .img file today using fastboot command and for some reasons my F1 reboots to system, not recovery.
The fastboot flash command completed OK for both Sending and Writing but when I tried
fastboot reboot recovery
the phone reboots to the system.
I also tried
fastboot boot TWRP-3.5.2-F1.img
but get the same result.
Any idea what went wrong and how to fix it? TIA.

nnSlick said:
@Shadow Of Leaf, Thanks for your work.
I tried to flash the .img file today using fastboot command and for some reasons my F1 reboots to system, not recovery.
The fastboot flash command completed OK for both Sending and Writing but when I tried
fastboot reboot recovery
the phone reboots to the system.
I also tried
fastboot boot TWRP-3.5.2-F1.img
but get the same result.
Any idea what went wrong and how to fix it? TIA.
Click to expand...
Click to collapse
it is not fastboot flash boot
it is fastboot flash recovery TWRP-3.5.2-F1.img
when it finished tap fastboot reboot when phone is rebooting click on volume down until the bootlogo come out then it will go to recovery

Shadow Of Leaf said:
it is not fastboot flash boot
it is fastboot flash recovery TWRP-3.5.2-F1.img
when it finished tap fastboot reboot when phone is rebooting click on volume down until the bootlogo come out then it will go to recovery
Click to expand...
Click to collapse
@Shadow Of Leaf
Thanks for the prompt response, appreciate it.
I was not clear in my previous post, what I meant was I tried 2 ways
1. flash using fastboot flash command, and
2. boot directly using fastboot boot command
and both times I could not get TWRP to run.
Here is the output of the first method:
When I click on Vol- while the device was rebooting, I saw the boot logo andn then a screen with Chinese menus on the left top of the screen. Weird!
May be the file was not written properly? I tried to redownload the file twice but same thing happens.

nnSlick said:
@Shadow Of Leaf
Thanks for the prompt response, appreciate it.
I was not clear in my previous post, what I meant was I tried 2 ways
1. flash using fastboot flash command, and
2. boot directly using fastboot boot command
and both times I could not get TWRP to run.
Here is the output of the first method:
View attachment 5380507
When I click on Vol- while the device was rebooting, I saw the boot logo andn then a screen with Chinese menus on the left top of the screen. Weird!
May be the file was not written properly? I tried to redownload the file twice but same thing happens.
Click to expand...
Click to collapse
did you unlock your bootloader ???
if yes when flash try the power and volume down combination to go recovery
if not try this
Unlock the bootloader (will result in a factory data reset and a warning message on the boot screen) YOU LOSE YOUR WARRANTY BY DOING THIS!!!
a) Enable Developer options
b) Enable OEM unlock and USB debugging. (Install ADB drivers on your computer)
c) Connect your phone to USB and in a command window type adb reboot bootloader
d) Type fastboot flashing unlock
e) Confirm your decision on the phone (You can re-lock the bootloader with fastboot flashing lock)

Shadow Of Leaf said:
did you unlock your bootloader ???
if yes when flash try the power and volume down combination to go recovery
if not try this
Unlock the bootloader (will result in a factory data reset and a warning message on the boot screen) YOU LOSE YOUR WARRANTY BY DOING THIS!!!
a) Enable Developer options
b) Enable OEM unlock and USB debugging. (Install ADB drivers on your computer)
c) Connect your phone to USB and in a command window type adb reboot bootloader
d) Type fastboot flashing unlock
e) Confirm your decision on the phone (You can re-lock the bootloader with fastboot flashing lock)
Click to expand...
Click to collapse
I did unlock the bootloader, and every time the phone reboot I see a warning that the device is unsafe.
It appears that flashing went OK, as reported by the 'fastboot flast recovery...' command. But when I try to go to recovery with Power+VolDown combination the phone just could not run TWRP!
I am not sure if it is related but after power off, when I try to reboot with Power+Vol Down (or Up) combination the boot logo appears then disappears (looping?) and I do not see a boot menu (as shown in a YouTube video). When I reboot from fastboot it seems to go to some boot program with a Chinese menu.

nnSlick said:
I did unlock the bootloader, and every time the phone reboot I see a warning that the device is unsafe.
It appears that flashing went OK, as reported by the 'fastboot flast recovery...' command. But when I try to go to recovery with Power+VolDown combination the phone just could not run TWRP!
I am not sure if it is related but after power off, when I try to reboot with Power+Vol Down (or Up) combination the boot logo appears then disappears (looping?) and I do not see a boot menu (as shown in a YouTube video). When I reboot from fastboot it seems to go to some boot program with a Chinese menu.
Click to expand...
Click to collapse
ok another solution
try to reboot your phone to the system and enable adb (android debug shell) and type adb reboot recovery
it will reboot to recovery

Shadow Of Leaf said:
ok another solution
try to reboot your phone to the system and enable adb (android debug shell) and type adb reboot recovery
it will reboot to recovery
Click to expand...
Click to collapse
@Shadow Of Leaf
Appreciate you prompt help!
Not sure what happened but I retried one more time and guess what it works this time . Thank you so much!
I notice that it takes long time to show the menu and it looks like TWRP tries to decrypt data, even though I already did a factory reset.
Now I can root and install custom ROMs. Thanks again!

nnSlick said:
@Shadow Of Leaf
Appreciate you prompt help!
Not sure what happened but I retried one more time and guess what it works this time . Thank you so much!
I notice that it takes long time to show the menu and it looks like TWRP tries to decrypt data, even though I already did a factory reset.
Now I can root and install custom ROMs. Thanks again!
Click to expand...
Click to collapse
you welcome anytime

Hi thank you so much for your work.
But when I try to flash recovery and suddenly, when I type fastboot reboot recovery , it says something like can't get recovery partition unable, and then when I go manually into recovery I get stock one.
Of course the flashing of twrp recovery goes all well, so it's a strange issue. Just one time after the flash I successfully got twrp but lost after reboot and I didn't have internal memory mounted.
Can you help me?
Thanks

kayuz said:
Hi thank you so much for your work.
But when I try to flash recovery and suddenly, when I type fastboot reboot recovery , it says something like can't get recovery partition unable, and then when I go manually into recovery I get stock one.
Of course the flashing of twrp recovery goes all well, so it's a strange issue. Just one time after the flash I successfully got twrp but lost after reboot and I didn't have internal memory mounted.
Can you help me?
Thanks
Click to expand...
Click to collapse
yes for sure
first use this recovery https://forum.xda-developers.com/t/...icial-twrp-3-3-1-for-umidigi-f1-play.4007315/ for now
data exryption work
flash this recovery in fastboot(fastboot flash recovery 'recovery file') and type fastboot reboot
when reboot a long click on volume up button until seeing umidigi logo it will work

Shadow Of Leaf said:
yes for sure
first use this recovery https://forum.xda-developers.com/t/...icial-twrp-3-3-1-for-umidigi-f1-play.4007315/ for now
data exryption work
flash this recovery in fastboot(fastboot flash recovery 'recovery file') and type fastboot reboot
when reboot a long click on volume up button until seeing umidigi logo it will work
Click to expand...
Click to collapse
that's the error:
fastboot: usage: unknown reboot target recovery
I tried but can't access recovery, I need to plug out the cable before pressing vol up?

kayuz said:
that's the error:
fastboot: usage: unknown reboot target recovery
I tried but can't access recovery, I need to plug out the cable before pressing vol up?
Click to expand...
Click to collapse
just go to stockrom and type adb reboot recovery

I solved flashing the twrp by another person, currently on phone so can't see who was.
Anyway it appears that was an issue with decryption, because that twrp can see internal storage. Flashed all and will send feedback in appropriate thread ;-)
Shadow Of Leaf said:
just go to stockrom and type adb reboot recovery
Click to expand...
Click to collapse

TWRP 3.6.1 stable new version at last
i think it is bugless but try it out and report

Shadow Of Leaf said:
TWRP 3.6.1 stable new version at last
i think it is bugless but try it out and report
Click to expand...
Click to collapse
hello friend, could you tell me what process you did to compile a twrp for your umidigi, I wanted to make one for my umidigi a9 pro 2021, it has the same processor as your device.

Isaac™ said:
hello friend, could you tell me what process you did to compile a twrp for your umidigi, I wanted to make one for my umidigi a9 pro 2021, it has the same processor as your device.
Click to expand...
Click to collapse
you can use this guide to build twrp for your device and use this device tree thats is compatible with your device and has a newer vendor (mine is comptable with old pie vendor that will have issues with data encryption)
link of the guide : https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL/blob/master/docs/HOW-TO-BUILD.md
links of device tree : https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_XL_EEA
Common device treehttps://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL
you have to change the common device tree and the device tree to your device