Database Info

Moto g3(2015) XT1550 flashable modem file

When I flash cm13 or mokee rom sim card doesn't get detected but after i get back to stock moto g3(2015) XT1550 rom(indian dual sim varient) it works fine...any solution?

did you format sd card as external ?? or internal ??
if you format as internal , then format as external .. then remove memory card and keep it again
i dont know if it works.. but its just a suggestion

nandakis4 said:
did you format sd card as external ?? or internal ??
if you format as internal , then format as external .. then remove memory card and keep it again
i dont know if it works.. but its just a suggestion
Click to expand...
Click to collapse
I tried everything, It didn't work in any way... I am not even able to flash to lollipop stock rom for moto g3. It shows <bootloader> prevalidation failed though i have allowed oem unlock and debugging. I dont want marshmallow, it has many bugs like scroll bugs and glitches.. And the bootloader is unlocked too...

akkisid23 said:
I am not even able to flash to lollipop stock rom for moto g3. It shows <bootloader> prevalidation failed though
Click to expand...
Click to collapse
If you are doing downgrade, you don't have to downgrade bootloader (and you musn't downgrade partition!). Just do:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Acetyloaceton said:
If you are doing downgrade, you don't have to downgrade bootloader (and you musn't downgrade partition!). Just do:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Oh cool, thank you so much and one more thing is when i flash any ROM on my moto g3 it doesn't detect sim card and when I get back to normal stock ROM its all well and fine..I even tried flashing the modem file(NON-HLOS.bin) that was in the stock ROM zip file but did not work...what do I do?

Problems after unlocking bootloader

I manually unlocked my bootloader and began the process of installing TWRP and then Cyanogenmod. After playing with Cyanogenmod I realized I wasn't missing much, so I tried to go back to Lollipop / Marshmallow only to discover that now every time I boot up my phone it immediately goes to the bootloader, requiring me to manually start my phone. If I try to factory reset it does the same thing. I can reinstall TWRP, but the resulting flash will not allow me to flash custom roms or do much more than click buttons that won't do anything. I cannot get TWRP to export my log to the SD card so I can share the issues. Here is what I have noticed:
1. I have no cache directory according to TWRP.
2. If I try to flash a custom rom, IE Cyanogenmod, it reboots recovery and I don't see an error until I attempt to go back and reflash. Again, I cannot export a log file that will open or allow me to copy it to a different directory.
3. No matter what operation I try to perform, rebooting the device always puts it back to the bootloader. I have to manually start my phone from the menu.
Is there something I should be doing differently? Should I try and flash down to Cyanogenmod 12.1 and then go back to Lollipop? Is the previous upgrade to Marshmallow screwing things up?

Hmm... can you try to flash firmware again? For now skip factory reset in recovery. You can do it later. Flash the latest Marshmallow firmware in bootloader mode:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If you want to flash lollipop you must skip partition and bootloader. It might cause bootloop which you will not be able to fix:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

If your phone goes to the bootloader mode every boot, then you didn't close fb_oem mode, when in the bootloader send the command "fastboot oem fb_mode_clear", you should get an OK. Reboot and you should be good to go.

Your phone reboot to system but every reboot it goes first to bootloader or only bootloader is loaded and you can't boot to system? If first then do what @acejavelin said. If system is not loaded then flash firmware again.

<bootloader/ has-slot:system: not found?

I can flash firmware again, but from there it's still acting up. I also cannot do fastboot oem lock.

Now I'm told the storage is in RAW format?

Downgrading the bootloader

Hi guys!
I have got the XT1621 and i have a lot of lag when i flash a nougat firmware through fastboot
But when i install marshmallow (23.4) and i update by ota to nougat (-14) it is very smooth!!
The problem is that i updated by induced ota from -14 to -14-4 nougat
The real problem is that the bootloader updated to .05 version and i cant flash marshmallow and update by ota to -14 because it would end in hardbrick!!
What can i do to downgrade??
If i hardbricked my moto g4 with intention, could i flash the -14 bootloader blankflash file? It could be a way to downgrade the bootloader
Any other idea of what can i do?

I recall you can downgrade to MM if you wish, just do not flash the GPT and bootloader partitions. Leave them as they are. That way, you'll avoid a hard brick (but you'll need to flash the latest firmware to re-lock your device).
Of course, you'll need an unlocked bootloader for this to work, and the appropriate stock ROM (a copy is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETAIL/) - I see XT1622 MPJ24.139-23.4 which matches what you had before (though I strongly recommend double checking it's the right firmware).
Then follow this guide to downgrade: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
If you're unable to download the script that's mentioned in the guide, you may try the following fastboot commands (note the absence of the locking, GPT and bootloader commands).
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
This procedure will wipe your device and should revert your device to an MM baseband and system. As always, back up your data, move it off your device until you're done flashing.

Relock bootloader

Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.

gorbatschoff said:
Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.
Click to expand...
Click to collapse
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .

Thanks for the answer. I've used these commands and of course they work. The phone works but the ADB and recovery problem is still there. And that worries me.

dont work
SnowTalker said:
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 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_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .
Click to expand...
Click to collapse
dont work

bugy65 said:
dont work
Click to expand...
Click to collapse
The commands?

Moto G7 Power XT1955-5 Baseband: (Not Found)

I have flashed several times to this phone and never have I had issues. Yet, after trying out Lineage OS 17.1 I can no longer get broadband connection. I have flashed back to the stock ROM and I still have the same issue that was happening with Lineage OS 17.1 . Basically, it seems as if my IMEI info isn't getting pulled to the system. I noticed that when at the bootloader screen it says ""Baseband: (Not Found). I'm thinking this might have something to do with my issue. (I don't really know.)
EDIT: I will add that I do have wireless functionality and can get internet perfectly fine. Why I think it's IMEI related is because it isn't filled in the OS About phone section. I've even done *#06# and that just shows the serial number of my phone.
[ I do see the following ]
Running: fastboot getvar all
...
(bootloader) version-baseband: <not found>
...
(bootloader) imei: 3595250... // I omitted part of this for privacy reasons.
(bootloader) meid:
...
I have done the following as well to no effect:
fastboot oem config carrier virgin, vzw
fastboot oem config fsg-id virgin, vzw
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache

ITDominator said:
I have flashed several times to this phone and never have I had issues. Yet, after trying out Lineage OS 17.1 I can no longer get broadband connection. I have flashed back to the stock ROM and I still have the same issue that was happening with Lineage OS 17.1 . Basically, it seems as if my IMEI info isn't getting pulled to the system. I noticed that when at the bootloader screen it says ""Baseband: (Not Found). I'm thinking this might have something to do with my issue. (I don't really know.)
EDIT: I will add that I do have wireless functionality and can get internet perfectly fine. Why I think it's IMEI related is because it isn't filled in the OS About phone section. I've even done *#06# and that just shows the serial number of my phone.
[ I do see the following ]
Running: fastboot getvar all
...
(bootloader) version-baseband: <not found>
...
(bootloader) imei: 3595250... // I omitted part of this for privacy reasons.
(bootloader) meid:
...
I have done the following as well to no effect:
fastboot oem config carrier virgin, vzw
fastboot oem config fsg-id virgin, vzw
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Click to expand...
Click to collapse
I would try flashing just the modems not sure if u in us if u are u can try the retus modems do it several times just lost base band some times have to try different modems from different carriers https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw. Go here if u need more help

</sigh> I kid ya'll not, I resolved my issue.... I know the stock firmware I had worked for me plenty of times but it looks like trying a different and newer version worked in its stead.
I got the new firmware from here: <Add https back to the link>
//mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
I used the following version:
XT1955-5_OCEAN_RETUS_10_QPO30.85-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I used all the same commands I've ran before.
fastboot oem fb_mode_set oem
fastboot erase all
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
#fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear

roadkill42 said:
I would try flashing just the modems not sure if u in us if u are u can try the retus modems do it several times just lost base band some times have to try different modems from different carriers...
Click to expand...
Click to collapse
I would have sworn the former stock ROM I had was RETUS but looking at it's info, I'm no longer sure. Even then, it was at one point working fine when flashing it. I tried a new stock ROM and later newer build version and that seems to have worked. I'm happy yet frustrated with how much time I've sunk into this issue. </sigh>
(AVOID AT ALL COSTS)
Here is the old stock ROM build info:
BUILD REQUEST INFO:
SW Version: ocean-user 9 PPO29.114-134 fee207 release-keysM632_26.100.01.120.01R
MBM Version: MBM-2.1-ocean_retail-b508f3a-190702
Modem Version: M632_26.100.01.120.01R
FSG Version: FSG-8953-22.112
Build Fingerprint: motorola/ocean/ocean:9/PPO29.114-134/fee207:user/release-keys
CQATest App Version: 6.0.4
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.271.151.ocean.retail.en.US
Model Number: moto g(7) power
Android Version: 9
Baseband Version: M632_26.100.01.120.01R
Build Id: PPO29.114-134
SW Display Build ID: PPO29.114-134
Build Date: Tue Jul 2 04:40:26 CDT 2019
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.29.271.151.ocean.retail.en.US
Version when read from CPV: ocean-user 9 PPO29.114-134 fee207 release-keys
AB Update Enabled: True
Full Treble Enabled: True

ITDominator said:
</sigh> I kid ya'll not, I resolved my issue.... I know the stock firmware I had worked for me plenty of times but it looks like trying a different and newer version worked in its stead.
I got the new firmware from here: <Add https back to the link>
//mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
I used the following version:
XT1955-5_OCEAN_RETUS_10_QPO30.85-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I used all the same commands I've ran before.
fastboot oem fb_mode_set oem
fastboot erase all
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
#fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
There is one more command for q this is all the commands for 10 aka q

You are missing one command line.
roadkill42 said:
There is one more command for q this is all the commands for 10 aka q
Click to expand...
Click to collapse
Please note that version Q or 10 has one more sparsechunk file, so you must add a line fastboot flash system system.img_sparsechunk.10 If you don't you will not have a full load.

tamwood53 said:
Please note that version Q or 10 has one more sparsechunk file, so you must add a line fastboot flash system system.img_sparsechunk.10 If you don't you will not have a full load.
Click to expand...
Click to collapse
Well...it seems to run fine without the chunk? I ran flashing without that last img_sparsechunk and I don't have issues currently. (Didn't see it existed when I flashed...) Will it affect updating by any chance?