Related
hello
i update to nougat by using these commands
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
Fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
and now instead of 64GB i see only 24..where is the rest?
i have root and twrp
thanks
Only those with the 32gb model need to flash user data
So just format your device and start over and you should have 64gb again.
ok so i just to skip the
fastboot flash userdata userdata.img
but it stays as before 24.1GB
and what is - Fastboot flash vendor vendor.img
thank you
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
and i did fastboot flash userdata userdata.img
so to fix these i did the flash all.bat
just left to know what is the Fastboot flash vendor vendor.img
thanks
Format data
See guide here : http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
vendor formats data???
flashing the vendor will not cause a wipe of data.
firstly fastboot format userdata
then follow the guide by Heisenberg that is stickied.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
what does the vendor command?
I7210I said:
what does the vendor command?
Click to expand...
Click to collapse
It will flash the vendor.img
so if the device doesn't know that he is from huawei so these will remind him?
Sent from my Nexus 6P using Tapatalk
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
try http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
then flash android 6.0 maybe trupure 2.9 and then get the modem from trupure and flash it
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
acejavelin said:
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
Click to expand...
Click to collapse
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
goldentequila said:
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
Click to expand...
Click to collapse
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Sagar_1401 said:
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
Click to expand...
Click to collapse
The instruction in that post said to not worry about the sparse error message, so I went with it. This is what the post said.
"You may notice a "sparse header error" when flashing at the beginning. Don't worry about it, all is well. The current AutoFlashFirmware.bat file doesn't work with this Firmware file. Flash the files manually!"
Also, i posted above too, but I just accidentally wiped internal via TWRP too. Do you know what I need to do now in order to get my phone back? I've found solutions for other phones regarding this situation, but I haven't come across one for Moto X Pure. This is what happens when you work on your phone all day long and some more into late night lol...
acejavelin said:
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Click to expand...
Click to collapse
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
goldentequila said:
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
Click to expand...
Click to collapse
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
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 flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
acejavelin said:
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
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 flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
goldentequila said:
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
Click to expand...
Click to collapse
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Oh ok. Thanks again. I'll report back if I succeed (or not) later today. I appreciate your help.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
goldentequila said:
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
Click to expand...
Click to collapse
Glad I could help. You're welcome.
Lol it was sparsechunk i just got confused with it and said spunk??
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
I mean ... is the October fastboot rom ready to flash with miflash and comes with root?
rulezman said:
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
Click to expand...
Click to collapse
Heard that there are two Oct updates, may I know if yours is the latest?
.15 is the second (latest) October update.
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Can't flash through miui flasher. Is it possible to flash this through recovery?
Are U tested?
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Ind33d said:
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Click to expand...
Click to collapse
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Xyam said:
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Click to expand...
Click to collapse
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Ind33d said:
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Click to expand...
Click to collapse
Yup
i lost my wlan mac adress by flashing this, im flashing again now without without_data
anyone ever seen that problem?
nvm, the 3rd time it worked
9.6.16 is out can you provide fastboot archive?
hugopg said:
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Click to expand...
Click to collapse
I researched for such a long time on this, I'm exactly the same in your situation, rooted with magisk, camera2api substratum things like that on august patch.
Later on i figured myself a way to update without losing any data or wiping the phone which is :
1. download the full stock rom of august patch, it should be tgz files, extract it.
2. Make sure u got adb fastboot all the stuff installed on pc, and also mi a2 drivers.
3. On the phone, go to developer options and turn on usb debugging, guess u already done it since you rooted the phone.
4 now connect the phone to pc in fastboot mode.
5. After extract the tgz august stock rom, locate to folder "image".
6. Hold shift and right click open cmd or in my case open windows power shell.
7. Type fastboot devices to see if your phone is connected properly.
8. Paste these codes and hit enter.
9. After that the phone will be rebooted and after success booting go to settings > system update and start installing the ota without issues.
The codes :
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
Guess that every patches on mi a2 will work with thus method, haven't tested with any version other than august patch. Let me know if it's work !
pani690 said:
Can't flash through miui flasher. Is it possible to flash this through recovery?
Click to expand...
Click to collapse
Search google for mi a2 manually flash firmware.
The result that said "techdroider.com" will be the answer you looking for.
If you don't want to lose any data but still wanna update, remove line "fastboot....userdata.img"
No November update?
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
Flie link not exist plz give working link
I am using the ticwatch pro 2020. I tried to flash a custom firmware and now it wont boot into anything but fastboot. I was wondering if anyone could help me find the stock firmware files
No stock files are avaiable yet, you have to get it back to the repair center
Coaleb said:
I am using the ticwatch pro 2020. I tried to flash a custom firmware and now it wont boot into anything but fastboot. I was wondering if anyone could help me find the stock firmware files
Click to expand...
Click to collapse
https://mega.nz/#F!cVVBRaxL
[DECRYPTION KEY]
iZbWXMs8vabDW1szJz1hgg
- fastboot flash aboot aboot.img
- fastboot flash boot boot.img
- fastboot flash vendor vendor.img
- fastboot flash system system.img
- fastboot format userdata
- fastboot format cache
- fastboot flash recovery recovery.img
- fastboot reboot
Hello, what process did you exactly use? I don't think there is stock firmware available for this watch but maybe we can help you to get the custom one running.
Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.
don't format data before LOS16
HueyT said:
don't format data before LOS16
Click to expand...
Click to collapse
So, I should:
1. Flash LOS 16 without formatting data (I'm on Android 10)
2. Format data
3. Flash halium boot
4. Flash UBports GSI
I'll try that but I don't think it's a data problem, because I've already tried it and the zip was successfully installed - files it should copy were copied on data partition, I've checked this. But I'll try once more, without formatting data. Should I boot lineage after flashing?
Yeah, so I followed this and it worked. Thanks!
If anyone had the same problem, I'll write down all what I did:
0. Temporarily booted TWRP and installed it via zip (twrp-3.3.1-14-river)
1. Installed LOS 16 (lineage-16.0-20200127-UNOFFICIAL-river) without formatting data.
2. Booted LOS but it rebooted as the data wasn't formatted and i kept it booting until it booted into LOS Recovery to format data, so I just rebooted phone without formatting data and installed TWRP as in step 0.
3. Flashed halium-boot as boot image in TWRP and installed UBports installed v5 zip, also in TWRP of course.
4. Rebooted phone.
5. Now Ubuntu Touch booted succesfully. Unfortunately, it reboots after about 1 minute. So it's not stable enough at this time. Or maybe I'm doing something wrong, I'll try also another vendor image.
EDIT: I've just tried another vendor.img from newer LOS16 build. Worked fine, but sim doesn't work
Nick_Nicker said:
Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.
Click to expand...
Click to collapse
Did it occur to you to maybe link to what you're talking about? Where is this halium-boot port for River you're talking about? I see nothing in the main GSI thread about anything but the G7 Power. No results on google for halium-boot river or halium river point to anything but this thread, so I have no idea what you could possibly mean.
Check on https://build.lolinet.com/file/halium/
Here you can find GSI and halium-boot images from Erfan. He also posted it on XDA, here you can find all information about it: https://forum.xda-developers.com/pr...development/gsi-ubuntu-touch-ubports-t4110581
So, halium-boot.img is found on build.lolinet.com
But you can also build Halium 9 image if your device's kernel source is available, here's some info https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI)#how-to-install-gsi
Also it's very important to have Android 9 ROM installed before. However, stock Android 9 didn't work for me, I prefer LineageOS. So, just install Lineage and then the GSI and halium boot image. For Moto G7 also flash 'river-firmwares.zip' found on lolinet. It'll fix that weird vibration noise bug. For now, there are some visual glitches visible (also only on river), but it'll be fixed. Anbox is working if you have /data partition formatted in ext4 (not f2fs), so if you follow instructions, you can also run some Android apps. Unfortunately, for me internet connection inside Anbox doesn't work.
Thanks sorry I was just starting to feel a bit insane, that stuff is not indexed on google at all by the looks of it. Thank you.
So here is the process that worked for me.
I started with the stock rom.
1. Followed the full Lineage OS install instructions, including the partitions zip etc.
2. Installed Lineage OS on Slot B per the above instructions
3. Wiped data
4. Flash halium-boot.img
5. Flash GSI zip
Everything works perfectly including cellular functionality.
Followed the steps above. Is it possible to revert?
I followed the steps above, but I am have serious issues with the screen jitter. I have been looking all over the place to see if there is a way to revert back to android so that I can use my phone without the screen jitter. Does any one have any instructions on how to do this? I did turn on ADB mode on Ubuntu Touch but my computer does not see an adb device. Thank for any help.
Took me a long time to figure out too.
Main thing is, if you hold down Power and Volume Down, eventually it will reboot to the boot menu. Don't select anything, just plug it in, and you'll have fastboot.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware/moto/river/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. After this you should have a fresh phone you can unlock and try flashing again. THis also restored my OTA ability and I was able to get the Android 10 update without any issues.
fastboot oem lock begin
fastboot oem fb_mode_set
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 system.img_sparsechunk.10
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 vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
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 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 system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock
Click to expand...
Click to collapse