Database Info

marshmallow 6.0.1 to stable lollipoo

hi guys ,
i want to downgrade my marshmallow current stock rom to lollipop please provide the steps to do it as i am facing battery issues in mm, and my device is rooted and twrp installed and also using xposed framework in mm do i need to uninstall framework please let me know steps thanks

Download Fastboot flashable image from here:
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then flash everything:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
fastboot reboot
Click to expand...
Click to collapse

Anyone with a Moto g7 Power XT1955-4?

Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.

Ballyeet said:
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Click to expand...
Click to collapse
Me bro... See:
xe500linux said:
Whats the difference between fastboot -w and just wiping everything in Twrp? That could have been it.. Syber makes the official Twrp as well so dont know if the one in OP is any different
And theres 4 roms btw, Havoc OS has no thread but its on Syber's androidfilehost. Same rgb/display issues as Lineage though
Click to expand...
Click to collapse
bruh you dont even have to use the fastboot -w or wipe command
CREATOR OF POST: MY F***IN BAD my speak problem was some bs from a blank flash i sorted it now the only bugs i got in some sketchy nav bar
there are apparently these roms as well:
CARBON-CR-7.0-OPAL-UNOFFICIAL-ocean-20191025-1317.zip
Viper-ocean-20191029-v6.7-UNOFFICIAL.zip
XenonHD-191024-Unofficial-ocean.zip
---------- Post added at 09:53 AM ---------- Previous post was at 08:54 AM ----------
FULL GUIDE TO DEBRICK/INSTALL STOCK ROM/REMOVE BAD KEY/INSTALL CUSTOM ROM AND TWRP
ensure your google accounts are removed from the phone and bootloader is unlocked...
boot to bootloader
run cmd prompt
use cd C:\*LOCATION* to go to folder with full STOCK ROM but make sure you have this files in the folder too [adb.exe, fastboot.exe, adbwinapi.dll, adbwinusbapi.dll] from ur minimal adb and fastboot setup. you will also need the recovery file TWRP-ocean-3.3.1-Syber-v2.2_11-02.img in this folder and the logo.bin file to remove the bad key FROM HERE. I suggest you rename to logonew.bin and put in the stock rom folder. you will also want ur RRromzip, the copypartitions.zip, the TWRP INSTALLER, GAPPS & MAGISK ZIP...
no matter what stage u are at other than bricked [after the BLANK FLASH then resume with this guide. if ur stuck bootlooping or have messed anything up start from the stock rom install or you will end up bricking your phone....
ok so in your cmd open in stock rom folder type these commands:
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_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
fastboot reboot-bootloader
when it reboots to bootloader use these commands from the same folder:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now use these commands to remove bad key
fastboot flash logo_a logonew.bin
fastboot flash logo_b logonew.bin
now boot the twrp by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
when twrp boots it should show up in ur windows explorer if you have an sd card just drop the files you need on it or you will have to use command adb push copy-partitions-payton.zip /sdcard/
install the copy-partitions-payton.zip
when complete reboot-bootloader
now boot the twrp again by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
now install the rom zip
then the twrp installer zip
reboot-recovery [it auto switches slot]
install gapps and magisk zips
reboot system
you should have ur custom rom and twrp recovery permanently installed now

Thanks for this guide! Does it work with official TWRP?
One more question: I have the RETEU Version, wich zip should i pick? The PPO or the PPOS Version?
thanks in advance!

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?

How To Guide How to downgrade back to 11 from 12

This guide is for anyones like me that wants to go back to Android 11 from 12.
Prerequisites:
unlocked bootloader
Your phone's Android 11 firmware
Ability to get into fastboot and type commands one at a time hitting ENTER after each line
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 vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
flash bluetooth BTFM.bin
flash dsp dspso.bin
flash logo logo.bin
flash boot boot img
flash vendor_boot vendor_boot.img
flash dtbo dtbo.img
flash super super.img_sparsechunk.0
(This flash took almost 15 seconds to finish. Continue flashing sparsechunk.1 thru sparsechunk.11 one at a time.
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
I had to flash both a & b slots to get this to stick. Disable updates to avoid problems.

Question Firmware updates

As most of you probably know, so now and then the firmware of our G100 is updated when using the official OS. I noticed that there is a new firmware (1.4) out:
https://mirrors.lolinet.com/firmware/motorola/nio/official/RETEU/
A question about updating the firmware when already using an alternative OS like LOS or Evolution; how to do that?
Is it enough to flash radio and bluetooth, or do we have to flash other parts also (without loosing our OS install), so:
Code:
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
And do we have to use the copy-partitions.zip then afterwards or not?
Code:
adb sideload copy-partitions-2022xxxx-signed.zip
The parts I flashed before a completely fresh LOS to have the latest original firmware (after I had some issues...):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.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 userdata
fastboot erase ddr
fastboot oem fb_mode_clear
I hope someone can help solving the mystery... ;-)

Can't seem to install the new firmware at all, and now bricked........any solutltios would be appreciated

Ok, did some research on the internet and though I am still not 100 percent sure about A/B I did the following which seems to do the job:
UPDATE PROCESS FIRMWARE WITHOUT LOOSING YOUR CUSTOM ROM INSTALL / DATA:
First reboot into bootmenu (fastboot)
Then:
Code:
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 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 reboot
So I did not erase any partitions, though when looking into servicefile.xml in the firmware I probably should do:
fastboot erase mdmddr
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot erase carrier
>> Someone knows?
Some references:
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

FYI;
I just asked the same question in the topic https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/ as it seems a better place to ask these in-detail technical questions.
Probably this topic can be closed or removed now...