yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Lannig:
Sorry rhn19 but you're wrong. The stock recovery won't flash a zip file that isn't signed by the manufacturer or rebrander. You

do

need TWRP to flash Magisk.

Building TWRP by yourself is a job for advanced users. I'm still struggling with this myself and I'm a Unix system administrator who compiled his first Linux kernel in the mid 90s... it requires solid knowledge of the process of building Android from source code and good control of all Linux development tools.

I'm surprised that the stock firmware can't be found. I had no problem whatsoever to find it for my Z5 and M5. Have you searched hard enough?

EDIT: it's not there on the Leagoo Malaysia website which usually is a good source for Leagoo phones firmware: http://www.leagoo.com.my/support/firmware/

It might appear soon though.

Needrom has it (from a reputable poster): https://www.needrom.com/download/leagoo-t5c/

Of course this isn't 100% guaranteed as usual on Needrom, but looks good to me.
[General Questions and Answers] UglyStuff:
Hi,

I went to Needrom, and indeed, the ROM they offer for download is more recent than the one I have (is it an international ROM? I don't know; after all, I need to be able to use my device in France, or at least in English for the UI, with all the right LTE frequencies for France).

I've also read the comments, and I've noted that most posters were from Europe (I saw Italian flags, along with people posting from Russia, Sweden, Austria, etc...). All are worried about this new ROM containing the same Trojan MalwareBytes found on my device, and since the version of the UI seems to be the same (2.1), I suppose this new ROM only adds the latest security updates from Android, but isn't devoid of the malicious payload mine already has.

I think I'm going to register to this website and download this new ROM anyway. In the comment section, someone posted a video on how to upgrade other than via OTA, so this may help too, but if the Trojan that's in my current ROM is still in the new one (and I don't see any reason why it shouldn't, alas), then what's the point?

As for what rhn19 suggested, I don't think I'm quite ready to do that: I don't have a Linux machine handy, but using one in a VM in VirtualBox would be an option, provided I manage to solve the issues I've always had with the way VB deals with the use of USB ports on the host OS by the guest OS...

I'll keep that under advisement, of course, but my poor knowledge of Android makes it difficult for me to fully grasp the nuts-and-bolts of this operation.
[General Questions and Answers] rhn19:
U can change the signature of the zip, even from windows. The only problem that might occur is the locked boot loader and when i searched google for this device, the results were very unpromising. So, sorry for my phrasing but you should have checked before buying this device.:crying:.

Also, building TWRP from scratch is very hard but building a simple recovery like cwm minimal is not that hard you just need to have the source code for it.

I mostly use Samsung devices for which you can use the recovery.img from Odin and then modify it to suit your needs. Thats what i did for a Old crappy 2.6 Android samsung phone of mine and it was pretty straight forward.

This is the guide i used:

[youtube]-MkAsacu9_M[/youtube]

And

[youtube]rFnG7fso9HE[/youtube]

See if it helps!
[General Questions and Answers] UglyStuff:
I'm sorry, but this seems way above my level of competence when it comes to Android, and like I said earlier, I absolutely need this phone to work. In other words, I can't risk to brick it.

I've checked in the Developer Options, though, and the bootloader can be unlocked. As a matter of fact, it IS unlocked at the moment.

I have a question regarding a possible upgrade from the ROM I'd download from Needrom: my phone has USB OTG, but I don't have any microSD card handy. Can I park the new ROM on a USB drive, and uncompress it from there onto the phone, or is OTG disabled when the phone is in Recovery Mode?
[General Questions and Answers] rhn19:
Twrp supports OTG. Don't know about your phone's recovery.
[General Questions and Answers] Lannig:
[MENTION=6638579]rhn19[/MENTION]: No. Putting a self-signed signature on a zip won't help. Most if not all stock recoveries check that it is signed using the private key of the manufacturer or rebrander and will reject any other signature. Try it.

[MENTION=8914166]UglyStuff[/MENTION]: another approach would be to modify the system image that comes with the firmware downloaded from Needrom or another source to remove the crapware before flashing it. This isn't too hard on Mediatek devices, I've done it already. Well, unless the device has dm-verify enabled in the boot image which makes the whole thing much more difficult.

However this is a Spreadtrum-based device. I know next to nothing about the format of they firmwares, whether there is any kind of integrity check done by the flashing tool that would reject a modified image or not

Your best bet probably is that someone comes up with a cleaned firmware and makes it available...

---------- Post added at 11:52 AM ---------- Previous post was at 11:47 AM ----------

I think you're misled. AFAIK flashing is done using Spreatrum's "ResearchDownload" tool

from Windows

with the phone connected over USB. Meaning that you don't need to send the firmware file to your phone. It stays on your PC, the phone is passive during the flash operation. It works pretty much the same as Mediatek's SP Flash Tool or Qualcomm's QFIL
[General Questions and Answers] rhn19:
[MENTION=4555170]Lannig[/MENTION] Will try, BTW thanks for the info, didn't know this. Because on my Samsung device once Knox was void, it had an option to skip a lot of checks like zip signature via Odin.

For the firmware part i found literally no info on Google. So, i am assuming there is not much you can do unless you can read from a decompiled source code.
[General Questions and Answers] Lannig:
You're mixing two very different things: flashing via Odin (from a Windows PC, then) and flashing from the built-in recovery of the smartphone itself.

I'm not sure what kind of integrity checks Odin does, I'm not a Samsung specialist, but I know for sure that apart from some very rare exceptions, all stock recoveries accept only zips signed with a recognized signature (manufacturer, OEM etc.)

I'll try having a quick look at that firmware from Needrom, see if there's a chance a modified boot image could be built then flashed back to the T5C using Phhusson's toolkit. Give me a few days.
[General Questions and Answers] UglyStuff:
OK, that would be really nice of you, though there's no hurry: the phone performs OK, and I'll just have to be careful with whatever personal data I entrust it with.

FWIW, I did unzip the compressed ROM I downloaded from Needrom, but I can't get inside the .pac package. I thought it was some kind of compressed format, but that's not the case.

Thanks again for your help!
[General Questions and Answers] UglyStuff:
PROBLEM SOLVED!!!

I made another attempt with ADB (turned out I was trying to run the adb.exe from the wrong location; I hadn't actually installed it on my PC... I know, I know, I'm a noob...), and finally managed to get rid of the whole launcher, Sujet, along with the Trojan it contained.

MalwareBytes confirmed my phone is now clean.

Thanks, all, for your input, help, and time!
[General Questions and Answers] jubei23:
hi! could you explain in more detail how you solved the problem with ADB (...cannot change component state for com.leagoo.launcher3...)? thanks a lot!!
[General Questions and Answers] UglyStuff:
Hi,

I did as suggested by a fellow forum member: ran ADB from an elevated command line, typed " adb shell pm disable com.leagoo.launcher3 -k -user 0" (no quotes), hit Enter, wait a few seconds, and got back to the prompt, which meant the operation was successful.

I didn't exactly get rid of Sujet, Leagoo's application launcher (I don't think you can do that without rooting the phone, which I'm not sure is possible at the moment), but I fully disabled it, and MalwareBytes later told me my phone was clean, which is understandable, given that Sujet wasn't loaded in memory.

Another way to get a clean ROM is to download and flash the latest available from Needrom: https://www.needrom.com/download/leagoo-t5c/

(You need to register first, but it's free and real quick)

Also download the flashing tool, it's the latest version, and it works flawlessly; my phone currently runs this ROM, and it is indeed clean.
[General Questions and Answers] tarinka:
I have same problem with ulefone be pure lite, try too root with kongroot but cant root. Any sugestion ?
[General Questions and Answers] UglyStuff:
I'd avoid KingRoot if I were you, because it has a bad reputation. It does a lot of things behind the scenes that aren't completely kosher, and opens a lot vulnerabilities on your device.

I suppose your best course of action is to back up your personal data (photos, music, etc... but NO APPS) on a USB drive, then perform a factory reset.

After that, plug your USB drive on a PC and scan the content to make sure that some unwanted programs didn't hide there, and transfer it back onto your device. Then you can reinstall your apps, from the Google Play Store, not via some .apk website where quality control isn't always optimal...
[General Questions and Answers] tarinka:
I try several factory reset, dont work, every time is coming back. Install eset for mobile scan, recognize virus , uninstall over eset but coming back again. Try root, cant root.
[Moto G4 Plus Questions & Answers] jadeilson777:
to be able to revive but to flash the December rom stock of error
[Moto G4 Plus Questions & Answers] echo92:
What errors are you getting? Which stock firmware version are you getting these errors with?

What device do you have and how did you hard brick your device? Which blankflash did you use?

Are you following this guide here: https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
[Moto G4 Plus Questions & Answers] prasadak2811:
i tried with above link but no success
[Moto G4 Plus Questions & Answers] echo92:
Can you provide us with some information please as well?

What device do you have, how did your device hard brick and what errors/messages are you getting?
[Moto G4 Plus Questions & Answers] jadeilson777:
xt 1640

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8952-B1.07

(bootloader) product: athene_16mp

(bootloader) board: athene_16mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 6

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F

(bootloader) cpu: MSM8952

(bootloader) serialno: 0038111937

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: D6EBBF0200000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 536870912

(bootloader) reason: UTAG "bootmode" configured as fastboot

(bootloader) imei:

(bootloader) meid:

(bootloader) date: 09-15-2017

(bootloader) sku: XT1640-DS

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Wed May 4 19:56:34 UTC 2016"

(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ

(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys

(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta

(bootloader) ro.build.version.full[1]: il.pt.BR

(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0

(bootloader) version-baseband: M8952_70030.25.03.62.01R DFLT_FSG

(bootloader) kernel.version[0]: Linux version 3.10.84-ElementalX-G4-2.00

(bootloader) kernel.version[1]: (aaron@bella) (gcc version 4.9.4 201506

(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L

(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP

(bootloader) kernel.version[4]: PREEMPT Thu Jan 25 12:45:01 EST 2018

(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343

(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead

(bootloader) tz.git: git=69dd24b-dirty

(bootloader) hyp.git: git=69dd24b-dirty

(bootloader) keymaster.git: git=69dd24b-dirty

(bootloader) cmnlib.git: git=69dd24b-dirty

(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba

(bootloader) qe: qe 0/0

(bootloader) frp-state: no protection (0)

(bootloader) ro.carrier: retbr

all: listed above

finished. total time: 0.488s
[Moto G4 Plus Questions & Answers] echo92:
Thanks for that. A few things I've noted:

1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?

2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.

3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.

If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
[Moto G4 Plus Questions & Answers] jadeilson777:
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image
[Moto G4 Plus Questions & Answers] jadeilson777:
2) Yes I was without a network and was trying to fix what happened to the hard brick

3) Yes I am trying to flash the December rom stock NPJS25.93-14-13
[Moto G4 Plus Questions & Answers] echo92:
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.

I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.

How did you lose network in the first place, was it after flashing firmware?

If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.

If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.
[Moto G4 Plus Questions & Answers] jadeilson777:
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x
[Moto G4 Plus Questions & Answers] echo92:
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.

The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.

If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.
[Moto G4 Plus Questions & Answers] jadeilson777:
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled
[Moto G4 Plus Questions & Answers] echo92:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.

If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
[Moto G4 Plus Questions & Answers] jadeilson777:
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over
[Moto G4 Plus Questions & Answers] jadeilson777:
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus
[Moto G4 Plus Questions & Answers] echo92:
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.

---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------

Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.
[Moto G4 Plus Questions & Answers] jadeilson777:
Can you tell me when the next update comes out if and still this month?
[Moto G4 Plus Questions & Answers] echo92:
Honestly no idea - we've not even seen the OTA update for the February 2018 security update, just the patch notes. Could be this month, could be next month. Furthermore, that still relies on someone capturing and uploading the stock ROM firmware with that patch to Android FileHost or somewhere.
[Nokia 8 Guides, News, & Discussion] harisn:
When is Nokia 8 getting a new Camera app? Similar to the Camera app received by Nokia 6 and Nokia 5 after the Android Oreo update.

I still see the old camera UI, even after installing Android 8.1 Oreo.
[Nokia 8 Guides, News, & Discussion] cri347:
As I wrote here, they haven't yet released the new version on Nokia 8 because on those two devices, on which it's already present, has given some problems that they want to solve. The Nokia 8 will directly receive the fixed version. This at least as much as the Italian customer support has reported to me.
[OnePlus 5T  Accessories] Deleted member 8133137:
Ordered from slickwraps a month ago, called fedex for the tracking number, they said not shipped, tough I have an email saying it is shipped from slickwraps, they won't respond to emails for refund or explanation.

Since it seems they look at xda at least, trying here. Really shady.
[OnePlus 5T  Accessories] stevenkelby:
I can't believe people still use them. All these years of poor customer service and shonky products.

I bought one years ago, 1 of the cut outs was missing. They didn't even reply to emails.
[OnePlus 5T  Accessories] slickwraps:
Yes, thousands daily.

We're very sorry for your recent experience. At Slickwraps we stand 100% behind our products. If for any reason you are not satisfied or there was an issue with the wrap please DM us. We would love the opportunity to address this and get you wrapped up with a Slickwraps you're proud of! Thank You!

---------- Post added at 11:43 AM ---------- Previous post was at 11:42 AM ----------

Hello,

We ship with Fedex FIMS internationally. If you spoke to Fedex and not the Fedex FIMS department they would not be able to help.

With that said simply DM us on here , happy to check out your order and Fedex tracking #.

SW
[OnePlus 5T  Accessories] Deleted member 8133137:
You found me!

Ironically some minutes before xda post, i got a reply to my most recent, that it has been shipped and fedex doesn't show things anyways...
[OnePlus 5T  Accessories] Deleted member 8133137:
Got 2 of them ()all

So I got them, in 1 piece!

Unofrtionetly there is no video for m50x or m40x, and it has like 20 pieces.. I have no idea where to place the smaller ones...

Could u give at least some instructions for m50x? phones are like 3 things only, it can be figured out, but m50x is more complicated...
[OnePlus 5T  Accessories] jelousdogs:
try [MENTION=8866337]capesindia[/MENTION] , faster and better response.!
[OnePlus 5T  Accessories] Lazyboy-Summit:
Got this.. from skinnova gadgetshieldz.. it dosent even sticking at the edges.. useless.. it looks better from back side but not properly covering edges.. so useless 5-10days durable as I hate covers for devices
[OnePlus 5T  Accessories] jaybh93:
I ordered a wrap from slickwrap on Sept 5. The website says it will be shipped in a 3-4 business day. Guess what it got shipped on 19 September, nearly 2 weeks. When I track my order it still says it is waiting for next facility. It is a month since it got shipped but no sign of the product. When you submit a request to them, they will just apologize and will ask us to wait. Such a pathetic customer service. Dbrand is so much better in term of service. Other online retailers give back the money if the product is not able to deliver in a certain time frame. These douchebags are money hoggers. Sorry for my language, but I am quite annoyed because of them. I cannot use my new bumper case which I got.
[OnePlus 5T  Accessories] Deleted member 8133137:
Tip: if you spot a newsletter box, subscribe, but only buy once or with periods

If you sub to their newsletter you will see how they try with the discounts (20-50%)

They might not have the best image, but from what I understand they probably make a lot of money with few resources.
[OnePlus 5T  Accessories] jelousdogs:
Try capesindia.com
[Moto Z2 Force  Themes, Apps, and Mods] darthxa:
After broke my head a little, I finally made to work the Motokey for Moto x4 to work on our device.

View attachment 4421230 View attachment 4421231

Just follow this guide and be happy.

1 - Download this file and file two XML files and place on system/etc/permissions and set permissions to 644

View attachment 4421228

2 - download and extract the MotoKeySystemSupport.zip and place in system/priv-app and set permissions to 644 for files APK, odex and vodex

3 - download and extract the MotoKey.zip and place in system/priv-app and set permissions to 644 for files APK, odex and vodex

View attachment 4421229

4 - reboot and be happy.
[Moto Z2 Force  Themes, Apps, and Mods] mookiexl:
Didn't work for me. The XML files delete themselves after reboot. Motokey is selectable but force closes.