yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 5 Questions & Answers] Keyvannn:
https://www.google.de/url?sa=t&sour...CDkwAg&usg=AFQjCNF1sHlk2z9QIx28jtvfnGP_UlkifA
[Xiaomi Mi 5 Questions & Answers] fabioplata:
following this video.

https://xiaomi.eu/community/threads/6-12-8.36620/page-12#post-338195
[Xiaomi Mi 5 Questions & Answers] djekan:
The link don't work, can't see nothing...

Enviado do meu MotoG3 atravÃ©s de Tapatalk
[Xiaomi Mi 5 Questions & Answers] djekan:
That video is to put device in EDL Mode, mine is always in EDL [emoji19]

Enviado do meu MotoG3 através de Tapatalk
[Xiaomi Mi 5 Questions & Answers] Keyvannn:
any solution?

i have same problem
[Xiaomi Mi 5 Questions & Answers] djekan:
Hi, no solution, returned to the seller.

Enviado do meu MotoG3 através de Tapatalk
[Xiaomi Mi 5 Questions & Answers] Keyvannn:
Solved

3rd post https://xdaforums.com/mi-5/help/bricked-mi5-t3528810/post70316914#post70316914
[LG G5 Themes, Apps, and Mods] Raafat:
[IMG="LG Theme Template"]https://raw.githubusercontent.com/RaafatAkkad/LGThemeTemplate/master/_app/src/main/res/drawable-xxxhdpi-v4/theme_preview_0.png[/IMG]

Code: https://github.com/RaafatAkkad/LGThemeTemplate

Releases: https://github.com/RaafatAkkad/LGThemeTemplate/releases

Happy Theming!
[LG G5 Themes, Apps, and Mods] enteresan05:
Tercüme et

bu temalar hangi programla yapılıyor

With which program these themes are made
[LG G5 Themes, Apps, and Mods] wizard7926:
This is incredible!

So, it looks like common > src/main > res > drawable-xxxhdpi-v4 contains the Yellow, Green, and Pink background files respectively. If we wanted to make a barebones theme, would we just replace those three files and package with gradle? What about things like the dialer keys, etc, where do those resources live?

I'm super-new to theming and app development in general, but I think my skills as a designer would really benefit the community, I'd love to start doing themes for you guys!
[LG G5 Themes, Apps, and Mods] slamanna212:
Thank you so much for this! I have the info all there but how do you make the apks that actually theme the apps? like come.lge.theme.template.common.apk?

Edit, I did find this: https://plus.google.com/+PiereRalph/posts/9zqVrHrCWrS

Just do that for each app I want to theme? This is going to be fun haha
[LG G5 Themes, Apps, and Mods] kate_loves_cats:
eczplaaain!

but can you pleas tell what to edit to change the colors and phonts? im not very good at java.
[LG G5 Themes, Apps, and Mods] batkinson001:
Is there a guide on how to use the files in the template? This seems more complicated than just changing a few colours or substituting images.

The readme.md doesn't say much...

I am not a programmer.
[LG G5 Themes, Apps, and Mods] kate_loves_cats:
what do i edit here to change the colors? and how do i install it on my phone?
[LG G5 Themes, Apps, and Mods] christopherrrg:
This literally helped every question I ever had however once I edit an apk file do they need to keep the name com.lge.theme.template.common.apk?
[LG G5 Themes, Apps, and Mods] christopherrrg:
This response may never get to you but if it does use apktool to decompile it then in assets/overlays/ you will find the apks of each individual app. Use apktool to decompile those and then go from there. I just decompiled the stock 'black' theme. Once finished theming replace the new modded apk where the overlay apks are. Then use apktool to repackage. It may need to be signed when completed however, I haven't quite gotten there yet. :D
[LG G5 Themes, Apps, and Mods] Ardany Jolón:
Hi guys, I have a question regarding com.lge.theme.template.common.apk, this apk refers to everything in the framework-res.apk is true?

Thanks for the template.
[Huawei P9 Lite Questions & Answers] Edston:
Hi guys, i'm trying to remove carrier footprint on huawei p9 lite, and wanted to ask if i can delete Telecom(name of carrier) files in system>priv-app>Telecom and if it will help in any way.

Or if there is a better way to remove this please suggest one. I dont want to root the device if not neccesary.

Any help?
[Nexus 6 Q&A, Help & Troubleshooting] leo5111:
Is The xt 1103 model is fully compatible with At&t/Cricket for Lte ?? Thanks for replys
[Nexus 6 Q&A, Help & Troubleshooting] snowrelyt:
yes
[Nexus 6 Q&A, Help & Troubleshooting] leo5111:
I thought so but wanted to double check thank you :p
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.

Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.

Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!

This tool will allow you to:

Backup your boot and recovery partitions.

Flash a boot or recovery image (including the signed TWRP image).

See following posts for operating system specific setup instructions.

Once your setup is complete, enter EDL mode:

1. Power off phone.

2. Hold both volume buttons.

3. Plug phone into computer.

4. For G models, you must "adb reboot edl" (see other threads).

Usage:

axon7tool <mode> <partition(s)>

Note: The tool name will vary depending on your operating system.

<mode> is -r for read, -w for write.

For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin

For write mode, <partition> is boot or recovery. File will be read from <partition>.bin

Examples:

To backup everything on Linux:

./axon7tool-1.5-linux -r gpt boot recovery

To write recovery on Win64:

Place file as recovery.bin

axon7tool-1.5-win64 -w recovery

Links to axon7tool:

axon7tool-1.5-linux (main)

axon7tool-1.5-linux (alternate)

axon7tool-1.5-win64.exe (main)

axon7tool-1.5-win64.exe (alternate)

Link to signed TWRP removed.

FAQ:

Q: Can you provide a signed boot image with root?

A: No. I do not have the ZTE signing key, and tenfar's images are not current.

Q: Can I have the source code for the tool?

A: No.

Q: Can you provide the programmer?

A: No.

Q: Do you accept donations?

A: No, all work is provided freely for community use.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Setup instructions for Linux:

1. Ensure your login user is in the "plugdev" group.

$ id

You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.

2. Ensure your udev rules are setup.

Create a file eg. /etc/udev/rules.d/qcom.rules that contains:

SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"

3. All done!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Setup instructions for Win64:

1. Download zadig from http://zadig.akeo.ie/

2. Put device in EDL mode.

3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.

4. All done!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Reserved for Mac instructions.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kgptzac:
Questions:

1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)

2) The signed TWRP image is by... ZTE?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.

Like [MENTION=7890973]tennear[/MENTION] mention about try first by using -r (read) then just flash the sign TWRP.

I personally recommend just flash TWRP and DON'T mess with Boot image.

2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.

2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.

Step 1: Enable Developer options in phone by tapping the build number

Step 2: Enable OEM Unlock in phone (is this needed?)

Step 3: Enable debugging (for adb)

Step 4: Connect phone to PC

Step 5: Download Zadig

Step 6: Install Zadig

Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)

Step 8: Enter the command “Adb Devices” to reassure your device is detected

Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode

Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device

Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”

Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located

Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)

Step 14: Enter command “axon7tool -r gpt”.

Step 15: Enter command “axon7tool -r boot”

Step 16: Enter command “axon7tool -r recovery”

Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.

Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?

Step 19: enter “axon7tool -w recovery recovery.bin

Step 20: Wait for the command to finish

Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.

Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)

Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP

Step 24: Flash the .zip of your custom ROM of choice in TWRP

Step 25: Flash the .zip of your Google Apps of choice in TWRP

Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP

Step 27: Reboot your phone, enjoy the custom ROM of your choice.

Is this the correct procedure?

I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?

For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.

Thanks for the help.

Jan
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
[MENTION=4464865]Controllerboy[/MENTION] close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
None of these steps should be necessary.

I believe you just run zadig, I don't remember an installer.

Renaming the tool is optional.

The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.

Yes, this is correct.

Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.

Everything past step 20 is up to you. :)

You cannot unzip an img file.

The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.

If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rczrider:
Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
I found this on the 65th page of Tenfar's thread (http://xdaforums.com/showpost.php?p=69215285&postcount=642)

So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?

The issue here is that the hosting used is so crappy I can't even download the file...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
That is correct.

d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
[MENTION=7890973]tennear[/MENTION]

As far as u know TWRP is the same for every A7, sign or not.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Unpacking the TWRP image for A2017U, it says:

ro.product.model=A2017U

So this recovery seems to be specific to A2017U.

But unpacking the TWRP image for A2017 (China), it says:

ro.product.model=ZTE A2017U

Hmm, different but still A2017U.

I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nuserame:
So can the Linux tool be used on Mac?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
No. I have not built the tool on Mac yet. I will try to do that soon.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MATTHEWLONG:
I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.

Thank you for the time and support.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.

It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] le_cactus:
Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.

TIA,

Cheerz,

/Cacti
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
* Not being able to write two partitions at the same time is a huge feature. Writing both boot and recovery is a major source of bricked devices.

* It consults the device partition table to ensure that it finds the proper location for the partitions. tenfar's tool does not do this -- it blindly assumes all devices have the same partition table. (No, I don't have his sources. Yes, I know this to be true.)

* It can read the partition table (GPT). This is handy for me, to diagnose users' issues.

* It runs on Linux (and I can make a Mac version).

* It is maintained. tenfar is MIA.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] le_cactus:
Hi Tennear,

Sorry if you feel offended, seriously it was in no way intended as such! Your work and time is very much appreciated.

Thanks for the info, it indeed seems a much better tool than tenfars tool. Maybe I'll find the courage to use it some day. I'm still very much afraid of ending up in DFU mode.

Cheerz,

/Cacti
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Thanks for this explanation.

I always guessed Tenfar's tool would simply write to static offset's and not looking at the GPT table at all. This is an huge improvement.

Would this tool work for the Axon-7 mini users?

Not having one. Just curious for those users coming into the Axon7 thread that asked if Tenfar's tool would work. I warned them not to try because of my guess.

Yours could actually read from GPT and at least extract (read) boot and recovery. Which then could lead to a dev singing it's own Boot to be able to boot a custom recovery. Am I right about your tool opening up this possibility?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
Ok, don't know why I missed the obvious message that the BL should be unlocked for in order to run ANY custom ROM. I guess that'll be my next step, unlocking BL via TWRP before (hopefully) trying ZAD Mix and CM
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
It is unlikely that this would work for axon7mini. It is a different SoC (SnapDragon 617). And I don't know the ZTE key policy -- they may use a different signing key for each device. (Yes, the programmer is signed).

However, it would not hurt to try... the worst that can happen is it won't work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Oh, this is surprising. I will need to investigate.

I must confess, I built the Win64 version on Linux using mingw64 and I never actually tried running it. But this is the same code I have used in the past, and I always used zadig to install the WinUSB driver for EDL mode.

Thanks for the very detailed writeup!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Yes I agree. Someone with an Axon-7 mini should try your tool and "read". It can't hurt to read it won't brick the device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] puremind:
Can it be used to root similar instead of the tool used here?

http://xdaforums.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204

It seems cumbersome to always have to check the com port before flashing boot / recvery when your tool does not require such a thing?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tebor:
[MENTION=7890973]tennear[/MENTION]

Myself and [MENTION=4464865]Controllerboy[/MENTION] have lost our IMEI's. Any chance you could help?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] manu7irl:
There is a solution for that:

Do

From a computer connected to the phone on TWRP:

adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Then
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2

This will blank your modem data partitions then at reboot the phone will recreate the missing data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tebor:
I tried that and all it did was get wifi working again

Still cannot connect to mobile data. Sim is detected but no connection. Imei''s still zeroed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
[MENTION=6054963]Tebor[/MENTION] how did you lose your IMEI?!?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
Sorry for speaking in someone else's name, but [MENTION=6054963]Tebor[/MENTION] and I seem to be in a similar, quite bad situation. Tebor and I lost our IMEI numbers and SIM functions when restoring a TWRP backup...

I had CM13 up and running on my unlocked A2017G. The only issue I had was the sound distortion. I backupped everything with TWRP and installed a Dolby.zip mod which did not help a bit. I decided to roll-back and restore my TWRP backup, and that's when the trouble began. CM wouldn't boot anymore. Since then, my phone has lost Wi-Fi + Cellular. My SIM isn't even detected anymore. When i use

adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
Then
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2

My Wi-Fi is back and it does detect my SIM. However, IMEI shows up as "0000" and my phone doesn't connect to a network, even if it finds the available networks in the area.

I've a "efs1.emmc.win" and "efs1.emmc.win.md5" now for two backups. One from just before everything went wrong (the one I backed up just before I flashed the Dolby.zip, in a Cyanogenmod backup) and one from the day I used your tool to flash TWRP and then unlocked BL (stock B06 A2017G ROM).

I've tried restoring both backups with TWRP and then flashing either CM or Stock but when I do that, CM won't boot and the stock ROM doesn't even detect my SIM.

I'm a bit at a loss. I'm scared I took my chances too far and I'm going to have to send my phone back....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Yeah, don't ever do that. :(

I'm not familiar enough with the details of the axon7 to know exactly how to get the IMEI back (yet, anyway). And I'm not sure what would be in that backup file. If those backup files have your EFS data, it may be restore-able, but it would take some deep magic. If not, well, you're kind of stuck ... the IMEI doesn't seem to be printed on the outside of the device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Controllerboy:
Damn. If you can't do it, I'm not sure who can help me... I posted a seperate thread hoping someone has at least an idea.

I have my two IMEI codes, though. They're on a sticker on the back of my device. I didn't take it off. Is there anything you can do when yo you do have the codes?

Thanks again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Well, it's good you have your IMEI's. I don't know exactly what I can do. I'll have to investigate.

The first thing to do is examine your backup file and see if it looks like it matches an existing partition. It may be a simple matter of flashing it back to the proper place.

I have done some poking at the diagnostic mode on my device. I can talk to it. But the SPC seems to be set to something non-zero and I don't yet know how to find out what it is.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tennear:
Guys ... I'm getting ready to release a new version of the tool next week. It has better error reporting and I also have the Mac version that is working.

I did test on Win10 64-bit using the WinUSB driver installed by zadig. It works here. So I'm not sure what the issue is with folks running Windows. But maybe the new version will shed light on any errors.

EDIT: Note I'm using a Linux host. Mac and Windows are built and run inside a VirtualBox VM.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
jcadduono could probably explain where the Axon-7 stores it's IMEI information. Looking at his TWRP fstab file I would guess it's modemst1/modemst2/fsg/fsc.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist bs=262144
adb shell mke2fs -t ext4 /dev/block/bootdevice/by-name/persist

UPDATE: DO NOT ERASE FSG PARTITION UNLESS YOU HAVE A FULL BACKUP OF IT ALREADY

it is device specific and contains modem configurations that for whatever reason don't load on other devices of the same model.

it may have your IMEI and bluetooth address on it in some weird format i'm not familiar with.

run that while in TWRP, those are all caching partitions, none of them contain anything important.

this will cause the modem/gps/bt/wifi/all the firmware on your device to regenerate those partitions from scratch, no longer panicking at bad data.

all sensors will recalibrate as well.

you should gain full usage of your phone once again.

i've done it myself while working with other devices that have had similar corruption issues.

just did it now on my own axon 7 to confirm it for you. everything's fine.

should you continue to have issues, flash the B20 full OTA, B20->B27, and B27->B29 and run those commands again

corrupt sim cards are also a possibility, so consider trying yours in other devices to make sure
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tebor:
[MENTION=5672995]jcadduono[/MENTION]

I just tried these and still not connecting to data. As Controllerboy and myself both have A2017G's, do I try flashing the A2017U firmware as you mentioned?