Database Info

[Q] Water Damage - Please Help Recover Data!

I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.

sj_martin said:
I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.
Click to expand...
Click to collapse
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------
BlackHawkA4 said:
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
Click to expand...
Click to collapse
Ok, again. I don't know if this would work: I can't test this out. If anyone else knows or could confirm.
IF, you can use ADB while in fastboot (Anyone know if you can or can't? Never tried it; can't test it right now) check this post out about how to mount the storage using ADB: http://groups.google.com/group/android-developers/browse_thread/thread/485d7b04bc61d7be
I'm not sure if you can use ADB in fastboot though as you usually do it while the OS is on and debugging mode is enabled. Not sure how it would work from fastboot.

I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks

sj_martin said:
I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks
Click to expand...
Click to collapse
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB

anishs said:
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB
Click to expand...
Click to collapse
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.

download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.

sj_martin said:
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.
Click to expand...
Click to collapse
as i said just try to load the recovery following that guide, try it without unlocking the bootloader if it doesn't work you have to unlock the bootloader, and maybe your sd won't be wiped but you phone data will

Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
I understand how to use cwr however i need to get that loaded onto the phone first, and for me to load it to the phone i need adb i need the computer to be able to recognize it first which it wont. it shows it in the device manger, and all the drivers are installed correctly however in command prompt when i type "adb devices" it does not list it.

Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
If you've got no warranty, you could take your phone apart to see the motherboard, and spray it with isopropyl alcohol which will properly dry it.
Sent from the future to put right what once went wrong.

For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.

If the bootloader is locked it might prevent u from flashing recovery (I dunno mine always been unlocked). But I'm not telling him to flash a new recovery. U can just boot a recovery without flashing it (again not sure if locked bootloader prevents this... but its not writing to the phone just booting a external recovery.img).
Fastboot boot recovery filename.img
Worth a try
Sent from my Nexus S using xda premium

my understanding is that i need the have the device visible in command prompt via adb to do any of this which is the issue i'm trying to solve. once i can get my computer to see the phone via adb i think i'm home free to extract all the data i need.
{
"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"
}
Also it looks like I have 2 threads in the same section now, it looks like mods moved my posts so sorry for double replying.

bedalus said:
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
Click to expand...
Click to collapse
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/

10 character delete

Ive seen some uncertainty here, so I'll offer my advice (the limited I feel qualified to give).
Unlocking the boot loader will erase everything. Considering your goal is data retrieval, I would definitely NOT ever do that.
Unfortunately, having a locked bootloader severely limits your options.
My opinion on the matter is your best bet is ADB, but if the data is not time sensitive, I would let this topic get a bit more exposure. (perhaps mirror post on some other forums like xda too)
Hopefully someone more knowledgeable can post and help you out.

sj_martin said:
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/
Click to expand...
Click to collapse
I just tried cw 3.0.0.5 per this thread:
http://forum.xda-developers.com/showthread.php?t=931865
and still get the same failure stating i need to do fastboot oem unlock

Is your bootloader even unlocked?

mathkid95 said:
Is your bootloader even unlocked?
Click to expand...
Click to collapse
No it is not. That's the point of this thread. It was a completely stock phone trying to recover data.
There is a method to root + recovery with locked bootloaders
"WITHOUT oem unlock & wipe" http://forum.xda-developers.com/showthread.php?t=931865
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Click to expand...
Click to collapse

kenvan19 said:
For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.
Click to expand...
Click to collapse
Just want to restate this. If his bootloader is locked he is pretty much SOL. He needs data off if it but to get the data he has to wipe the phone.
To the poster above me, that method no linger works. You cannot root without unlocking the bootloader. You cannot flash or boot a custom recovery without unlocking the bootloader. The links in that thread are dead.
One more time just to be sure Ira clear: you CANNOT get into a custom recovery without unlocking the bootloader.
Sent from my Nexus S MV from the XDA Premium app.

I've been looking everywhere on how to get ADB to work without debugging on; however, the only shred of hope I saw was the ability to get into your stock recovery. I didn't read on as you said you can't so it wouldn't help you anyways.
BUT!, if somehow do get into it (Or want to try to get into it over and over again and hope it works) you might be able to use ADB there. Then, that link I posted in the beginning should work to mount the storage.
Edit: Just looking at the pictures and you said you don't see the device in ADB. Have you tried actually going into ADB Shell and seeing if it connects to the phone? Mine device didn't "Show" in the list when I was using ADB but it worked.

Stuck Rooting @ tf300t

hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"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"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.

johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.

cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?

cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?

johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.

I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.

johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.

Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?

johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.

So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed

Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.

Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment

Try this guide.

[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.2.1-0 for GPD XD Plus / XD+ Handheld MT8176

Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.

{
"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
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img

My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.

I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.

Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.

I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.

"fastboot reboot" worked perfectly for me!

Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64

So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..

LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/

Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings

Contact me in discord.

Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.

Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks

[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