Related
Hello all,
I have a Zenfone 2 (ze551ML aka Z00A), with TWRP 3.02, with a broken usb port, so I can't connect it to a computer.
I'm trying to upgrade my bootloader, from a Lollipop bootloader to a Marshmallow Bootloader. (in order to upgrade to Lineage 14.1)
To do this, I have some files, which are supposed to be flashed using fastboot. The script is as follow:
Code:
fastboot flash splashscreen splashscreen_551.img
fastboot flash token bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
flash recovery TWRP-3.0.3-M3-Z00A.img
Since I can use that, I'l trying to do it from within TWRP, using it's Terminal.
1) The TWRP terminal provides a "flash_image" binary.
I guess I can do :
Code:
flash_image splashscreen splashscreen_551.img
flash_image fastboot droidboot_4_21_40_134.img
flash_image recovery TWRP-3.0.3-M3-Z00A.img
Is that correct ?
2) Is there a way to flash the other bin files ?
My TWRP doesn't have any binary like flash_token, flash_ifwi, or flash_dnx.
But maybe I can do flash_image token bom-token_ze551ml_4_21_40_134.bin ? (and so on)
3) The updated TWRP version I'm flashing (3.0.3-M3-Z00A) is supposed to be only compatible with the M bootloader.
Is it safe to only issue the commands listed in 1), or am I at risk of having an "incomplete" bootloader, by not flashing the ".bin" files ?
While I'm pretty sure that the ifwi is only baseband related, I don't know what bom_token and dnx are for.
Thanks for reading !
PS: Apologies is not the right forum to post. I feel like it is more related to TWRP than Zenfone2, but I can move to the Zenfone2 sub-forum if needed.
Download
Lenovo Yoga Book Android 6.0 ROM: androidfilehost.com/?fid=817550096634799507
Intel Flash Utility: 01.org/android-ia/downloads/intel-platform-flash-tool-lite
Custom Recovery: twrp.me/lenovo/lenovoyt_x703f.html
Magisk Root: magiskmanager.com
Flashing ROM
With the yoga book in recovery, either use the intel utility + json files to flash, or these commands to flash with adb tools with the files from the archive. To unlock bootloader, enable dev mode, then settings>developer>oem unlock.
Fastboot Flashing Commands:
fastboot flashing unlock
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Click to expand...
Click to collapse
Set Country Code
how to make Halo Keyboard work. Go into Contacts and create a random one, then type into search ####6020# then set country code. This also fixes the "easyimage-country code" error which causes OTA updates to fail. During your system setup process, if you get constant touchpal errors, go into system settings and disable Touchpal app.
OTA Updates
You should now be able to run thru 5+ OTA updates for a few hours till you're at 7.1. These require a locked boot. If you unlock it, then everytime there's a new update you'll have to unroot and relock.
Root
Download twrp and magisk from the above links
$ fastboot flashing unlock
$ fastboot flash recovery twrp.img
go into advanced sideload
$ adb sideload magisk.zip
To get a full Linux desktop experience with chrome with extensions and dev tools, I recommend the "Linux Deploy" and "Xserver" app to install Ubuntu desktop.
there`s already a thread for this here https://forum.xda-developers.com/yoga-book/how-to/yoga-book-yb1-x90f-android-how-to-flash-t3709930
thread closed
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash Bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Android 11 to Android 10 downgrade
It seems Motorola has disabled bootloader downgrade through Anti-Rollback in Android 11. The latest version of Android 11 (Q1-19-58-30-2) doesn't allow vbmeta to be flashed. Fastboot would return following error:
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 16
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
skritch said:
I have the Verizon Edge plus. I noticed that there is a VZW folder, which I am assuming is the Verizon firmware, and a Retail folder on the lolinet mirror. Can you flash the retail version on the Verizon version of the phone successfully and would it remove the Verizon bloat?
Click to expand...
Click to collapse
Also wanna know this
Disillusionedsal said:
Stock firmware are available on lolinet.
You can find the list of all Motorola Edge Plus firmware here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Select your region and download relevant firmware.
[Prerequisite]
- ADB
- Motorola Drivers
Extract zip into adb folder for convenience.
Paste following command in command prompt:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs12
fastboot flash Bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
These commands are also available in servicefile.xml for reference.
If you plan to relock the bootloader, first flash stock firmware and then relock the bootloader using
fastboot oem lock
Click to expand...
Click to collapse
How long is the "fastboot oem fb_mode_clear" command supposed to last? Left it for a lot of time and nothing happens, I check the bootloader logs and last log is erase:ddr. If I select Start from the menu using the up/down keys and the start button, it takes me to a screen where it says no valid firmware detected contact motorola support. Please help
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
snowman2765 said:
(bootloader) Invalid partition name Bluetooth- can proceed no further. Had to rescue as phone is a necessity
Click to expand...
Click to collapse
anybody?
if i want to downgrade to low version from high version, need to unlock bootloader??
snowman2765 said:
anybody?
Click to expand...
Click to collapse
Try use lowercase bluetooth
tha_mechanic said:
I haven't tried it yet but someone confirmed to me that you can flash the retail firmware on a Verizon variant. Yes it will remove the extra junk. No it will not make the bootloader unlockable
Click to expand...
Click to collapse
if the bootloader is unlocked does that mean it can be used with any carrier? what exactly would an unlocked bootloader enable?
Unlocked bootloader just allows you to flash custom .img on the device
This however wont fix the fingerprint scanner, that even if you did the workaround after unlocking ( https://forum.xda-developers.com/t/fix-fingerprint-not-working-after-bootloader-unlock.4214041/ ) , because you lost root after flashing stock and no way to edit the goodix files.
Anyway to properly return to stock and get fingerprint scanner back ?
EDIT: Nvm, the fix works properly with just skipping all the goodix part and doing all the CQA Menu Mode operations per the instructions.
Hello everyone,
I bought a Moto G Power that came with Android 11 and it's so laggy. I used to own this device on 10 and it was great. Well, I've downgraded to Android 10 successfully using the ROM files from Lenovo Rescue and Smart Assistant and flashing them with Platform Tools but afterrelocking the bootloader successfully using '.\fastboot oem lock' and rebooting the phone it says No OS is found. Is it even possible to relock the bootloader after downgrading on this device and booting into Android 10 even if it's an official firmware from Lenovo?
I'm using these instructions to flash the Android 10 files:
Moto G Power flashing guide
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9) Requirements: * Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and...
forum.xda-developers.com
Thanks everyone!
It's possible but you have to flash everything clean from adb using factory files found at https://mirrors.lolinet.com/firmware/moto/sofia/official/ There used to be an automated batch file for windows users I think, not sure since I use linux.
I'm sure there is a guide around somewhere for it regarding installing android platform-tools and the commands.
TaZeR369 said:
It's possible but you have to flash everything clean from adb using factory files found at https://mirrors.lolinet.com/firmware/moto/sofia/official/ There used to be an automated batch file for windows users I think, not sure since I use linux.
I'm sure there is a guide around somewhere for it regarding installing android platform-tools and the commands.
Click to expand...
Click to collapse
Yep I've tried that and also while on 10 and 11 I've pulled the ROM file folder from Lenovo rescue itself so I have the exact copy of the firmware. Still nothing. Weirdly when I'm on Android 10 and lock the bootloader I receive an error when using Lenovo Rescue to install Android 10 from them just to see what happens. Something about flash partition failed.
shylonite said:
Yep I've tried that and also while on 10 and 11 I've pulled the ROM file folder from Lenovo rescue itself so I have the exact copy of the firmware. Still nothing. Weirdly when I'm on Android 10 and lock the bootloader I receive an error when using Lenovo Rescue to install Android 10 from them just to see what happens. Something about flash partition failed.
Click to expand...
Click to collapse
I would forego anything to do with Lenovo Rescue, its unecessary and its automated process may be the thing at fault here. I suggest just grabbing the Android 10 factory files and flashing them manually with adb and see if the flash goes through that way. Just fished out the commands for you:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
I have a 2020 Chevy Bolt EV with Android Auto (AA) and a Moto G Power XT-2041-4 2020 (Sofia), which ran Moto's stock A10 out of the box, as I recall. But I immediately rooted it and flashed Bettle64's A11 Havoc ROM. Later, after Bettle6i discontinued Havoc it, I decided to flash LOS A11, but the installation got screwed up. So, I ran the Lenovo Rescue Tool, but ended up with Moto stock A11. I also learned that I must use Vasche's tool and downgrade to A10 in order to root and flash a custom ROM, again.
Also, my Sofia was unable to connect to Android Auto until recently, as explained below, which I attributed to being rooted and/or running a custom ROM.
Chevy recently installed a new software update which is supposed to ameliorate the infamous battery fire issue, but it apparently fixed the AA connectivity issue. So, my Sofia running stock A11 connects to AA.
I'm concerned that if if root the device and install a new ROM it will not connect to AA, again. Also, Moto recently announced that it won't upgrade the Sofia to A12, and I don't want to be stuck forever on stock A11.
So, I'd like to do the equivalent of a Nandroid backup of my current working stock A11 ROM for insurance before venturing forth to root/ROM the phone. Is that possible? Any other thoughts/ideas? Forgive the length.
Thanks
Honestly all the information you need is available on the first pages of some of these forums, just do a search, browse around.
In short I would just backup your important files and forget nandroid backup of android 11 if your going back to 10. You don't need any tools just download the android 10 factory firmware from lolinet mirrors: https://mirrors.lolinet.com/firmware/moto/sofia/official
Make sure you have your android adb software on your computer, adb reboot bootloader and run these fastboot commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
If your looking for a solid android 10 based custom rom may I suggest Ressurection Remix, it's been solid for me.
TaZeR369 said:
Honestly all the information you need is available on the first pages of some of these forums, just do a search, browse around.
In short I would just backup your important files and forget nandroid backup of android 11 if your going back to 10. You don't need any tools just download the android 10 factory firmware from lolinet mirrors: https://mirrors.lolinet.com/firmware/moto/sofia/official
Make sure you have your android adb software on your computer, adb reboot bootloader and run these fastboot commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
If your looking for a solid android 10 based custom rom may I suggest Ressurection Remix, it's been solid for me.
Click to expand...
Click to collapse
Thanks for this, but I'm unclear on 2 issues:
- Do you mean that I don't have to downgrade from A11 to A10 first?
- Flash with Fastboot or FastbootD?
Thanks again
jhford said:
Thanks for this, but I'm unclear on 2 issues:
- Do you mean that I don't have to downgrade from A11 to A10 first?
- Flash with Fastboot or FastbootD?
Thanks again
Click to expand...
Click to collapse
Yes you have to downgrade by using the Android 10 factory image, and this process is done with regular fastboot.