yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A1 Questions & Answers] Never_Sm1le:
I have seen Mi 5X running a ported version of Mi A1 rom and it's very hard to distinguish from real Mi A1. Have you check the IMEI?
[Xiaomi Mi A1 Questions & Answers] mitux:
Stock rom is "Stable Global". And there is no Stable Chinese for Mi A1.
[Xiaomi Mi A1 Questions & Answers] anarchocellia:
I will check the IMEI and post the results here. Many thanks for your patient help.
[Xiaomi Mi A1 Questions & Answers] kudos1uk:
As far as I understand, if you have one of the fake Chinese ones the stenciling will be different on the back.

A real one will say:

MI

Xiaomi corporation co Ltd

Designed by Xiaomi

CE {recycle logo}

Made in China model MDG2

Androidone
[Moto G6 Questions & Answers] najjannajS650:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)

mybea you can try "fastboot flashing unlock"
[Moto G6 Questions & Answers] delosanto:
thanks, i think ive already tried that already before,

here is a recap of what happens when i type in fastboot flashing unlock

- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.

- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.

i dont have any rom installed so i cant get into developers options and allow OEM unlock :(

edited: and if i try ./fastboot oem unlock

i get

... (bootloader) invalid boot state

:crying:
[Moto G6 Questions & Answers] delosanto:
nobody has solution to this? :confused: really????
[Moto G6 Questions & Answers] Spaceminer:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
[Moto G6 Questions & Answers] delosanto:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error

after digging around xda even more ive realized im in the same situation as the guy: https://xdaforums.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215

ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"

im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..

RIP moto g6 you were my first... bricked... phone :crying:
[Moto G6 Questions & Answers] Spaceminer:
I don't think you're bricked just yet. From fastboot try the following commands;

fastboot oem fb_mode_set

fastboot format -w

fastboot erase userdata

fastboot erase cache

fastboot erase DRR

Then try flashing your firmware again. Also, something would help is running the command;

fastboot getvar all

And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
[Moto G6 Questions & Answers] delosanto:
ok, here goes nothing :D

fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s

fastboot format -w returns fastboot: usage: expected argument

fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s

fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)

fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)

getvarall info:

(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306

(bootloader) product: ali

(bootloader) board: ali

(bootloader) secure: yes

(bootloader) hwrev: PVT2

(bootloader) radio: 4

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5

(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F

(bootloader) cpu: SDM450

(bootloader) cid: 0x0032

(bootloader) channelid: 0x00

(bootloader) uid: 1A46B50700000000000000000000

(bootloader) securestate: flashing_locked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 534773760

(bootloader) reason: Fall-through from charger boot mode

(bootloader) date: 11-26-2018

(bootloader) sku: XT1925-4

(bootloader) carrier_sku: XT1925-4

(bootloader) battid: SB18C15119

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"

(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8

(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta

(bootloader) ro.build.version.full[1]: il.en.US

(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0

(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST

(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud

(bootloader) kernel.version[1]: soncm@ilclbld36) (gcc version 4.9.x 2015

(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT

(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018

(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306

(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306

(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306

(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306

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

(bootloader) ro.carrier: retgb

(bootloader) current-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

all: listed above
[Moto G6 Questions & Answers] Spaceminer:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
[Moto G6 Questions & Answers] delosanto:
im in the uk, please dont say there is still hope
[Moto G6 Questions & Answers] Spaceminer:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

If that doesn't work, try this one.

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
[Moto G6 Questions & Answers] Spaceminer:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.

If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.

---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------

@delosanto

Are you able to boot or flash twrp?
[Moto G6 Questions & Answers] delosanto:
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.

yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode
[Moto G6 Questions & Answers] Ragarianok:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
[Moto G6 Questions & Answers] delosanto:
the last OS that was successfully flashed was Oreo
[Moto G6 Questions & Answers] Spaceminer:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
[Moto G6 Questions & Answers] delosanto:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..

this i think prevents flashing ANYTHING onto the phone except two files:

./fastboot flash partition gpt.bin

./fastboot flash bootloader bootloader.img

flashing any other file returns permission denied :(

and ive tried at least 6 different roms
[Moto G6 Questions & Answers] Spaceminer:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
[Moto G6 Questions & Answers] delosanto:
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error

(bootloader) flash permission denied

FAILED (remote failure)

but then it crashes back to fastboot

and i even did a clean windows installation today

:(
[Moto G6 Questions & Answers] Spaceminer:
I think we can get you running again. Twrp can more than likely still write to the system partition since that works. Does fastboot refuse to flash that very same boot.img that I gave you?
[Moto G6 Questions & Answers] delosanto:
yes, fastboot refuses to flash that boot.img along with others ive tried like XT1925-5_STOCKBOOT or PPS29.44_no-verity_boot.img, flashing from within twrp however seems to work on some .img files (unfortunatelly it doesnt work with a stock rom .zip file)
[Moto G6 Questions & Answers] Spaceminer:
I think we need to try making you a system image of the stock rom and flashing it in twrp. Also, does your twrp have options to mount /vendor, and /oem? If not I can make that happen, I'd just need to be pointed to the one you're using. We can probably trick fastboot if we can get most of your partitions restored with TWRP. If you can use dd commands through the terminal in TWRP, you could manually flash things like the modem and logo. This is essentially what I think we need.

1. A system image of your stock rom.

2. A twrp backup of oem, and vendor.

3. Some dd commands.

I think images rewrite the file structure entirely, and that's why they work. I'm not positive about that. I know that images and .dat packages don't install the same way though.

Edit: I just realized you tried installing the stock firmware zip through twrp. That will never work. Those are not the same as ROM zips. Firmware zips must be extracted and flashed through fastboot. And OTA zips only work with stock recovery.
[Moto G6 Questions & Answers] delosanto:
is this what you have in mind?

or this?

ill study up on how to use the terminal within twrp, google for A system image of your stock rom and A twrp backup of oem, and vendor and share my progress tomorrow :D :D thanks spaceminer man! :D
[Moto G6 Questions & Answers] delosanto:
i saw the different partitions that can be backed up in twrp but could not find any online to download

the files in test backup i created have suffix like .emmc.win.sha2 or .log
[Moto G6 Questions & Answers] Ex novo:
Lenovo Moto Smart Assistant

Try flashing the ROM with Lenovo Moto Smart Assistant.
[Moto G6 Questions & Answers] delosanto:
i get THIS DEVICE IS NOT SUPPORTED msg
[Moto G6 Questions & Answers] Ex novo:
Stockrom net

Then you can try the website www stockrom net. Use the Chrome Browser to translate to your language and follow the installation instructions. Download the correct ROM for your model and the installation tools. Although I have not used the tools of this site because when I had a similar problem to yours with my Moto E5 Plus I managed to solve with Lenovo Moto Smart Assistant, I believe you have nothing to lose trying with the tools of this site.
[Moto G6 Questions & Answers] delosanto:
my problem is that i can not flash via fastboot, ive already tried countless stock roms and methods, even blankflash etc.

maybe there is a way but i guess im not experienced enough, i have flashing_locked and (bootloader) flash permission denied and no matter what i do i cant get past it, im exactly in the same situation as this guy and he was told his phone is bricked beyond normal repair

https://xdaforums.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
[Moto G6 Questions & Answers] greyman86:
If that doesn't work, you could try the Unified-Android-Toolkit, from Skipsoft. It is a great kit, but being very slowly updated, due to circumstances beyond the developers control.

It is certainly worth a try, if what the current suggestions are do not work. SkipSoft is also in the UK.
[Moto G6 Questions & Answers] madbat99:
No, no no. Skipsoft toolkit just executes adb and fastboot commands. He already said he knows how to do it manually. It will never be as reliable as manually issuing commands.

That toolkit supports only a handful of devices for build specific firmware flashing, rooting, etc. In generic mode it just does what we all know how to do. Issue commands in adb or fastboot, So... How does that help?
[Samsung Galaxy S7 Active Questions & Answers] Joshua53315:
Hi everyone,

I have an AT&T Samsung Galaxy S7 Active SM-G891A that just became unresponsive. It began with a vertical pink line appearing and disappearing intermittently down the right side of the screen. After a few times if this happening, the phone froze while playing "Laser Overload," which I had just downloaded, for about 30 minutes. I performed a soft reset and the phone went into a boot loop that lasted 20 minutes or so- sometime it would make it to the AT&T screen and freeze, sometimes it wouldn't make it past the "Samsung Galaxy S7 Active" screen.

Finally, it booted up normally but was running slowly. I powered it down, thinking it may have been overheated, and left it alone for a few hours. Upon starting it back up, it worked fine for about 15 minutes but then froze once again. I performed another soft reset, but this time the screen stayed black- no image and unresponsive to touch, but with the top left LED indicator a steady blue. It stayed like this for an hour or so until I plugged it in; the screen did show the lightning bolt charginf icon but it took about 10 minutes for it to display the battery percentage (0%). The phone had 75% battery when it became unresponsive.

Once it had charged to about 15%, I booted it up (leaving it plugged in) and again it became stuck in a boot loop. I rebooted to the system menu (Home + volume up + power) and cleared the system cache in hope that this would resolve the issue, but again the boot loop. Finally, I performed a factory restore on the phone from the boot menu. This time, the phone booted to the AT&T screen before it froze with a horizontal line of static near the bottom of the screen. I soft reset it and the phone made it through the boot screens to a Wi-Fi login. I logged in to the network and the phone froze again, this time shutting down completely and is unresponsive to being plugged in- multiple cables and chargers being used. There is no top-left LED light when plugged in, and attempting to power on the phone using any method does nothing.

Is it possible that playing a game for a half hour was the final straw in killing a graphics processor? I hadn't used this phone for any thing graphics intensive and this game seems rather simple (2D only, no simulated camera, etc.), but it's a secondhand phone that I've had for a few months now. The phone had been dropped a few days ago- only about 2ft onto a rubber mat with no damage to the phone. Could this have caused it?

Is there any way to verify what the issue could be with the phone unresponsive as it is? Any help would be appreciated.
[Motorola One Questions & Answers] AstroNoot8:
Anyone else having problems with pixelated videos/images in some apps? (e.g Discord,Reddit,9GAG,Facebook,Instagram )? It bothers me a lot and I need help with it. Many people blame the OpenGL Skia renderer used in Android Pie.
[Motorola One Questions & Answers] megamefta:
i am having the same problem on zenfone 6 (2019), could not find a solution yet.
[Xiaomi Mi 9 SE Questions & Answers] Galunid:
Hello, I wanted to download a stock firmware for my Xiaomi Mi 9 SE. It shipped with rom: V10.2.2.0 PFBEUXM.

The only download links I could find are for V10.2.3.0 PFBEUXM and V10.2.2.0 PFBMIXM.

I'd like to know what's the difference between those two and whether I can use V10.2.2.0 PFBMIXM on a PFBEUXM phone.

From what I've seen those characters reference region the phone is meant for, but I've met "MI" code only with V10.2.2.0 and I wonder whether it is some kind of "universal" rom.

Thanks in advance for your help.
[Xiaomi Mi 9 SE Questions & Answers] RinzImpulse:
"EU" is for EEA (European Economic Area) specific & "MI" is for Global for general. the difference is usually from SIM support

Check ROM link here https://xdaforums.com/mi-9-se/development/rom-official-mi9se-global-eea-china-t3929511
[Moto G6 Play Questions & Answers] madbat99:
If it's Aljeter retail, use Aljeter retail firmware. It's easiest to flash with RSDlite. You can use fastboot if you like. Just open the flashfile XML and copy the commands from it for fastboot.

https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/
[Moto G6 Play Questions & Answers] madbat99:
[MENTION=7390995]Motorocker[/MENTION]

If you flashed the boot.img and recovery.img from the stock firmware, you shouldn't be rooted anymore. I wouldn't lock the bootloader. It's not a big deal and can cause problems if a flash goes bad.
[Moto G6 Play Questions & Answers] Motorocker:
I just downloaded the following RETAIL ROM from mirrors . lolinet . com /firmware/moto/aljeter/official/ (remove the spaces, as I can't post links yet)

ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

and used the following fastboot commands, one at a time.

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash dsp adspso.bin

fastboot flash boot boot.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash oem oem.img

fastboot flash vendor vendor.img

fastboot erase carrier

fastboot erase userdata

fastboot erase DDR

fastboot flash logo logo.bin

fastboot reboot

Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.
[Moto G6 Play Questions & Answers] jatindra105:
please give me offiicial rom

(bootloader) version: 0 . 5

(bootloader) version-bootloader: MBM-2 . 1-aljeter_retail-b1f322d-191127

(bootloader) product: jeter

(bootloader) board: jeter

(bootloader) secure: yes

(bootloader) hwrev: P4

(bootloader) radio: 2

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003

(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F

(bootloader) cpu: MSM8937

(bootloader) serialno: ZL522265N2

(bootloader) cid: 0x0032

(bootloader) channelid: 0xc0

(bootloader) uid: 5FC3428700000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: no

(bootloader) max-download-size: 535822336

(bootloader) reason: Fall-through from normal boot mode

(bootloader) imei: 35552709152xxxx

(bootloader) meid:

(bootloader) date: 06-08-2018

(bootloader) sku: XT1922-10

(bootloader) carrier_sku: XT1922-10

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Thu Mar 5 10: 2:54 UTC 2020"

(bootloader) ro . build . fingerprint[0]: motorola/aljeter/aljeter:9/PPP29 . 5

(bootloader) ro . build . fingerprint[1]: 5-35-18/f7946:user/release-keys

(bootloader) poweroffalarm: 0

(bootloader) ro . build . version . full[0]: Blur_Version . 29 . 301 . 33 . aljeter . re

(bootloader) ro . build . version . full[1]: tail . en . US

(bootloader) ro . build . version . qcom: LA . UM . 7 . 6 . r1-03700-89xx . 0

(bootloader) version-baseband: M8937_34 . 42 . 05 . 97Z JETER_INDIADSDS_CUST

(bootloader) kernel . version[0]: Linux version 3 . 18 . 120-perf-g3e480e1-042

(bootloader) kernel . version[1]: 56-gd43db30 (hudsoncm@ilclbld160) (gcc v

(bootloader) kernel . version[2]: ersion 4 . 9 . x 20150123 (prerelease) (GCC)

(bootloader) kernel . version[3]: ) #1 SMP PREEMPT Wed Nov 27 09:41:39 CS

(bootloader) kernel . version[4]: T 2019

(bootloader) sbl1 . git: MBM-2 . 1-aljeter_retail-0d2031d-191127

(bootloader) rpm . git: MBM-2 . 1-aljeter_retail-af31f6a-191127

(bootloader) tz . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) devcfg . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) keymaster . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) cmnlib . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) cmnlib64 . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) prov . git: MBM-2 . 1-aljeter_retail-5bf0857-191127

(bootloader) aboot . git: MBM-2 . 1-aljeter_retail-b1f322d-191127

(bootloader) frp-state: protected (77)

(bootloader) ro . carrier: retin

(bootloader) current-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

all: listed above

finished . total time: 0 . 215s

i need official stock rom please sugest me