yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Lite Questions & Answers] dbl81:
Hi all,

I followed the instructions at point number 6 of this thread:

https://xdaforums.com/huawei-p9lite/how-to/tips-tricks-tools-huawei-p9-lite-t3452756

and now I'm successfully using my external SD as internal storage.

As the above post warns, the storage info page cannot measure the real space left, but I can use all the apps/features except the panoramic shot function of the stock camera app: it says "disk full".

I wiped data and cache of the camera app, but panoramic shot still gives me the disk full error.

I can use the stock camera for "normal" shots without any problem.

Do you have any suggest?

I really like the stock camera and I think it's faster than other camera apps I found on play store.

Thank you.
[Motorola One Action Guides, News, & Discussion] tys0n:
I've made a .bat file for flashing and some other stuff. Basic stuff that I use the most.

I made it for One Vision but since Action use exactly the same flash commands, it works for Action as well.

View attachment 4838841

Unzip .bat to same dir as your fastboot.exe and double click it or drag it to your cmd window and press enter.

Options:

[f] - FLASH FULL FIRMWARE.

[w] - FACTORY RESET. (erase userdata)

[g] - DEVICE INFO. (getvar all)

[p] - OEM PARTITION INFO. (oem partition)

- GET BOOTLOADER UNLOCK CODE FROM DEVICE. (oem get_unlock_data)

[r] - REBOOT TO SYSTEM, EXIT.

- REBOOT TO BOOTLOADER.

[e] - EXIT, leave the phone in fastboot mode.
[Motorola One Action Guides, News, & Discussion] arsradu:
Nice work! Really useful for flashing Android 9. :D However, couple of changes might be necessary for Android 10, in case anyone wants to use it for that. Minor changes. :)

Such as:

renaming bootloader.bin to bootloader.img

renaming fwbl1.nbl1.bin to fwbl1.img

renaming keystorage.bin to keystorage.img

renaming ldfw.bin to ldfw.img

Other than that, very good idea, and very useful tool!

Thank you! :)
[Motorola One Action Guides, News, & Discussion] binary**#:
Updated Fastboot command batch file for Android 10

This is the updated fastboot command batch file for Android 10. Just move to the platform-tools folder and execute it (obviously the stock firmware should be there as well :p)

Haven't added the fastboot reboot command at the end. You will have to execute that command manually after the flashing is done (in case the device doesn't automatically boots up).

PS: Can't upload the .bat file directly so had to compress it.
[Motorola One Action Guides, News, & Discussion] arsradu:
Attached the updated version for Android 10, including the rest of the tool, for anyone interested. :)
[Motorola One Action Guides, News, & Discussion] tys0n:
Thanks for your contribution. I actually updated the .bat it a few weeks ago to include both pie and A10 flash commands, since not everyone is updated yet.

Then I realized it would be stupid to share it cause someone would probably try to downgrade, which may result in i brick, and then blame me for it :P although it's common knowledge not to downgrade android version on new devices.

I'll probably have to add a warning about it in the .bat at least.
[Motorola One Action Guides, News, & Discussion] arsradu:
Heey! Welcome back! :)

It is common knowledge indeed. And I always wondered why is that. Why does it result in a brick? I'm guessing there are some conflicts or something, right? If you have more info (which it sounds like you do) could you share it? I would love to know more about it. :)

I mean, you could do that pretty easily with older (Android 6 for example) devices. I mean, it's not advisable. But...if the update sucks or it brings some really nasty bugs and you cannot use your phone cause the modem part of it is broken, for example, there should be a way to safely go back to the previous version, right...? At least until the bug is fixed. Shouldn't it be possible to simply flash Android 9 the same way you do Android 10 (I'm guessing the answer is no, but just wondering why...)? You can even do that on iOS, for God's sake! Which is like the definition of no downgrades! But Apple still allows it. Not permanently, but for a while, yeah, if you have an issue with the new version, you can go back to the old one.

But, yeah, you're definitely not the first one advising against going back to, in this case, Android 9.

By the way, nice job with this script. I was working on a version for Mac, since I'm a Mac guy. :) And...I got pretty far. But one thing I can't figure out how to do: goto (especially for the "Back to Menu" option which is used pretty often). There is no such thing in Bash. So...you have to improvise. And so far, everything I tried failed, for one reason or the other. So..for now, I just boot into Windows if I need to flash anything. Then return to Mac. :))

It's' good to see you around. And once again, thank you! :)

Update:

So...downgrading to Android 9 is definitely possible. You just need to make sure OEM Unlock is checked in Developer Options (allowing bootloader to be unlocked) and that you actually are bootloader unlocked. Everything else is the same.

Update 2:

There seems to be a typo in your script when flashing vbmeta.

It should be "fastboot flash vbmeta_a vbmeta.img" according to the flashfile.xml for Android 9.
[Motorola One Action Guides, News, & Discussion] tys0n:
Sorry, I don't know what it is that can cause bricks when downloading android version, but you're right, everything was easier with older android versions :)

Did you try to downgrade from 10 to 9, and it worked? It would be great if that was the case.

Thank you..again! Didn't notice that typo and I've had no problems or errors while testing/flashing with it.

I guess that's why I missed it. You don't look for errors if it's working :P

I'm attaching an updated tool with pie and android 10 flashing, and typo corrected. Also added you to "credits".

For now I've added a warning about downgrade since I don't have any confirmation on if it's possible or not.
[Motorola One Action Guides, News, & Discussion] arsradu:
It is possible. :) I'm back on Android 9 right now.

BUT, a few notes:

1. the problem causing boot failure (and flash failure, with error "(bootloader) validation image failed") is not so much the ROM itself, as it is the Security Patch. It seems that it HAS TO be at least the same version. Which makes me think that it should be possible (at least in theory) to downgrade to Android 9, even without unlocking the bootloader, IF the Security Patch you're coming from is the same as the one of the ROM you're trying to flash. In other words, if your Security Patch is not being downgraded. It has to be at least the same version, or newer, in order to work without any issues.

2. IF you already upgraded to something, anything, with a newer Security Patch, downgrading is no longer possible with a locked bootloader. It IS, however, possible after unlocking the bootloader (which will void the warranty).

3. once in this state (unlocked and downgraded to Android 9), you cannot relock the bootloader anymore (again, IF you're coming from a newer Security Patch). No errors when locking, but upon boot, you'll get the "your device has failed verification and may not work properly" warning, and, despite the message underneath that says "your device will boot in 5 seconds", it won't boot.

I'm guessing...it should be possible to relock the bootloader IF:

1. you're upgrading again to the ROM with the Security Patch you had before (January 2020 for example), but then you won't be able to downgrade again (unless you unlock the bootloader).

2. you're waiting for a security patch for the current Android version to match the one you had before (again, January 2020 for example).

So, in other words, you can either flash a January 2020 Security Patch included with a ROM, or wait to receive it via OTA.

Also, thank you very much for the update. Indeed, it doesn't show any errors. When upgrading to Android 10, I already corrected that line. But I forgot to do the same in the original script. No errors indeed (not sure if it makes any difference....) but it's probably better to be corrected nonetheless.

Soo...thank you! :)
[Motorola One Action Guides, News, & Discussion] binary**#:
Hey, first off thanks to both of you arsradu and tys0n for sharing some wonderful insights. What I failed to understand is the fact that how the initial tool was still able to flash the vbmeta file if you failed to mention which slot should it be flashed to? Is explicitly mentioning slot isn't compulsory for all the files?

Another thing which seems to intrigue me is the fact that how come we have fixed the slots in these fastboot commands. Because in dual slots, the active/inactive slots keep on changing every time we flash an OTA and REBOOT the device. So in those cases, why don't we have to modify these fastboot commands according to the changing slots?

For example, if we use fastboot flash vbmeta_a vbmeta.img, then we always use this command only and not vbmeta_b vbmeta.img. It seems we are explicitly assuming that every device should be having 'A' partition as the inactive slot (before REBOOT), but that can't be universally applicable, right? But we all know it works like a charm! So what is it that is actually happening ??

Any update on this by you guys will be highly appreciated ;)
[Motorola One Action Guides, News, & Discussion] arsradu:
Your guess is a s good as mine. :)) Maybe tys0n has some better knowledge about it. I was also wondering why only vbmeta_a.... And how does it work though, without specifying which slot to write to? There is no vbmeta_b in the xml. Why? I have no idea.

I mean, it's clear that, for other components, you need to specify it. At least, the flashfile.xml is specifying it. So you would assume it is important. Aaand I don't think anyone is assuming this is a universal tool for every device. Though it can definitely be adapted for other phones.... :)) So I'm not assuming every phone is gonna write to the same partition. But these two (the Vision and the Action) seem to have this thing in common.

I'm not sure what you mean by switching slots. I honestly don't have enough experience with that. Also, I don't think the tool is for flashing the OTA updates... I think it's only for flashing the full images. Again, I could be wrong here. This is a new phone for me, and I haven't checked any OTAs for it yet. If you have one, we can analyse that. But...again, I'm not sure if this tool was meant for flashing OTAs.
[Motorola One Action Guides, News, & Discussion] binary**#:
First off I should have been more specific regarding the term "every device", what I actually meant was "every Moto one action device".... An error on my part [emoji2960]....

Regarding the OTA I didn't meant to say that this tool could be/couldn't be used to flash OTAs[emoji85]

Coming back to the point, while executing the fastboot command to flash vbmeta, we always keep the slot A attached to it, rather than checking for the inactive slot beforehand and then flashing. I guess the reason could be the fact that since we are using these fastboot commands to install the stock firmware from scratch...so whatever slot we install the system to, vbmeta needs to be flashed to that slot...

As we are installing system to slot A (fastboot flash system_a system.img), so it's 'vbmeta_a' vbmeta.img.

Now I'll try flashing all these sparsechunk files to slot b and then check whether vbmeta gets flashed to that slot without actually mentioning that slot (B) in its fastboot command [emoji14]

And yes, thanks for your prompt response:)
[Motorola One Action Guides, News, & Discussion] arsradu:
You know why I love this community? Cause we can share interesting ideas and experiences like this. We can learn from each other. And at least for what I'm concerned, I do have a LOT to learn. And I'm glad I have nice people I can learn from.

As for your experiment, I'm also curious to know the outcome. I never wondered what would happen in that particular case. But then again, I'm very much a noob when it comes to this phone. It's a new phone, never done this on another Moto phone, and I know each manufacturer (and sometimes each phone) has its own particularities. So I'm happy to learn from you guys. :)
[Motorola One Action Guides, News, & Discussion] binary**#:
Exactly! There are tons of new things to learn from everyone out there. And this being my first Exynos device, I'm just loving the challenges here. Till now I only had Snapdragon devices in which everything was a cakewalk. Furthermore, my recent devices were all Redmi/Xiaomi and it had a pretty neat escape even from hard-brick situations via EDL Mode. But with One Action, everything is so different, thanks to its processor :p
[Motorola One Action Guides, News, & Discussion] arsradu:
Yeah, I was actually surprised (pleasantly surprised, I might say) it had a Samsung SOC. My previous Moto had a Mediatek and I did not enjoy that one bit. New versions are better though. But that one...not really. And before that I had a SONY Z3 Compact. Cool phone, plenty powerful for its time, but apparently SONY had some troubles with their glue...cause the display kept getting unstuck. :))) Looks like this was its "thing".

Anyway, back to Moto Action, I'm liking it so far. The only thing I don't particularly like about it is the update. Kinda slow for an Android One device. But hey, it could be worse. :)) I'm not expecting too much from a mid-range device. It's perfect for the price. And for my use case, it gets the job done.
[Motorola One Action Guides, News, & Discussion] binary**#:
You pretty much summed it up: "kinda slow, but could have been worse". I was confused between Mi A3 and One Action, but I ultimately decided to go with the latter (because of 720p display of Mi A3, there was really no point in going after that). And now I'm quite satisfied with my choice, even more so considering Mi A3 is yet to receive the Android 10 update.
[Motorola One Action Guides, News, & Discussion] arsradu:
Lucky dawg, you already got it. You got it first, didn’t you? :)))

Well, you know, I’m happy for you, man. This way you have more time to experiment with it so you can help others when they get theirs. So, if you think about it, it’s really a win-win. :)))
[Motorola One Action Guides, News, & Discussion] achmed420:
i ****ed up

guys i ****ed up and bricked my moto one action xt2013-4 and now it wont boot and i cant flash stock firmware back to it
[Motorola One Action Guides, News, & Discussion] arsradu:
What did you do? What error do you get on boot? What error do you get when flashing?
[Motorola One Action Guides, News, & Discussion] achmed420:
i ****ed up

i unlocked boot loader and attempted to flash TROIKA_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml some items failed other flashed some had verification image errors and now it won let me boot anything except recovery and fastboot ... i was on psbs29. 105-27-2 before this with january 2020 security patch
[Motorola One Action Guides, News, & Discussion] arsradu:
Where did you get the ROM from? Can you post a link? I'm trying to understand which exact variant (for which region) did you flash.

You still didn't tell me which error do you get upon boot. :)

Also, did you use the correct commands for Android 10? Which script did you use?

By the looks of it, you tried to flash a ROM with December security patch over one with January security patch. Which, with a locked bootloader is not gonna be possible, but...should be possible with an unlocked bootloader. But since you didn't tell me which error do you get upon boot, I'm not sure how to help you.
[Motorola One Action Guides, News, & Discussion] achmed420:
no errors on boot it just boot loops the android one logo and i cant remember where i downloaded rom from i used adb to flash do you have a stock firmware with january security i can flash

---------- Post added at 04:45 PM ---------- Previous post was at 04:35 PM ----------

this is the build info for the rom i attempted to flash

BUILD INFORMATION

SW Version: troika-user 10 QSB30.62-17 10ff7 release-keys

Build ID: QSB30.62-17

SW Display Build ID: QSB30.62-17

MBM Version: MBM-2.2-troika_retail-72368e2-191210

Modem Version: S337AP_TROIKA_SGCS_QB2658324

OTHER INFORMATION

Sudsidy Lock File: slcf_samsung_default_v1.0.atc

Regulatory Info (elabel): regulatory_info_default.png

Build Fingerprint: motorola/troika/troika_sprout:10/QSB30.62-17/10ff7:user/release-keys
[Motorola One Action Guides, News, & Discussion] arsradu:
Looks like you've got one of the RETAIL versions.

Bootloop when the logo is displayed is usually (at least in my experience) a sign of incompatible userdata.

Try to erase userdata and try to boot again.

You can do this in two ways:

1. command line:

fastboot erase userdata

2. boot into Recovery and select Wipe data/factory reset.

To do that:

a) boot into Bootloader as usual (Power + Volume Down).

b) use the Up and Down volume buttons until you see Recovery

c) press the Power to select it

d) in the "no command" screen, press end hold Power button and short press Volume UP.

e) in the next screen you should be in Recovery mode where you can select Wipe Data/Factory reset

f) in the same screen, select Reboot System Now.

See if you can boot after that.
[Motorola One Action Guides, News, & Discussion] achmed420:
yes i do have a retail version and i already wiped userdata a bunch but i think you missed the part where i mention it only half flashed the files like GPT.bin failed bootloader.img flashed non-hlos.bin failed fsg.mbn failed modem 1 and 2 were denied bluetooth failed dspso.bin failed boot.img verification image failed system.img flashed vendor.img failed erased carrier

erased userdata erase ddr failed logo.bin flashed ....

---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------

and i factory reset as well still same story i need the firmware files to flash stock
[Motorola One Action Guides, News, & Discussion] arsradu:
waaait. where did you get those commands?

GPT.bin? non-hlos.bin...? Which ROM are you trying to flash? For which device? This is usually for G-series, not One series.

This is the list of commands if you're flashing Android 9:

fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img

And this if you're flashing Android 10:

fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img

As you can see, there are no such files in this ROM.

Here you can find the RETAIL ROM (if you still want to go with that) for Motorola One Action (aka TROIKA).

Get the script from this post and flash the ROM again. Make sure you select the correct letter [q] for Android 10.
[Motorola One Action Guides, News, & Discussion] achmed420:
i got the commands i used from androidinfotech,com

and thank you for the firmware link but am i going to have issues going to a different security patch
[Motorola One Action Guides, News, & Discussion] arsradu:
The commands are wrong. Very. Wrong.

I mean, in case you didn't see that for yourself. :)) Those commands are NOT for the Motorola One Action. You cannot flash those files since they are not present in the ROM.

Also, from the page I gave you, you have one Android 10 build with December Security Patch (QSB30.62-17) and one with January security patch (QSBS30.62-17-2).

I would highly recommend going with the December Security Patch version.
[Motorola One Action Guides, News, & Discussion] achmed420:
i will gladly take your advice (wish you would explain though as this is only the 3rd device ive flashed my first was a moto g7 power then a samsung s10+ an this is my new phone) but it shouldnt be an issue to go backwards... im a knowlegeble noob but still a noob
[Motorola One Action Guides, News, & Discussion] arsradu:
a

I'm not an expert either. But I know for sure those commands are wrong for flashing the ROM on a Moto One Action!

Anyway, what do you want to know? :) I thought the instructions were clear. Buut...I guess they weren't...? :))

1. commands for Moto G7 and Moto One Action are NOT the same. Please don't mix them. While the commands you mentioned above might work for the G7, they will most certainly not work for the Action.

2. you need to either download the ROM (whichever security patch you want, but I would recommend December, so you don't have issues in case you need to revert) or, if you already have it downloaded, just flash again.

3. please, use the script I posted above. It's a lot easier, and since you're actually on that script's thread, it would be a good idea to actually use it. :))

I saw a tutorial a while ago on a site somewhere (I don't remember if it was the same one you mentioned or a different one), but they said the tutorial was for Moto One Action, and they were providing a ROM for Moto One VISION! So I don't trust those at all.

Anyway, please, let me know what exactly do you want me to explain and I'll do my best to do so. :)
[Motorola One Action Guides, News, & Discussion] achmed420:
i was wondering why you recommend the dec security patch even though i was on january before i tried flashing the wrong stuff