yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 10  Questions & Answers] Paul Clem:
Restart the phone

I was having the same problem on my Honor 8, but a simple phone restart did the trick.
[Huawei Mate 10  Questions & Answers] Coreinsp:
Just restart you phone It happens after it being up for a long time a simple restart fixes it I hope they fixed that bug in Android 9.
[General Questions and Answers] MissLaniS:
I just got a new phone for Straight Talk. Only one I could afford right now. I got the LG Fiesta Lte. It has Android 7.0 on it. For the life of me, I can not figure out how to get the app drawer to show. I tried the long pressing on home screen then choosing home screen options, but then after that the only option that comes up is, HOME SCREEN & it is already checked, and there is no option to uncheck it or anything. I cant not figure out how to get to all my apps. I dont see an app icon or an app drawer icon or anything.. I cant even figure out how to see all the apps on the phone. Anyone know how to get the app drawer back or is there any other solution for getting an appo drawer on here?? Its annoying.

Thanks for your help guys!!
[General Questions and Answers] Tiqqy:
Apparently you might have EasyHome switched on.

Try this: Settings > Display > Home Screen > Tap on Home

https://www.androidcentral.com/using-easyhome-lg-g4

Hope that helps
[Sony Xperia M4 Aqua] Wolfus-IT:
I apologize already for my poor english :(

If your m4 aqua won't stay in fastboot mode (so it turns off after a few second), then you have to follow these steps :D​

1 Download the program from this link "flashtool.net/downloads_windows.php"

2 Install the program

- For steps 3 through 9, you can follow the guide for windows 8 on this page "flashtool.net/win8drivers.php"

With the images (even for those who have windows 10 if you need images to simplify your life ;), the steps are very similar)

3 Enter the computer settings -> Update and security -> Restore -> "Restart now" under the Advanced start section

4 The computer will reboot -> Troubleshoot -> Advanced options -> Startup settings -> Press "Restart"

5 After restarting another menu will appear, press 7 or F7 on the keyboard

6 The computer will now start

7 After entering the desktop, open the folder where the program was installed, enter the "drivers" folder and start the "Flashtool-drivers.exe" program

8 Select "Flashmode Drivers" and "Fastboot Drivers"

9 Follow the installer instructions until a window appears, where you will be asked if you want to install the drivers, press to install the drivers, and wait until you have finished installing all the drivers

I hope everything is clear and has helped someone :fingers-crossed: :p​
[Sony Xperia M4 Aqua] winXPHE:
https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/

https://mirrors.zzu.edu.cn/android/repository/platform-tools_r26.0.2-windows.zip

http://www.flashtool.net/downloads_windows_prev.php

https://developer.android.com/studio/run/win-usb.html

get boot.img variant from

https://xdaforums.com/m4-aqua/general/root-twrp-sony-xperia-m4-aqua-t3503369

get recovery twrp from

https://xdaforums.com/m4-aqua/development/stock-concept-ify-improved-stock-mm-rom-t3671104

when stuck on loading after twrp, hold down vol down and power keys and restart. will take a while to get to start.

then boot to recovery, install conceptify and then follow

https://xdaforums.com/showpost.php?p=78280260&postcount=552
[General Questions and Answers] Lobotom_:
Hi

Maybe you can help me.

I used my M808 2 years. In 2 days i can't call and sms and don't have internet when i have 3G or 4G. When i force 2G i can call and sms. In 3G i can see range but i cant call to anybody.

Do you have idea how i can fix it?

I done hard reset and nothing, I try my SIM card in other smartphone and there i had 4G ok.

Will Change rom help?
[General Questions and Answers] bigrammy:
This could be caused by a few things.

1. Hardware fault.

2. Your carrier (SIM Provider) switched to a none supported band or bands. The M808 does not support LTE band 20 (800mhz) which is common in Europe

Supported Network Bands:

(2G) GSM 850/900/1800/1900MHz

(3G) WCDMA 850/900/1900/2100MHz

(4G) FDD-LTE B1/B3/B7/B8/B28

3. APN settings although this would not affect voice calls

4. Your carrier Decided to block your phone by IMEI from using anything other than 2G and yes they do sometimes do this O2 did it to me some years ago now with absolutely no warning or reason given so I will never ever use them again the arrogant s**** :mad:

5. Duplicate IMEI someone is using a phone with the same IMEI as yours on the same network. This can cause all kinds of strange stuff to happen. Again happened to me when I restored the incorrect backup. Both mine and my sons phone ended up with the same IMEI . It took ages to work out what was going on with that one :eek:

I would suggest you first try another sim card from another provider that use's the supported bands for 4G (3UK) if in the UK it used to work fine on my Old M808.
[General Questions and Answers] Lobotom_:
I done some tests.

I put my sim card to other phone - everything is ok.

I put other provider sim card to my phone - only 2G is working properly.

I done flashing - no improvement.

Im afraid hardware fault.

Any more sugestions?
[General Questions and Answers] bigrammy:
Full Firmware Upgrade using SPFlashTool If that dont fix it then it's time for a new Phone see the original Infocus V5 M808 Thread for ROM s and tools.

https://xdaforums.com/general/device-reviews-and-information/infocus-v5-mt6753-5-2-fhd-2gb-ram-16gb-t3341297

MM ROM's and Recovery's https://xdaforums.com/showpost.php?p=67345310&postcount=182
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] carlosdys11:
Someone who has the OEMinfo of RNE-AL00C00
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
You can find it in this tool:

https://xdaforums.com/mate-10/huawe...development/hwota-huawei-mate10-lite-t3777115
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] SevenUp9:
As above. But I suggest a deep understanding of this phone's backing up from dead or you'll be stuck in a dead end (bootloop, I thought it was hard-bricked again - eRecovery not working, even fastboot status wasn't showing properly) just like I was. Be ready to download original ROM and HuRupdater. I had a problem with HWOTA8 where oeminfo was probably corrupt and system would not boot up, flashed oeminfo from HWOTA7 (through HWOTA8 ofc) and system booted up. eRecovery wasn't working before I reflashed whole system tho.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] carlosdys11:
how did you solve it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Just in case you want to use this tool for preparing the partition table for flashing some common sets of ROMs:

The The first Treble ROMs made by NFound splits 800MB of Vendor partition from the beginning of the data partition. You can do it using a Computer and flashing the EDL package or you can use this tool from TWRP.

The Unofficial LOS 15.1 20180810 splits 512MB of vendor partition from the end of the system partition. The new Unofficial LOS 16.0 ROMs requires a vendor partition using this scheme. The benefit of this configuration is that the user data is not formatted or modified and system partition is resized without losing any data.

In case you want to return to a previous non-treble rom, you just need to run this tool from TWRP and seamlessly remove the vendor partition.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
Thanks yet again oki, for all the great tools you bring us for our phones.

Question: If you were to choose, which vendor part version would you recommend people create to prepare for upcoming Treble releases, the 800 MB or the 512 version?

Also , since I & others already have the NFound method installed, is there a need/benefit to convert over to the other one?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Thanks, this is great!

Not mentioned in your Procedure: are there any prerequistes, such as having a specific ROM, TWRP, bootloader, or ??? already installed?

Can this be run from B35 Stock to then be 'Treble Ready'?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
The best configuration is splitting 512MB (more than enough) from the end of the system partition. That leaves 5.5GB for system, when usually it doesn't even reach 2GB. a 3GB system partition is considered large nowadays. 5.5GB is still overkill. I have even thought in creating a Treble A/B partitioning for seamless update. But let's first stabilize Treble A before thinking in more advanced configurations.

The only prerequisite for this tool is having TWRP. It actually can be used in any legacy ARM device, not only the Axon 7, to create the vendor partition from system or data.

You can run it with any bootstack, even the old Nougat or MM bootstacks. The tool is bootstack agnostic. However, there is no point on having a vendor partition with a ROM requiring an old Nougat or MM bootstack, since they don't use it. Treble ROMs are all compiled using the Oreo B12 bootstack, and they won't boot with any other bootstack. This tool only prepares the partition table, the bootstack is another thing you must prepare before flashing any ROM.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
Hi [MENTION=319057]Oki[/MENTION]

Thanks for your handful tool!

It states that it has found vendor partition before data partition (I had it installed with NFounds method)...

My question: Will deleting this vendor partition using your tool leave data as is or will it wipe the whole internal storage also?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
It will wipe data and internal storage since the split was done at the beginning of the userdata partition so it was easier to flash using the EDL method both in the 64 and 128GB Axon 7. Now with this tool there is no reason at all for splitting from the data partition. Those with the initial 800MB split will have to backup data and storage to recover those 800MB and transition to the 512MB vendor partition at the end of the system partition. I already did it so now I can go back and forth seamlessly without losing the internal storage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] roisuke:
Hello Oki, I'm planning on following the steps below to install the treblerized August build of los 15.1 and was wondering if your tool would make the process any easier or would it even be necessary? I'm currently on the non treble 7/23 build of 15.1. Also thanks for all your contributions to the Axon 7 community! :p
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Masterjuggler:
First, thanks Oki! This is a great addition to our tool set, and will make life much easier going back to stock.

I've been following the LOS threads and have been trying to keep up, so if these questions have been answered already please just point me in the right direction. There's a lot of information all over the place, and it's difficult to search for without already having a working understanding of it.

Now that we have a simple method of adding a vendor partition (acknowledging LOS having an already integrated treblerizer, but no return), are we now able to reliably flash standard GSIs? If not, what exactly is needed to make our phone compatible with standard GSIs?

The kernel still goes into the /boot, which would still be device-specific, so the way I understand it is that we still need the other device-specific stuff like DAC configs, which would then go into the /vendor? I take it this means the HALs (if that's what I'm talking about) are at a level above bootstack but below kernel?

If we were to go flashing GSIs now, would a lot of crap just be broken, or would it pretty much work save for the DAC? If broken, could we get it to just default to the SD820 integrated DAC? Are we (the xda community, developers, users, etc) able to make HALs that would accomplish getting audio to work properly in either case, or is this something that must be included in the ROM or kernel rather than /vendor?

If there is any interest, an FAQ on this might be a good idea, if one doesn't currently exist. We'd just need someone to maintain it. I'd be happy to do so, but obviously I'm currently terribly confused LOL, and definitely need to do a lot of required reading on this.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
LOS15.1 20180810 already creates the vendor partition, so no need for my tool for creating it. It is already an easy process when coming from a non-treble LOS15.1. In case you prefer to go back to the previous non-treble rom, then you will need PARTY. PARTY is also required to transition from the old 800MB vendor to the new location at the end of the system partition.

All the hardware specific drivers are in the Kernel, but the configuration files and libraries are in the vendor partition in a treble rom. GSI use the available libraries, but they must ask for those entry points. So if a Vendor partition doesn't provide the GSI with the standard entry points along with the configs, then the specific hardware won't work. In our case the DAC is critical since most of us purchased the Axon 7 instead of the OP3 just because of the amazing sound of this device. The Vendor partition is the key, but it all depends on the device tree and ported vendor blobs.

Probably the future will be a Treble ROM for the Axon supporting the standard Qualcomm devices and some kind of patches for the GSI so we could enjoy the excellent DAC. The best would be if ZTE release an Android Pie update for us the same way it is going to happen for the OP3.

You are very welcome to create answers or gather the answers in a central FAQ.

I have created this tool so the Treblerization of legacy devices could be easier and the Axon 7 could benefit of it too. This device has an amazing hardware configuration, the only problem is the software. It all depends on ZTE and the user base.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Masterjuggler:
So other than the DAC config, is there anything else broken or preventing us from flashing GSIs? Put another way, what else would we need to port/create for /vendor in order to properly run a GSI? I'm sure if we create a vendor partition and just flash a GSI, /vendor will still be empty and useless until we do something with it.

Also, for anyone who cares about semantics, I am saying "we" because I would at some point like to learn more and also contribute to these projects. I don't have much time for the foreseeable future due to college starting again, but we have to remember it's not like developers are a certain breed that do nothing but unpaid work for us. It's everyone's responsibility to keep development alive.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
So i flash this in twrp and can delete vendor partition?

---------- Post added at 06:44 AM ---------- Previous post was at 06:38 AM ----------

Well,after i flashed this... vendor is still here and twrp is unable to mount vendor...what to do now?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] samo_lego:
Hi!

Of course you deserve the THANKS word, so I would start with that ... :p

My question is; I am running the treblerized version of AEX 5.8, provided by NFound, so my vendor partition is 800 mb one. Is it recommended to flash the PARTY to make it smaller (512 mb) or is this one just good enough?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] taufikthexfader:
Dear [MENTION=319057]Oki[/MENTION], can i use this on any device? say i have an old xperia z ultra (togari) and i wanna trebelize it..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedWave31:
Is there ANY way this could be used to reduce the system partition to 2GB or 2.5GB like stated in another comment? And kill other ones?

- BT_Firmware : 1GB wasted

- Cache : 750mb wasted

- dev : 2GB wasted

- system : 4GB wasted

> 8GB that I can barely use, or that I should paste into, using root programs...

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
I should have been removed. Could you please run PARTY and at the end do not reboot, open the terminal and type:

cp /tmp/Party.log /sdcard/

Then boot to system and share or send to me the Party.log file that should be in the internal storage so I could see what happened.

Thanks

800 is good to go, there is no need to recover that space unless you need those 800MB returned to your internal storage.

It should work. But creating the vendor partition is just one step. Be aware that the developers should do the hard work of splitting the ROM files and configuration from a single system image to a vendor and a system image, along with the changes in the kernel of the rom.

BT_firmware is only 1MB, not 1GB

Cache is in the same disk than data so it can be added to the main storage with some backup and repartitioning. We can recreate another cache partition from the system partition.

Not sure what partition are you referring to as "dev". Devinfo is only 4KB and Devcfg is 128KB.

So far the only partitions we can use to increase the storage userdata partition are in the /dev/block/sda disk. This is the stock partition table:

Number Start (sector) End (sector) Size Code Name
1 6 7 8.0 KiB FFFF ssd
2 8 204807 800.0 MiB FFFF cache
3 204808 205063 1024.0 KiB FFFF misc
4 205064 205191 512.0 KiB FFFF keystore
5 205192 205223 128.0 KiB FFFF devcfg
6 205224 205255 128.0 KiB FFFF fbop
7 205256 205383 512.0 KiB FFFF frp
8 205384 205511 512.0 KiB FFFF cryptkey
9 205512 13944826 52.4 GiB 8300 userdata

As you can see only cache is there with enough space to consider it. The System disk is another interesting partition since the Treble A/B could be possible with some work:

Number Start (sector) End (sector) Size Code Name
1 6 133 512.0 KiB FFFF rpm
2 134 645 2.0 MiB FFFF tz
3 646 773 512.0 KiB FFFF hyp
4 774 1285 2.0 MiB FFFF fsg
5 1286 1289 16.0 KiB FFFF sec
6 1290 1417 512.0 KiB FFFF pmic
7 1418 25737 95.0 MiB 0700 modem
8 25738 29833 16.0 MiB FFFF dsp
9 29834 30089 1024.0 KiB FFFF dip
10 30090 38281 32.0 MiB FFFF mdtp
11 38282 38537 1024.0 KiB FFFF aboot
12 38538 54921 64.0 MiB FFFF boot
13 54922 1627785 6.0 GiB 8300 system
14 1627786 1644169 64.0 MiB FFFF recovery
15 1644170 1644170 4.0 KiB FFFF devinfo
16 1644171 1644426 1024.0 KiB FFFF bluetooth
17 1644427 1644458 128.0 KiB FFFF lksecapp
18 1644459 1644522 256.0 KiB FFFF keymaster
19 1644523 1644586 256.0 KiB FFFF cmnlib
20 1644587 1644650 256.0 KiB FFFF cmnlib64
21 1644651 1644714 256.0 KiB FFFF apdp
22 1644715 1644778 256.0 KiB FFFF msadp
23 1644779 1644779 4.0 KiB FFFF dpo
24 1644780 1653135 32.6 MiB FFFF splash
25 1653136 1663375 40.0 MiB FFFF echarge
26 1663376 1663887 2.0 MiB FFFF sti
27 1663888 1663994 428.0 KiB FFFF last_parti

We have a total of 6.5GB in the /dev/block/sde disk that could be repartitioned to handle the Treble A/B configuration for seamless update in our Axon 7.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedWave31:
This might be coming from an A2017 or A2017U. This is what appears on a A2017G:

Here is what I see using a root file explorer:

It doesnt seems to be SYMLINKS, since I only have a 52GB DATA partition, which would account for those 8GB missing + 2-4GB of system and a bit more.

Is there any way I could use the tool to modify partitions, or is that in ROMs as well?

- I know that If I go this route, I'll probably have to modify ZIP files for the rest of the device lifetime, but I'm ok with this...

- At the time of the Galaxy S2 (i9100) and HP Touchpad, we ended up removing the partition size files in ROMs and getting much, much more space.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
i did a stock restore trough EDL miflash.But i used party zip when i had gsi firmware installed on system,and i did use remove vendor option,i think that was a problem..i had to full clean phone first i think
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
The system reports logical sizes. A partition can appear to the system with a virtual size, the same way a VHD drive can have virtually 200TB when the image file is only 100MB in size, or compressed drivers storing virtually more space than the physical available space. The physical 1MB BT partition holds a vfat filesystem that wraps a 72MB firmware image (3 files) in a virtual 1GB partition. But the filesystem image is only 1MB.

dev is the device mount, it is a region in memory for communicating with the kernel through the fsnodes.

The other entries are mount points, some of them virtual or not corresponding to a physical partition.

Bottom line, that app provides you not with the physical partitioning of the device, but with a list of logical mount points and logical/virtual sizes.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
No, it should work in any case. Please provide me with the log file so I could figure out what you have and why it didn't worked for you. It will also helps others. I am suspecting you could have 2 vendor partitions in two different disks, so when you remove one, the software will still detect the other one in the next run. This is just an hypothesis I would like to clarify. Since you already flashed an EDL package on top, then there is no way to see it now.

Please, if you or someone else encounter this situation, please let me know.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Masterjuggler:
Also, as far as encryption goes, as it stands the Orden/Udev treble method is able to encrypt where NFound's method is not. Does anyone know if this due to the ROM itself (LOS vs NFound stuff), or how the vendor partition is created?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
It is a kernel/vendor stuff since it depends on the bootstack. GSI should be encryption agnostic.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Thanks OKI! This is an incredible achievement! Hope this will help us a lot! Only question is, if I understand correctly, we can easily get and remove the vendor partition. But that is still not worth much without moving everything not part of a GSI into it, right? So only step 1 is done with this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
HI [MENTION=319057]Oki[/MENTION], im on NFound RR non-treble July Build, if i were to use ur PARTY tool for the 512mb option, there would be no Data loss from Data partition and will i be able to Flash RR Treble (August)? or is NFOUND roms depended on Vendor being part of Data partition?

Also my current Bootstack is the universal bootstack from LOS 15
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
This tool allow the creation and removal of an empty vendor partition. It adapts the partition table so it could handle ROMs requiring the vendor partition. The same way it can remove the vendor partition and recover that space so you could flash also non-treble roms that require 6GB system partition.

Earlier Treble ROMs from [MENTION=5492451]NFound[/MENTION] worked only in 800MB before the userdata partition. Nonetheles all the recent ROMs (Pie, EAX, RR, Havoc) are compatible with any vendor configuration. So, the default configuration splitting 512MB from the end of the vendor partition is the recommended way. By doing so, you will be able to try a dirty flash to the latest RR rom he released and you won't lose your data. In any case a backup is always recommended!!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
thanks for the awesome tool [MENTION=319057]Oki[/MENTION], i tried to create vendor partition on lg stylo 2 plus running lineage 15.1, i get this error at the step where it creates the vendor partition [ updater process ended with error : 2 ], recovery log https://hastebin.com/exukoyeduc.sql any ideas ?