yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dragon502:
That is some prerequisite I would write in the installation instruction.

Ah, ok. They are device specific ROMs repackaged to fit in "treblerized" phones.

Nope, I wanna understand what is the difference between a full EDL and a boostack zip. Well, I have found that they contain a stock image.

Thank you for the enlightment.

As a final update everything I care about seems to be working (DAC, baddar kernel, Ainur narsil, usb debugging and night light).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct.

Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7.

You can't take any ROM and "repackage" it, you have to build it specifically for a certain phone. then, it gets whatever it needs to run on it

The bootstack zip has some files like fastboot, the boot stuff like boot image and everything that supports it, modem image, etc.

A full EDL zip is the whole damn system, so you also get stock system and the recovery which is 90% of the full edl zip
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kirknado18:
This rom does not boot on my axon a2017u bootloops
[OnePlus 6T  Questions & Answers] dismembered3po:
When one unlocks the bootloader on an Android device, the device then shows a "Bootloader Unlocked" warning splash screen. This is a general Android thing, not specific to the OP6T.

On the Moto Z2 Force (my previous phone), there was a way to hide that warning screen by flashing logo.bin. See thread:

https://xdaforums.com/z2-force/development/remove-bootloader-unlocked-warning-t3702353

I have no idea if an approach like this would be relevant to our OP6T, but wondered if there could be something similar.

Thanks
[OnePlus 6T  Questions & Answers] pbergonzi:
Intriguing, but idunno.
[OnePlus 6T  Questions & Answers] Dr. Mario:
Doubtful. Logo.bin is encrypted in most recent Android phones because the locked bootloader exists for a reason other than stabbing the customers in the back. So, I am confident that logo.bin mods will not work, since there are some machine codes embedded into the image file, meant for the phone to check if it's legit or not.
[OnePlus 6T  Questions & Answers] Striatum_bdr:
This quest is vane.

All is hardcoded and all devs that tried to hack the files failed.

The only question in fact is: what is your problem with this screen? It lasts 5 secs and only when your reboot....

There are many more crucial things to deal with
[OnePlus 6T  Questions & Answers] jestyr8:
There may be more crucial things to deal with, and yes it's only showing for a few seconds, but that doesn't mean it's not important to the OP. It annoys the crap out of me as well but will admit I don't have the knowledge to even attempt looking for a solution. Just because you see it as nothing more than a minor annoyance doesn't invalidate his or others annoyance level over it. I'd love to see a solution to it but am aware one is probably not coming.
[OnePlus 6T  Questions & Answers] dismembered3po:
My concerns about it are twofold:

1) If someone reboots my device without my knowing it, it's a dead giveaway that...well...the device is physically attackable.

2) When I inevitably pass this phone down to my wife, it will annoy her. Also, she has far worse opsec than I do.
[OnePlus 6T  Questions & Answers] Dr. Mario:
Also, on some phones, possibly this one (OnePlus 6T), the logo.bin image file is deeply embedded inside the second stage UEFI bootloader (aboot), meaning if you try, you will definitely brick it, since it obviously will cause the bootloader to either be quite upset that the logo.bin now no longer pass the cryptography checks, or worse, be completely corrupted.
[OnePlus 6T  Questions & Answers] Striatum_bdr:
1) that's exactly why Google is against 'root' and why many manufacturers forbid bootloader unlock.... And why phones are encrypted

And why nearly all phone that permit bootloader unlock have this type of screen

Far less annoying than the warning that never stops in your car if your don't put your belt....
[OnePlus 6T  Questions & Answers] Dr. Mario:
Actually, Google don't really care about rooting nowadays (they allow you to unlock the Google Store version of Google Pixel phones' bootloaders - if they are so against rooting, why do they give you a choice to unlock the bootloader), but they're more concerned about whether root agents are being hijacked (which is why Magisk have Superuser lockout protection, and I use it to only authorize the legit apps), and what the hackers (and cops hellbent on violating the privacy rights laws) would find once they get ahold of the Linux device block handles (like /dev/sda0 for instance) leading to the SD cards and embedded SSD.

So Google have had a right reason to encrypt the whole SSD; it's for your own protection and privacy, something you should be worried about especially after a few high profile security breaches.

In the end, it's never about rooting, it's always about the ramifications of if someone have a hold of your phone. Of course the argument against rooting is useless nowadays anyhow because when you unlock the bootloader, the phone automatically wipes itself clean leaving nothing for the suspects to try and steal (as the bootloader also do perform TRIM wipe too to make sure there's nothing left behind).
[OnePlus 6T  Questions & Answers] dismembered3po:
Google can't be said to be "against root," really. We continually see phones released with bootloader unlock allowed natively. I mean, all of Google's own phones - Pixels, Nexuses (Nexi?) - have permitted oem unlocking since basically ever (Ok, not sure about the Galaxy Nexus). All of the OnePlus phones have permitted it (save the new T-mobile 6t). It's mostly the CARRIERS who forbid it because they have a vested interest in making sure you can't take your phone to another network. Oh...and Samsung.

Full disk encryption is about user privacy, and I can't stress enough how important it is, but it's a separate argument.

I understand the underlying motivation for employing a warning screen like this. For someone who doesn't understand all this stuff, having a blatant warning is beneficial because they will know their device has been tampered with. On the other hand, I'm fully aware of the risks involved with unlocking, rooting, etc. I choose to do it because I'm using it to enhance the functionality and security of the phone for my very specific use-cases. That said, if I could mitigate one additional threat by not broadcasting to everyone that my bootloader is unlocked, maybe the attacker moves on to an easier target.

Whether you like it or not isn't really important to my motivation for asking these questions.
[OnePlus 6T  Questions & Answers] Striatum_bdr:
Those questions are asked since OnePlus 1, years ago.... Answer will always be the same. Impossible to get rid of the warning screen
[OnePlus 6T  Questions & Answers] OhioYJ:
People keep saying that, I don't buy it. It's been done on too many devices when someone has been determined.

Here is the Nexus 5X thread, it had some details about how it's done on that device. Perhaps it would be useful or provide some ideas?
[OnePlus 6T  Questions & Answers] Dr. Mario:
The problem is, Nexus 5X's bootloader use different disk partition compared to OnePlus 6T's, and OnePlus made a change to how the bootloader protect itself ever since OnePlus 5T phone was shown to be vulnerable to the bootloader console and UEFI payload partition attacks.

So don't be surprised if you attempted the Nexus 5X boot splash trick on the OnePlus 6T's bootloader, only to have to use the Qualcomm Snapdragon processor tool to get it back to life.
[OnePlus 6T  Questions & Answers] Dr. Mario:
After a little bit of research, it's kind of possible to install a modified UEFI payload bootloader (abl / aboot) on the Snapdragon 845 phones like our OnePlus 6T. It will be tricky because of the UEFI XBL bootloader agent which is very strict about the file size / cryptography checks even if *it* is technically already unlocked, it still acts like a locked bootloader for a good reason.

TL:DR, it is possible to replace the bootloader unlocked warning splash screen on the OnePlus 6T, but the encryption and UEFI security check will stop you short of attaining your hacking goal.
[Huawei Mate 20 X Questions & Answers] Yogi.G:
Installed new update on EVR-AL00

uninstalled hiboard and installed google... google feed is not starting up !!

hiboard has been un-installed and replaced with google feed but, it just not starting up... right swipe is'nt happening...

any one else has this issues ???

anyway to start it manually ?

any updated ROM for EVR-AL00 ?? using dload method
[Huawei Mate 20 X Questions & Answers] tuddu:
If you have uninstalled Hiboard, then installed Google feed and THEN update the firmware, well the Google feed is gone. And Hiboard as well.

Or better....Hiboard has been disabled only. I assume you have "uninstalled" (disabled) Hisuite via ADB commands (usb debug enabled). Then installed Google feed and everything was fine.

But, I think, then you update the firmware via OTA and both are gone.

If this is the case, then you have to re-enable Hisuite (via ADB commands) and then re-do the procedure to replace it with Google feed.

And you have to do this every time you perform a firmware update (OTA)....

Inviato dal mio ONEPLUS A6010 utilizzando Tapatalk

---------- Post added at 12:56 PM ---------- Previous post was at 12:47 PM ----------

Here you can find a guide in order to re-enable Hiboard (as I did too): https://www.xda-developers.com/disable-system-app-bloatware-android/

Inviato dal mio ONEPLUS A6010 utilizzando Tapatalk
[Huawei Mate 20 X Questions & Answers] Yogi.G:
thank you for the reply... and interest...

I have factory reset the device now... after updating to 9.1.0.127(C00E127R2P1)

and Like a new device, I started configuring & installing the google apps.

then uninstalled the hiboard, and I can see the google feed option in "home screen settings" I have switched ON the google feed.

but nothings happening, google feed doesn't start.

whenever I restart the phone, the google feed gets auto switched off in the "Home screen settings"

:crying::crying::crying:

also.

I used the Dload method to update my phone... now the build number has been changed.

my build numbers changed ( from R1P17 to R2P1 )

PREVIOUS build Number = 9.1.0.123(C00E121R1P17)

NOW build Number = 9.1.0.127(C00E127R2P1) ( after DLOAD method of updating )

I tried to use the System recovery via Hi-suit to fall back to 9.1.0.123 and it has been downloading ( 9.1.0.123 "R2P1" ) which is different build... but reverting back to 9.1.0.123 failed as not compatible.

so I am now running at 9.1.0.127(C00E127R2P1) everything is fine except the Google feed. which I tried a hard reset and reconfiguring the phone but unlucky it is not working !!

except google feed, I don't find any other issues. Yes, the build number also changed...
[Huawei Mate 20 X Questions & Answers] Yogi.G:
---------- Post added at 12:56 PM ---------- Previous post was at 12:47 PM ----------

[/COLOR]Here you can find a guide in order to re-enable Hiboard (as I did too): https://www.xda-developers.com/disable-system-app-bloatware-android/

Inviato dal mio ONEPLUS A6010 utilizzando Tapatalk[/QUOTE]

thank you so much, looks promising...

I will work / try on that...
[Huawei Mate 20 X Questions & Answers] Yogi.G:
---------- Post added at 12:56 PM ---------- Previous post was at 12:47 PM ----------

[/COLOR]Here you can find a guide in order to re-enable Hiboard (as I did too): https://www.xda-developers.com/disable-system-app-bloatware-android/

Inviato dal mio ONEPLUS A6010 utilizzando Tapatalk[/QUOTE]

I have Re-installed the HI-board and Disabled it and installed the google app.. still it doesn't work....

:crying::crying::crying::crying::crying:

any other options ???
[Android General] carpboy:
I am at the point of having myT-Mobile 935T fixed for a bad charging port and new battery, but I got to thinking of replacing it with a flat or edge Exynos. Reason is that I need to be rooted and the only root method (eng kernel) is horrific and I am craving having a phone that actually works with some speed. I am sick of the lag.

I am wondering how difficult it would be to use an F version and get VoLTE and wifi calling on it? How about video calling from the dialer?

Finally, can a working CA be enabled on this?

If any of those are not possible but if someone is using the phone anyway, would someone mind saying how they find their day-to-day phone usage to be without the feature in question?

If possible, any good links would be appreciated.

Thanks.
[Xiaomi Poco F1 Questions & Answers] hanseatic2:
Hi everyone,

I unlocked the bootloader with XiaoMiTool V2 (I have no Windows computer) and flashed TWRP with it, and then the current crDroid to check it out.

After that, I installed Lineage for MicroG with the XiaoMiTool V2, but this time, Lineage did not boot. (Probably not a great idea, to use this tool to exchange one custom ROM to another.)

I tried to sideload it manually, following these installation instructions without success:

https://wiki.lineageos.org/devices/beryllium/install

The Poco drops into fastboot after a wile after turning it on, but I can boot into TWRP (Official 3.3.0-0) with Vol+ & Power

What are the next steps to diagnose or reach normal installation behaviour?

Thnx for any suggestions
[Xiaomi Poco F1 Questions & Answers] suritsuwal:
tried flashing crdroid again?
[Xiaomi Poco F1 Questions & Answers] hanseatic2:
That seemed to work. Thnx. I am back on crDroid for now.

I suspect the issue with data encryption settings, but had not the chance to reproduce the prob or find a proper way.

I'll try to figure out how to enable signature spoofing and run microG on crDroid now.
[Xiaomi Poco F1 Questions & Answers] suritsuwal:
:good:
[LG V30 Questions & Answers] DTexUS:
So my lg v30 will connect to LTE on extremely rare cases, any other time it will not. I've been monitoring signal and events through Network Guru. According to it my LTE has a problem attaching. Whatever it is that means. So when it does connect to LTE and I move out of range of one tower, I get Tracking Area Update Failure. What could be causing this? How can I fix it. I've set the APN to the best of my ability, but currently I get message APN settings not available for this user. I can still add an APN and save it, but I have no idea if it actually saves cause I can't view the list of APNs. However even before this APN message I had these problems and I knew for a fact the APN was correct. Any help is appreciated!
[LG V30 Questions & Answers] ChazzMatt:
What variant do you have

What firmware are you on

What carrier are you using
[LG V30 Questions & Answers] DTexUS:
At&t

I am on lineage is

I am using google fi, but since is not fully fi featured its basicay T-Mobile
[LG V30 Questions & Answers] ChazzMatt:
So you have H931 converted to US998 and then with Lineage custom ROM installed.

But you are limited to T-Mobile coverage.

Do you live in good T-Mobile area? For instance my mother doesn't. There's no T-Mobile towers near her.

If you are in a good T-Mobile area, you have two options:

1) Ask in Lineage custom ROM thread how to edit/create APN.

2) For test purposes, sign up for cheap T-Mobile MVNO like Mint to see if you get better "T-Mobile" LTE signal. You're only using T-Mobile anyway... First sign up and get "new" phone number just to get a Mint SIM card for test purposes. If you like it, then port your real phone number over and let the "test" phone account die (it's prepaid, so not much money).

Or any T-MOBILE MVNO which allows you to "Bring Your Own Phone".
[LG V30 Questions & Answers] DTexUS:
I have tried many different carriers, all the same no LTE but gsm/edge works fine. Today I got to my jobs workshop and LTE started working, but as soon as I got into the town I was working in I lost it, LTE attach failure, or Tracking update failure. I'll see what I can do on the APN side of things. But do you have any information as to why it could get LTE sometimes and then other times the LTE attach failure comes up? At this point I'm likely just gonna get a fi compatible phone (Edit: one that has the auto network switching, the v30 is supported just will only work on T-Mobile towers), but just for learning's sake I'd love to figure this out. I looked at the coverage map for T-Mobile and I appear to be in a good area, and both the shop and the town mentioned above seem to be as well. Its almost as if the phone struggles to switch between towers. (I'm no service expert)
[Samsung Galaxy S10 5G Questions & Answers] floor51:
When I enable "Detect Suspicious Networks" in the advanced WiFi settings on the S10 5G, I begin to see fake looking APs being sent out in the WiFi probe requests.

I suspect that these are being added to my trusted WiFi AP list, though hidden. I've found the following logs which correlate with the probe requests. You can see the addition and removal of the random looking SSIDs, and that auto reconnect is set to 1. These don't appear in the list of trusted APs in the settings app, but presumably this is what they are:

2019-08-02T19:01:41.309 - addOrUpdateNetworkInternal: added/updated config. netId=346 configKey="n72n3pp96d52317knpj"NONE uid=1000 name=android.uid.system:1000 vendorAP=false hiddenSSID=true isRecommended=false autoReconnect=1

2019-08-02T21:18:46.461 - removeNetworkInternal: removed config. netId=346 configKey="n72n3pp96d52317knpj"NONE vendorAP=false hiddenSSID=true autoReconnect=1

2019-08-02T21:18:47.081 - addOrUpdateNetworkInternal: added/updated config. netId=348 configKey="agel0q7ee9ctgp0mc"NONE uid=1000 name=android.uid.system:1000 vendorAP=false hiddenSSID=true isRecommended=false autoReconnect=1

2019-08-02T23:29:52.752 - removeNetworkInternal: removed config. netId=348 configKey="agel0q7ee9ctgp0mc"NONE vendorAP=false hiddenSSID=true autoReconnect=1

2019-08-02T23:29:52.801 - addOrUpdateNetworkInternal: added/updated config. netId=350 configKey="c6j3wk75kaih66v"NONE uid=1000 name=android.uid.system:1000 vendorAP=false hiddenSSID=true isRecommended=false autoReconnect=1

Can anyone else corroborate this behaviour?

I used the following to find the logs:

adb shell dumpsys wifi
[8525, TyTN, MDA Vario II, JasJam ROM Development] mikehippe:
I just got a new WRT110 Lynksis router and when I try to connect to WiFi using WPA or WPA2, the "the key is automatically provided" box is checked and greyed out so I can't uncheck it and enter the network key to connect. I am able to uncheck this box if I choose WEP, enter the network key, and connect no problem. Any help would be greatly appreciated.
[Android Q&A, Help & Troubleshooting] Striker98:
[/HIDE][/STRIKE]Hi All ,,,

Last week i bought a used phone galaxy S7 G930FD(D is refering to duos i quess). when i dialed *#06# the first IMEI was okay but the second one was nulled, i never thought that is a problem before buying the phone.

The problem started when i flashed super su root through recovery, device rooted successfully but the phone could not connect to my carrier(634 01) network not available:(, i searched the web and i found this solution https://xdaforums.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516

I downloaded the files as mentioned in the post, when i got to flashing the combination file with odin, i booted the phone into download mode only to find out the G930S written on the top left of the screen as the product name, but in settings>about device the phone name was G930FD :confused: . Now i think that my phone is actually G930S and the guy who used the phone before me tried to make it dual sim by installing G930FD firmware, and the brick came when i flashed G930FD super su root on G930S device ? if my device is indeed G930S can i use G930FD combination file and firmware to fix the problem as mentioned in the post https://xdaforums.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 ?? or i misunderstood something ?

HOW can i SOLVE this ???? and thanks in advance.

Edit: I found a solution, see reply below.
[Android Q&A, Help & Troubleshooting] Striker98:
SOLUTION:

Finally i solved it!! know i can say that i have a phone not just a smart device.

I did a little reasersh until i found this Great software: Samsung Pro Z3X Tool without box at this site: https://www.gadgetsdr.com/2018/06/download-z3x-29-5-samsung-tool-pro/

It has a lot of features, i tried the Patch Cirtificate(Network repair) option and it did the trick ! wow im so delighted:laugh:, but the thing is it didn't work when i set the model to G930FD but when i made it G930S it worked! this tool even has a dual sim setting so you can make your phone dual sim easily thanks to Z3X Team.
[LG V35 Guides, News, & Discussion] X-Nemesis:
So I've just recovered my phone from my 1st attempt at updating to Pie on my unlocked AT&T v35.

But I'm left wondering if the process for updating from Oreo to Pie is somehow different than when I successfully updated from Marshmallow to Oreo.

The process I thought was:

1. Put phone in download mode

2. Connect phone to pc

3. Run the Modified version of LGUP

4. Select your ULM KDZ choice (any of the three will do)

5. Select Upgrade

6. Flash phone

Are any of these steps incorrect and should step 5 be Refurbish instead of Upgrade?
[LG V35 Guides, News, & Discussion] Shawnashley:
I used upgrade, when going from ULM 8.0 to ULM 9.0. I would assume you would use refurbish if going from stock to another firmware. Of course assumptions aren't really reliable.
[LG V35 Guides, News, & Discussion] MorningStarGG:
I've been trying to figure out if I should do UPGRADE or REFURBISH as well.

I found this: https://xdaforums.com/lg-v30/how-to/guide-how-to-upgrade-downgrade-restore-t3738917

Says REFURBISH wipes user data, UPGRADE does not. If moving from one image say from AT&T, to the Unlocked firmware I'd assume you want REFURBISH.
[LG V35 Guides, News, & Discussion] X-Nemesis:
So since I used refurbish to go to the ulm software from 7 to 8, do I still need to refurbish going to any of the ulm pie variants?
[LG V35 Guides, News, & Discussion] X-Nemesis:
That's what threw me for a loop on my first attempt. Since I'd successfully upgrade from the AT&T 7.0 firmware to I believe the Amazon 8.0 ULM firmware without issues, I thought the process would be the same going to 9.0. But I ran the upgrade through LGUP which was the modified version, and it crashed at 74% and sent me down a wonderful rabbits hole of brickage.
[LG V35 Guides, News, & Discussion] Neophy:
I don't understand how were you on Marshmallow before flashing to Oreo. I'm pretty sure the the V35 launched on Oreo 8.0. But I'm also looking for a way to get from Oreo to Pie on ULM kdz.

I went from AWM12k to ULM10i choosing REFURB and all went well (I followed xatokk's post on the lgV35 subreddit).

When I try to get from ULM10i to ULM20d (Pie .kdz) I guess I only have to drag ULM20d kdz in LGUP window?

I just want to make sure that's not how you bricked your phone before I try REFURB from ULM10i to ULM20d

Any advice would help, I'm a noob at this.
[LG V35 Guides, News, & Discussion] cmrntnnr:
FWIW, partition DL worked fine going first from AT&T firmware to Oreo ULM and then again to Pie. Sadly I had to set up the phone again.
[LG V35 Guides, News, & Discussion] X-Nemesis:
Sorry, Brainfart, I was completely out to lunch on that. I wanted to flash the latest available security update, but since I'm in Canada I could never get that from AT&T so I had to find a way to flash it and that led me to XDA and the whole LGUP process. So you were correct on that, and I did flash the Amazon 8.0 KDZ I believe without issue.

My brick happened when using the Amazon pie KDZ and using the same Upgrade process in LGUP. The update got to 74% and then crashed. I then tried to run the refurbish option but that crashed as well so by that time, my phone was beyond my knowledge of how to fix it