yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Q&A, Help & Troubleshooting] gridikoelie:
Just tried it in Ubuntu ...same result.

Warranty claim? I'm from Suriname. Would not be worth The hassle and costs.

I already ordered a Axon 7 from Amazon, but I love this phone...would really like to save it.
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
With a locked bootloader your options are pretty limited... if you can't get the official firmware to flash, there isn't much else you can do. Sorry.
[Moto G 2015 Q&A, Help & Troubleshooting] FNetV1:
Try to flash STOCK version 5.1.1 instead that is appropriate for your device original region and your region instead of the Stock version 6 that you are attempting to flash and see if that helps. Sometimes better luck can be achieved by flashing the firmware version (5.1.1) that your device potentially came with installed out of the box, that very same exact version as the one you saw when you first powered on your device for the very first time, thats the one that I recommend that you flash, version 5.1.1 and see if it goes thru..

Unless your device is in warranty, in my opinion there isn't any viable real reason for one wanting to keep their bootloader unlocked unless you dont qualify to have your bootloader unlocked because the possibility of things like this happening is still there and you will need to have a bootloader that wont restrict your very own efforts and attempts, legitimate attempts at rescuing your smartphone.

Potential cause of your issue:

Unless this was caused by a malware for which I dont see how any malware can cause such a boot loop inducing damage without having root rights and your device never being rooted (since you kept your bootloader locked, it is presumed you never installed things like TWRP or even bothered at rooting your device), so without root rights a malware cant perform a damage of such magnitude. So this leave me at the only other possibility:

Extensive NAND internal flash storage unit wear.

Yes, you probably wrote too much data to your Internal NAND (Motherboard integrated Solid State Drive) and eventually sectors began to fail until there were no more "extra" sectors to patch up failed ones and then live sectors began failing one by one until it affected critical system files thus causing a boot loop.

My assessment at your potential cause of failure could be wrong, but its my best case.

Anyways, good luck and see if flashing STOCK 5.1.1 helps you out.
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
Thanks for reply FNetV1

Try flashing XT1540_OSPREY_RETUS_5.1.1_LPI23.72-65_cid9 without success.

The smartphone does not allow downgrade from 6.0 to 5.1.1, or up to an inferior version of 6.0 to the Latin American (XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12) that tries to flash at first(XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9), Starting with that does not let me go back to the old partition table 6.0 or 5.1.1. retail us. In the screen of the telephone always indicates "version downgrade for primary_gpt" and in console adb:

F:\user\Descargas\XT1540_OSPREY_RETUS_5.1.1_LPI23.72-65_cid9_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.188s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.739s

This device was tried to flash because of problems that looked like malware, did not allow receiving calls, home button did not respond, the notifications bar was not deployed complete, among others. Previously it was realized a factory restoration that had solved everything, however soon after, I had the same problems. The user always had the phone with full memory, with no space to install anything ...
[Moto G 2015 Q&A, Help & Troubleshooting] gridikoelie:
Thanks for the suggestions, guys.

Still couldn't get it to flash.

I've been at it for 2 weeks now. I am just learning about flashing and I've tried 4X 6.0 and 4X 5.1.1 roms.

Same result:

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote failure)

For "XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12_subsidy-DEFAULT_CFC.xml" I ran these:

sudo fastboot oem fb_mode_set

sudo fastboot flash partition gpt.bin

sudo fastboot flash bootloader bootloader.img

sudo fastboot flash logo logo.bin

sudo fastboot flash boot boot.img

sudo fastboot flash recovery recovery.img

sudo fastboot flash system system.img_sparsechunk.0

sudo fastboot flash system system.img_sparsechunk.1

sudo fastboot flash system system.img_sparsechunk.2

sudo fastboot flash system system.img_sparsechunk.3

sudo fastboot flash system system.img_sparsechunk.4

sudo fastboot flash system system.img_sparsechunk.5

sudo fastboot flash system system.img_sparsechunk.6

sudo fastboot flash modem NON-HLOS.bin

sudo fastboot erase modemst1

sudo fastboot erase modemst2

sudo fastboot flash fsg fsg.mbn

sudo fastboot erase cache

sudo fastboot erase userdata

sudo fastboot erase customize

sudo fastboot erase clogo

sudo fastboot oem fb_mode_clear

sudo fastboot reboot

Am I doing something wrong?

Also...isn't there a way to just "format" it all and do a "clean install"? <--- excuse my noob-ness
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
Hi gridikoelie, in summary our problem was that we modified the partition table of original ROM with the computer with the command "fastboot flash partition gpt.bin" when trying to install the new firmware, and without enabling the box oem unlock in options Developer and also have not unlocked the bootloader.

So in these conditions everything is complicated, since we can not install any recovery, or firmware other than the one I had (in theory) I passed with motog 1st generation, I have recovered them without problems in 4.4.4, 5.0. 1 and 5.1, as long as it is the stock rom that had before the brick.

If we could load the original partition table of XT1540_OSPREY_RETUS_6.0_MPI24.65-25.1_cid9 it would bind all partitions correctly and should boot without problems ...

But the device does not let us downgrade, the version of the partition table that we place is more current than the one that had XT1540_OSPREY_RETLA_NA_6.0_MPI24.65-33.1-2_cid12

I'm wrong?

What I do not understand and gives me rage is because if we were allowed to load the gpt.bin, bootloader.img and logo.bin, the "Preflash validation"
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
Greetings again!

Even without giving up...

I have a possible solution, I say hopefully. Modifying the files "flashfile.xml" and "servicefile.xml" we could fool the bootloader to load the gpt.bin partition file and then try to flash the correct ROM version?

Something similar to this post:

https://xdaforums.com/moto-x/moto-x-qa/help-lollipop-update-brick-t3069325
[Moto G 2015 Q&A, Help & Troubleshooting] FNetV1:
Okay, I see what's the problem. You began a Stock Flash attempt without first unlocking the bootloader, not saying that starting a flash attempt without unlocking the bootloader to be a bad thing, in theory it should all go well being one of the official procedure to recover the XT1540 from scratch, but if I were you I would never, NEVER had run the GPT update fastboot without first unlocking the bootloader because things like this can occur. The bootloader accepts your GPT upgrade just fine, but then it doesn't accept the corresponding stock from (from the next steps) and when that happens you are left with an XT1540 running a GPT partition table that the current ROM installed (because it wasn't overwritten since it didn't take the new ROM flash) without being able to boot. So, not being able to flash the new and only version of ROM you can flash now because fastboot signature fails and at the same time not being able to boot the existing ROM to go to developer mode to tick enable bootloader unlock effectively leaves you with a bricked device that will be very hard to get out.

Technically speaking this was a procedural error on your part, Flashing GPT is very risky specially as a first step solution without knowing what might happen next, you should have left GPT alone, alone, and you should just have flashed the same stock rom the device had, same exact version.

You say that you tried to downgrade GPT partition tables, the problem is that you can't once you upgrade the GPT you cant go back, the whole device is made this way, rooted or not, bootloader unlocked or not, you cannot go back to a previous version of GPT.

The best you can do now:

Tell the user the Motherboard needs to be replaced in order to repair the XT1540, then charge for Part + Labor and call it a job done. At this point, I wouldn't waste any further time trying to recover the XT1540. Once you Update the GPT, bootloader will still expect you to flash the previous version ROM, but you can't flash the previous version ROM because its not compatible with the new GPT, so you are in a catch 22 situation and to top it off, your bootloader its not unlocked, its game over.

So, just recommend a motherboard replacement, go to ebay and order that up and replace it and charge the user appropriately and best of all, learn from your mistake.
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
Hi FNetV1, thanks for your input.

I am clear of my mistake. I have worked several motorola, but almost all 1st or 2nd generation, the E, G and X with android 4 and 5, I almost always unlock the bootloader, and if I do not do it earlier when I give some error (by warranty) , I have owned an xt1032 for 3 years. But I did not know the oem unlock box in developer options.for android 6.0. I think a bad play of the manufacturer, because if for some reason corrupts the system there is no way to unlock bootloader (in samsumg there is also that option that I use to unlock operator, but does not affect the recovery of the firmware). I see it as being "locked" outside your house and with the keys inside, illogical from any practical point of view.

I will have to save the plate and hope to be lucky if Motorola launches an update of the rom stock retail us cid9. Or try with some jtag box to overwrite the emmc directly by getting the pinout.

I hope motorola will change this way to unlock bootloader in the future, there are many users with this problem.
[Moto G 2015 Q&A, Help & Troubleshooting] gridikoelie:
O......k

Thank you for confirming this and thank all you guys for the help. :good:

I am the user of the XT1540 and a flash-noob. Have spent the last 3 weeks trying to safe my Moto G.

I really liked this phone (wish I had bought the 2GB RAM version though). Will have to buy a new mobo then.

The first and "fatal" flash was done by a friend of mine, who is definitely not a new to this and should have known better. Can't blame him though. That's what you get for free.
[Moto G 2015 Q&A, Help & Troubleshooting] Aqibjaved1999:
I also got same problem
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Did u tried to get unlock code ? Was OEM unlocking enabled ?
[Moto G 2015 Q&A, Help & Troubleshooting] Aqibjaved1999:
Yes I enabled
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
If u did then you can get your phone working
[Moto G 2015 Q&A, Help & Troubleshooting] Aqibjaved1999:
Yes my phone is working
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Okay
[Moto G 2015 Q&A, Help & Troubleshooting] FNetV1:
I just thought of something new you can try.

I see that through all this time you have been following the recommended fastboot flashing sequence in order and once it fails at flashing boot boot.IMG you stop, but what I propose you do now is to skip through all steps and start with flashing system and so on as described here:

Fastboot flash system the_system_image_spark.0 through the last splitted system image

IF and only IF you are successful at atleast flashing /system with any version of stock from the earliest 5.1.1 to the very latest 6.0.1 there could be a chance that it could boot without having installed that particular's image boot.IMG if it boots fine you might not have WiFi radio working because of different boot.IMG and the OSmight randomly crash forcing a reboot. However none of that would be important, you just want the OS to boot and work enough to get you in developer mode to quickly enable bootloader unlocking and then if you are successful you can reboot the phone, follow official boot unlocking procedure and then proper flash 6.0.1 following all sequence orders and you should be done.

Remember, if you are not having success at flashing /system with any version from 5.1.1 to 6.0.1 to get to developer mode to unlock bootloader, from a US version of the ROM, try again with LA versions of the ROM.

In here, you are betting that the /system will get successfully flashed and even though you did not flash it's /boot and some other partition, that it would still boot enough for you to get to developer mode.

Good luck and see if this works.
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
HI FNetV1

Did you get unbrick?

remember passing almost all the firmwares complete, even if they gave me error.

I can only enter in fastboot, the other partitions of sistem, recovery, qb_tools, in no other I can enter.

Of course entering the system and checking the option OEM Unlock would solve the problem ...

You did it !?
[Moto G 2015 Q&A, Help & Troubleshooting] jainulabudeen:
Guys I have the same problem, but my phone is unlocked and i have twrp recovery

when i give the command "fastboot flash partition gpt.bin"

the following error came....

C:\Users\SATHAKATHULLA\Desktop\Mfastbootzip>fastboot flash partition gpt.bin

target reported max download size of 268435456 bytes

sending 'partition' (32 KB)...

OKAY [ 0.005s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.416s

please help me to find a solution guys..

though i have installed cm 14.1 in my phone, in my bootloader menu, software status: official

in the beginning, when i unlocked my bootloader, it displayed software status: modified

so to try my luck i tried to unlock my boot loader again, even though it displayed "Device is UNLOCKED. status code: 3" in my bootloader menu

the results are:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock RCXKT2HRHVD3X4MHPHQ3

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) Unlock code = RCXKT2HRHVD3X4MHPHQ3

(bootloader) Not supported command in current status!

FAILED (remote failure)

finished. total time: 0.031s

what should i do now guys ? please help me to install stock firmware in my phone
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Do you have any system installed for now?
[Moto G 2015 Q&A, Help & Troubleshooting] RonRamon:
Post Log comand in ADB "mfastboot getvar all"
[Moto G 2015 Q&A, Help & Troubleshooting] jainulabudeen:
ya,

right now i have cm 14.1 in my phone

---------- Post added 5th February 2017 at 12:02 AM ---------- Previous post was 4th February 2017 at 11:38 PM ----------

getting the same error again bro
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Stick to it
[Moto G 2015 Q&A, Help & Troubleshooting] jainulabudeen:
CM 14.1 is working fine, but i want to spoof my phone's WiFi MAC id with my laptop's MAC id in order to access my College WiFi in my Phone. I've tried in CM 14.1 using nMAC app and it's not working, but it worked out in my stock ROM. Just for that reason i'm trying to revert, or is there any hope doing it in CM or LinageOS.
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Have twrp?
[Moto G 2015 Q&A, Help & Troubleshooting] jainulabudeen:
Yes i have
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
Are you able to flash any other system? Like lineage ?
[Moto G 2015 Q&A, Help & Troubleshooting] jainulabudeen:
Yes, of course i can flash it.
[Moto G 2015 Q&A, Help & Troubleshooting] infinite4evr:
I think you may not be able to flash the stock ROM ever
[Moto G 2015 Q&A, Help & Troubleshooting] BlondCleric:
It gives the same error

It gives the same preflash validation issue :/
[Moto G 2015 Q&A, Help & Troubleshooting] Anish117:
I'm also facing remote failure issue whenever I want to unlock bootloader. Plz help
[Xiaomi Redmi Note 3 Questions & Answers] Enrique prakash:
Guys I am not a developer just a lover of custom Roms recently I unlocked my device and flashed RR,lineage ,cm14 ,mokee all the Roms have one huge issue volte ,call does not go in jio I tried flashing EU.ROM no issue ,why cm14 has this issue I flashed the patches too will the developers or xioami care about it ,sorry guys I didn't point out developers they are working hard I done all the above mentioned method still volte has issue in my device I tried restore EMF still the problem persist can anybody give a detailed answer to this issue:good
[Xiaomi Redmi Note 3 Questions & Answers] Archit9169:
Yes i had the same problem. It will persist untill xiaomi releases their code for redmi note 3, and it wont be anytime soon.

https://xdaforums.com/redmi-note-3/development/volte-patches-nougat-based-cm-roms-t3509257

Follow his guide. i was able to get volte with it. It is superb.

1. Flash miui 6.11.3 and wait till it boots. Use volte on both sims.

2. Backup efs.

3. Flash cm14 by abhishek

4. Flash cm14 firmware by abhishek.

5. Flash volte V2 files by sudeep

6. reboot and call someone using volte.

7. If it works then good, if not then restore efs and call again.

Note: There wont be any signs of volte. You will only confirm by calling someone.

After you get volte on abhisheks rom, reboot to twrp and flash your desired rom.

Then flash volt V2 zip

then flash other files you want to flash

Note: Do not flash any firmware after this.
[Samsung Galaxy S7 Edge Themes, Apps, and Mods] jashancheema:
Some people facing accecibility issue.

Accecibility not turing on?

i made fix for this.

Just download zip file and flash in recovery

https://drive.google.com/file/d/0BzqLEfshRtoDSDRub05nb3B0S1k/view?usp=drivesdk
[Samsung Galaxy S7 Edge Themes, Apps, and Mods] vietnam100:
What it is please?

Gesendet von meinem SM-G935F mit Tapatalk
[Samsung Galaxy S7 Edge Themes, Apps, and Mods] jashancheema:
For some people accecicibility not turing on in settings its fix
[Samsung Galaxy S7 Edge Themes, Apps, and Mods] adamb30:
What is accecibility? You mean accessibility?
[Galaxy Tab S Q&A, Help & Troubleshooting] eberhardweber:
Magisk 10 finally came out and with it an explanation for why Magisk Hide does not yet work on stock Samsung kernels: "Stock Samsung Kernel hides namespace of processes. Magisk Hide cannot work properly"

Happy to finally find out the reason, but now I need to look for a replacement kernel.

Any custom Marshmallow-supporting kernels out yet that I might try? I saw that the newest IronRom comes with its own new kernel too, but would that be usable for this purpose?
[Galaxy Tab S Q&A, Help & Troubleshooting] eberhardweber:
To answer my own question right away! Here is the new MM IronKernel from Tkkg1994.
[Nexus 5 Q&A, Help & Troubleshooting] mobile_sensei:
Good Day XDA Friends​

As you can see from my tag, I am a retired developer.I was around in the days od Droid, Droid X, & Nexus G and was a member of a few outstanding teams like Team Liberty, Team Gummy, Sensei Mods, etc & had the pleasure of learning from pioneers like Chevy No.1 Droid, Jrunny16, Kejar31, Fab, etc. Things were much more cut and dry back then. Fast forward to today in the land of MM, Nougant, etc and I have a lot of catching up to do. First I would like to thank all you newer Devs who have kept Android growing & thriving beyond anything we thought possible, kudos to you guys!

I purchased a Nexus 5 to practice and learn on, but the phone will also be my daily driver, so I don't want to bomb out of the gate and brick my phone.

I am running the Google Nexus 5 with stock Android 6.0.1 build M4B30X on baseband M8974A-2.050.2.30, Kernal is 3.4.0-g99666f7.

I have rooted the phone and have unlocked the bootloader, and installed TWRP 2.8.7.1, but that is the extent of my customizations.

I would like to get into Nougant Roms and possibly CM. Not Sure what to flash next to become current.

I would appreciate any guidence you can give on my next steps as far as what my next steps should be. I'm looking at [HAMMERHEAD][7.1.1_r6] Zephyr OS v6.1 [DUI/OMS][27/12/2016] - [N5][OFFICIAL][7.1.0]Tesla N - 7.1.1_r4 [OMS] [28/12] - [CM14.1][7.1.1_r6] DARK ROM [Pixel features][Delta updates][12/29] - [ROM][N5][7.1.1_6]â˜… Pure Nexus â˜… Substratum â˜…[16/12/16] [Official] CyanogenMod 14.1 for Nexus 5 (hammerhead)- [ROM] [hammerhead+caf] [7.1.1] [LOS-based] **crDroid**v1.8 - [Hammerhead][official][2016/DEC/28] Slim6 weekly 1.17 / Slim7 alpha 0.5

Could someone who is knowledgeable tell me or link me to any upsates I must haave befoe flafing?

Thanks in advance for your time! :good:

~Mobile Sensei (0z0z)
[Nexus 5 Q&A, Help & Troubleshooting] catsruul:
There isn't much left. The Nexus is basically unbrickable with an unlocked bootloader and TWRP, unless you corrupt a bootloader flash.

However, you have the latest bootloader and radio, so there aren't any issues there :)

If you want to really get into Nougat you have quite a few decent options.

In no particular order-

- Slim7 Alpha (AOSP, pretty great ROM, minimal, fantastic battery life, blows all CM ROMs out of the water in terms of battery :good:, but lacks some features that other CM ROMs have (Night Display, etc.))

- Dark ROM (CM14.1 stripped down)

- LineageOS CAF, and an unofficial non-CAF (CyanogenMod 14.1 has been renamed, and will be built under the moniker LineageOS. Non-CAF builds and the weekly builds structure will be sorted out eventually)

- NitrogenOS (fully fledged CM based and packed full of features. Everything you might have wanted with Xposed is in this ROM)

-crDroid (CM14.1 based, lots of features)

-Santosh's AOSP- constant updates, stable, most bugs have been fixed regarding HDR/screen recording/green lines while video recording

...and many more. All of these are decent daily drivers; I cannot attest to their screen recording capabilities but I do know that some do have bugs concerning that as well as Google Camera/HDR.

Please note that most Nexus 5s with non-OEM screen replacements cannot boot CAF (Snapdragon Optimized). Be sure which ROM you are flashing!

IMO CAF gives slightly better performance but is relatively unstable and results in quite a few lags across different ROMs.

I also can highly recommend the blu_spark kernel as well as the ElementalX kernel for Nougat ROMs. I prefer blu_spark for its customizability, but ElementalX is rock stable.

That's it really. Just be sure to wipe system/data/dalvik/cache before clean flashing a ROM. Never flash custom kernels/ROMs over different custom kernels/ROMs; you can generally flash the same custom kernel/ROM over a previous version of the same kernel/ROM.
[Nexus 5 Q&A, Help & Troubleshooting] bblokar:
I was using crDroid for a long time since first came out with N version, but now I'm using AICP, because it's AOSP based and I must say I prefer it more than CM based, I found it's power consumption is lower and lower memory footprint plus it gets constant updates, so I use it now on both D821 and G3 D855 as well...
[Samsung Galaxy S7 Themes, Apps, and Mods] jashancheema:
Some people facing accecibility issue.

Accecibility not turing on?

i made fix for this.

Just download zip file and flash in recovery

https://drive.google.com/file/d/0BzqLEfshRtoDSDRub05nb3B0S1k/view?usp=drivesdk
[Samsung Galaxy S7 Themes, Apps, and Mods] KR15STU:
What is it?

What does it do?

Which ROM is it for?
[P3600 General] hungnt0804:
Help me!

I have a SFR S300+. When i unlock sim and CID for it, but i have been remove the USB connection from PDA phone and program during the update process

Now i cant upgrade for it.
[P3600 General] tnyynt:
Take a look here:

http://xdaforums.com/showthread.php?t=308691
[P3600 General] hungnt0804:
Thank so much.
[AT&T Samsung Galaxy S6] jashancheema:
Some people facing accecibility issue.

Accecibility not turing on?

i made fix for this.

Just download zip file and flash in recovery

https://drive.google.com/file/d/0BzqLEfshRtoDSDRub05nb3B0S1k/view?usp=drivesdk