Related
Hi, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back.
To going back to Stock ROM from CM12.1, I extract the latest firmware and did
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
The Swift now is on the latest ROM, but I now have
Code:
C:\fastboot -i 0x2970 oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
How can I set "Device tampered: true" back to "false"?
cyaneo said:
Hi, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back.
To going back to Stock ROM from CM12.1, I extract the latest firmware and did
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
The Swift now is on the latest ROM, but I now have
Code:
C:\fastboot -i 0x2970 oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
How can I set "Device tampered: true" back to "false"?
Click to expand...
Click to collapse
First you should've thought about that. Second it is possible but no guarantees. I did it using the method @FindYanot told me to do when my device was bricked and device tampered was false but becareful. My imei was damaged after that. I used QXDM to fix it.Might I ask why ? Are you sending it in for repairs or something??
yasteellutch said:
First you should've thought about that. Second it is possible but no guarantees. I did it using the method @FindYanot told me to do when my device was bricked and device tampered was false but becareful. My imei was damaged after that. I used QXDM to fix it.Might I ask why ? Are you sending it in for repairs or something??
Click to expand...
Click to collapse
Yes, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back. But a damaged IMEI would be also a bad deal...
cyaneo said:
Yes, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back. But a damaged IMEI would be also a bad deal...
Click to expand...
Click to collapse
Oh damn sorry man. Umm try the method @FindYanot gave me but make an EFS Backup of your modem partition just for safety.
yasteellutch said:
Oh damn sorry man. Umm try the method @FindYanot gave me but make an EFS Backup of your modem partition just for safety.
Click to expand...
Click to collapse
where can I find the method or could you please explain the steps? also how to EFS Backup - should I use EFS Professional?
Thank you!
You don't need EFS Pro
If your device is rooted just get EFS Backup from playstore. Then open it and backup. Once that is done keep a copy of the backup on your PC. Well @FindYanots way helped me when I bricked my Swift and yours isn't bricked so I don't know how to help you unless it was bricked.
cyaneo said:
[...]How can I set "Device tampered: true" back to "false"?
Click to expand...
Click to collapse
@cyaneo : did you manage to change it back to "false"?
There is one partition called oem (/dev/block/mmcblk0p19),
would it be possible and help to restore stock one with fastboot (or dd)?
cyaneo said:
Hi, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back.
To going back to Stock ROM from CM12.1, I extract the latest firmware and did
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
The Swift now is on the latest ROM, but I now have
Code:
C:\fastboot -i 0x2970 oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
How can I set "Device tampered: true" back to "false"?
Click to expand...
Click to collapse
Device Tampered: False
Use @FindYanot method in my thread about device bricked. It works like a charm. Erase all partitions via fastboot then the device will appear as HS USB QDloader and use QFil to fix and device tampered is gone
cyaneo said:
Hi, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back.
To going back to Stock ROM from CM12.1, I extract the latest firmware and did
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
The Swift now is on the latest ROM, but I now have
Code:
C:\fastboot -i 0x2970 oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
How can I set "Device tampered: true" back to "false"?
Click to expand...
Click to collapse
Device Tampered: False
Use @FindYanot method in my thread about device bricked. It works like a charm. Erase all partitions via fastboot then turnoff and plug in .the device will appear as HS USB QDloader and use QFil to fix and device tampered is gone
yasteellutch said:
Device Tampered: False
Use @FindYanot method in my thread about device bricked. It works like a charm. Erase all partitions via fastboot then turnoff and plug in .the device will appear as HS USB QDloader and use QFil to fix and device tampered is gone
Click to expand...
Click to collapse
can't find this post...
cyaneo said:
can't find this post...
Click to expand...
Click to collapse
Here is the link: http://forum.xda-developers.com/cro...wift-hardbricked-help-unbrick-please-t3260184
Look at where @FindYanot says Open this link and tool and guide
cyaneo said:
can't find this post...
Click to expand...
Click to collapse
Here is the link: http://forum.xda-developers.com/cro...wift-hardbricked-help-unbrick-please-t3260184
Look at where @FindYanot says: Open this link and tool and guide
yasteellutch said:
Here is the link: http://forum.xda-developers.com/cro...wift-hardbricked-help-unbrick-please-t3260184
Look at where @FindYanot says: Open this link and tool and guide
Click to expand...
Click to collapse
So there is no way to reset tampered to false via flashtool, right? sorry the guide I found was in russian which I do not understand, also, I have no windows computer. I use linux.
Dior DNA said:
So there is no way to reset tampered to false via flashtool, right? sorry the guide I found was in russian which I do not understand, also, I have no windows computer. I use linux.
Click to expand...
Click to collapse
Must I make a thread on how to do it?
---------- Post added at 02:26 AM ---------- Previous post was at 02:26 AM ----------
Oh and I use Windows. Sorry @diordna
Yes, please - would be very helpfull!
Here you go
cyaneo said:
Hi, cause of some dead Pixels on my 4 Weeks old Swift I have to send it back.
To going back to Stock ROM from CM12.1, I extract the latest firmware and did
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
The Swift now is on the latest ROM, but I now have
Code:
C:\fastboot -i 0x2970 oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
How can I set "Device tampered: true" back to "false"?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
cyaneo said:
can't find this post...
Click to expand...
Click to collapse
Do the guys behind the wiley phony really deny the warranty on the physical screen if the tampered switch was triggered ?
aparanoidpenguin said:
Do the guys behind the wiley phony really deny the warranty on the physical screen if the tampered switch was triggered ?
Click to expand...
Click to collapse
As allways: unlocking, rooting, etc. = loosing waranty (that's what the wileyfox-support also told me)
My friend I need your help, I have a moto g8 play (xt 2015-2). After resetting the phone, it shows the following message.
HTML:
Start up failed
You devices didn't start up successfully. Use the software repair assistant on computer to repair you device.
connect you device to you computer to get the software repair assistant.
AP Fastbook Flash Mode (Seceure)
No Bootable A / B Slot
Please !! Can anyone help me fix this problem?
aureliolk said:
My friend I need your help, I have a moto g8 play (xt 2015-2). After resetting the phone, it shows the following message.
HTML:
Start up failedYou devices didn't start up successfully. Use the software repair assistant on computer to repair you device.connect you device to you computer to get the software repair assistant.AP Fastbook Flash Mode (Seceure)No Bootable A / B Slot
Please !! Can anyone help me fix this problem?
Click to expand...
Click to collapse
Try LMSA's Flash/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try LMSA's Flash/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I can't find the moto g8 play model in the LMSA.
help me plzzz
aureliolk said:
I can't find the moto g8 play model in the LMSA.
help me plzzz
Click to expand...
Click to collapse
They must not have add it yet.
Run
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
I've posted some info on this here.
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Then find firmware at
https://mirrors.lolinet.com/firmware/moto
Then flash the firmware with something like this,
But you will need to compare with the
Flash_file.xml in the firmware folder
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
Sent from my ali using XDA Labs
sd_shadow said:
They must not have add it yet.
Run
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
I've posted some info on this here.
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Then find firmware at
https://mirrors.lolinet.com/firmware/moto
Then flash the firmware with something like this,
But you will need to compare with the
Flash_file.xml in the firmware folder
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I did this and still in bootloop, doesnt matter if i change to slot A or B, its still boot thenivrate and restart
doesnt matter the firmware version that i use, the bootloeader is unlocked and it still say "no bootable a/B slot"
RSDlite doesnt charge any flashfile from the firmwares that i downleaded,
think i just killed the phone, could u help me please @
anyone know if there is a blankflash for this device? like to wipe all from the device and flash a nwe firmware, sometimes i get it to work, bot just keep in a bootloop..
But it seems this forum is pretty empty sadd
Matiasfh01 said:
anyone know if there is a blankflash for this device? like to wipe all from the device and flash a nwe firmware, sometimes i get it to work, bot just keep in a bootloop..
But it seems this forum is pretty empty sadd
Click to expand...
Click to collapse
Even if there was a blank flash, unlikely you could get into EDL with those errors
ya, i dont know what else i can do, doesnt matter if use slot a or b, it just still in bootloop, and this device doesnt have a twrp
@aureliolk did you fixed your phone?
@sd_shadow nothing new bout that? could you gimme some tips please, now i need to fix that, cuz i broke the screen of my old moto g6 ((
tomorrow il ltry if i can get work rsd lite on a win7 pc, cuz is didnt worked on the laptop with win10
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZF522784QB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 32AA9F6547C0BDE1000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-13-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 3:10:57 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
(bootloader) ro.build.fingerprint[1]: 70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C70602
all: listed above
finished. total time: 0.007s
Click to expand...
Click to collapse
adrianosk8 said:
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
Click to expand...
Click to collapse
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my jerry_cheets using XDA Labs
sd_shadow said:
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
Thanks but my device is not in LMSA.
adrianosk8 said:
Thanks but my device is not in LMSA.
Click to expand...
Click to collapse
My bad forgot, it's the only newer device that isn't supported
Sent from my ali using XDA Labs
This resolved my problema about flashing the stock ROM. (Loop boot)
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
aureliolk said:
My friend I need your help, I have a moto g8 play (xt 2015-2). After resetting the phone, it shows the following message.
HTML:
Start up failed
You devices didn't start up successfully. Use the software repair assistant on computer to repair you device.
connect you device to you computer to get the software repair assistant.
AP Fastbook Flash Mode (Seceure)
No Bootable A / B Slot
Please !! Can anyone help me fix this problem?
Click to expand...
Click to collapse
solucion
Buenas noches, tengo el moto g8 play, trate de instalar un firmware mas atrazado, olvide desblquear el oem, al momento de dejarlo trabado se quedo con este frirmware
BUILD INFORMATION
SW Version: lima_32-user 9 PMDS29.70-81-3 a383d release-keys
MBM Version: MBM-2.1-lima_32_retail-210600d2e-200502
Modem Version: MT6771_V16.03.01.90R
SW Display Build ID: PMDS29.70-81-3
CQA Version: 6.0.4
Build Fingerprint: motorola/lima_32/lima:9/PMDS29.70-81-3/a383d:user/release-keys
Blur Version: Blur_Version.29.201.5.lima_32.retail.en.US
no encontre version mas reciente para componerlo, por suerte di con un archivo que ayuda con otro error, formateo el telefono y dejo datos de la version PMDS29.70-70-2
asi me permitio flashear la vesion PMDS29.70-81-3
despues del archivo, no es necesario ningun programa mas, solo baja e instala la rom directamente
el archivo se llama
"Moto_G8_Play_XT2015-2_Blankflash_Unbrick_Repair__Arquitetura_32_MT6771" solo pesa 4.91 Mb
lo encontre en google junto con el video de como usarlo
Motorola G8 XT2015-2 Play No Bootable A/B Sloot Solucion
I find myself in the same situation. I tried to reinstall firmware to repair severe lag and now I'm in a boot loop. My firmware was PMDS29.70-85-3 for a g8 play LATAM. I can get to fastboot, but that's as far as I get. Can anyone provide me with link to the correct flash? Thanks, PC
adrianosk8 said:
This resolved my problema about flashing the stock ROM. (Loop boot)
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
Thank's aloooot men
this help me with my motorola g8 play from claro honduras
also with this:
Blankflash Unbrick Repair Moto G8 Play_XT2015-2_Arquitetura_32_MT6771
and my firmware and now is running good
thank's again men!!!
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-190906
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZF522784QB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 32AA9F6547C0BDE1000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-13-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C55376
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 2 3:10:57 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
(bootloader) ro.build.fingerprint[1]: 70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C70602
all: listed above
finished. total time: 0.007s
Click to expand...
Click to collapse
adrianosk8 said:
Hi
my moto g8 (xt2015-2) went into boot looping after I tried to root using this tutorial:
https://www.getdroidtips.com/root-moto-g8-play/
I have already made several attempts to install several roms stocks, like these:
https://www.stockrom.net/2020/04/xt2015-2-pie-retail-latam-pmd29-70-81.html
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETAIL/
I used adb flash tools as the method in flashfile.xml inside the rom.
my device:
Click to expand...
Click to collapse
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Sent from my ali using XDA Labs
sd_shadow said:
You should be using
https://mirrors.lolinet.com/firmware/moto/lima_32/official/RETBR/
Click to expand...
Click to collapse
I already installed all these RETBR roms. None started. when the Motorola logo appears, the device restarts.
I was searching the net and I found some articles saying that it could be because the processor is MIDIATEK (MT6771V / WL). AND THAT WOULD HAVE TO DOWNLOAD MTK / Sp flashing tools:
https://flashtool.org/5/download-sp-flash-tool.html
to install the rom on devices with this processor.
then I installed this program, but it needs the rom to have a file called "mt6771-scatter- android-file.txt "- what my device's roms don't have.
So I found a program that would generate this file (mt6xxx -scatter-android-file.txt):
https://mega.nz/file/YAogUAAL#cAbYxrWcUODmyVLD6p2Oz-YTsxm9Fb61A0RUq6OmkYI
but as nothing is so easy in this life, the program does not identify my device. not even after I installed the MidiaTek drivers (MTK drivers):
I don't know what to do.
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash -u system_a system.img_sparsechunk.1 fastboot flash -u system_a system.img_sparsechunk.2 fastboot flash -u system_a system.img_sparsechunk.3 fastboot flash -u system_a system.img_sparsechunk.4 fastboot flash -u system_a system.img_sparsechunk.5 fastboot flash -u system_a system.img_sparsechunk.6 fastboot flash -u system_a system.img_sparsechunk.7 fastboot flash -u system_a system.img_sparsechunk.8 fastboot flash system_b system_other.img_sparsechunk.0 fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
did it work? and could you install magisk after that?
Matiasfh01 said:
did it work? and could you install magisk after that?
Click to expand...
Click to collapse
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.
adrianosk8 said:
Yes, It does. But i don't install the magisk after that because i don't want It happend the same error.
Click to expand...
Click to collapse
can u poste the final flashfile here pls
Matiasfh01 said:
can u poste the final flashfile here pls
Click to expand...
Click to collapse
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Watter flash het u gebruik?
adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i need the firmware i use to fix the xt2015-2 please brother I could not solve
I could not solve
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
you have saved my phone Bro!
this works..
Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?
BrenoSilva1997 said:
Does anyone have the controls for the moto g 8 xt2045-1 to flash the stock rom?
Click to expand...
Click to collapse
You can use LMSA to flash g8 stock rom
adrianosk8 said:
I managed to solve it!
The problem is that the system image is divided into 7 or 8 different files. And when you run the "flash" command it also deletes the previous file so you have to use the "-u" parameters right after the "flash". Only for system images and after the first part of the images. Code below. I hope it helps you.
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
hello, I know this is more than I year old but still I wanted to thank you for posting this solution, I was having a really hard time trying to fix my mom's phone and just with this all got solved, thank you
adrianosk8 said:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
Click to expand...
Click to collapse
i love u
My little sister gave me his phone because it was looping at bootlogo
I've flashed some firmwares before so i tried to fix it. I downloaded this firmware: https://mirrors.lolinet.com/firmware/moto/ocean/official/AMXMX/
and tried to flash it but i didn't work. Still bootlooping, tried with blankflash but none of this versions did anything, just <waiting for device> Blankflash i used: https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
i realized that the battery level screen don't displays anymore. when i connect it it's looping at electricity logo
Variables i think might know
version: 0.5
version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-210201
product: ocean
secure: yes
securestate: oem_locked
factory-modes: disabled
iswarrantyvoid: no
max-download-size: 536870912
imei: [I hide it for security but i got one]
carrier_sku: XT1955-2
ro.carrier: amxmx
running-boot-lun: 0
slot-successful:_a: No
slot-successful:_b: No
slot-bootable:_a: No
What could i do?
Lol, i just solved it
Tried with Lenovo/Moto smart assistant : https://support.lenovo.com/us/en/downloads/ds101291
Flashed but not worked at all (but It's an important step), then i downloaded https://drive.google.com/file/d/1LzWEzxSbg56GqIZaVHj8WxbuTMNWfzKb/view
and ran this commands on cmd
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
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 dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.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 vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
Not all commands worked but cmd skip those, then the phone worked again
I got a problem with the IMEI (I'ts 'unknow') but i can't flash another NON-HLOS.bin file (The correct for my firmware version)
At least it works for wifi usage
Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.
Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.
Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.
I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.
The following partitions have the same content:
Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode
The following partitions have different content:
Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a
In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:
Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs
With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.
The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.
When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.
TLDR:
fastboot flash ocdt ocdt_CPH2449.img
Known issue:
- BeiDou satellite is not available under Oxygen OS.
sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
Amazing find, so just need to flash this img once and everything will work even OTA? How about lock the BL
JimmyTian said:
Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.
Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.
Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.
I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.
The following partitions have the same content:
Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode
The following partitions have different content:
Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a
In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:
Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs
With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.
The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.
When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.
View attachment 5905297
Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.
TLDR:
fastboot flash ocdt ocdt_CPH2449.img
Known issue:
- BeiDou satellite is not available under Oxygen OS.
sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
Click to expand...
Click to collapse
Hi Jimmy,
Can you share the screenshot of the Settings showing up the phone ? Does it show CPH model as CPH2449 ?
We will need also the ocdt ocdt_CPH2451.img for those who want to convert to US Oneplus 11.
Last point: why don't we also flash the remaining imgs that are different like :
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs in order to get a fully converted device?
Steve
Flashed and can confirm auto brightness works well, amazing works
sunxutian said:
Amazing find, so just need to flash this img once and everything will work even OTA? How about lock the BL
Click to expand...
Click to collapse
I'm not sure if it is a general method or if I accidentally changed something during my testing that made it work on my device, but it did. More testing is therefore required.
I tried upgrading from A.09 OTA to A.10 and it seems to be working fine.
I also tried unlocking and relocking the bootloader and it seems to be working fine as well.
JimmyTian said:
I'm not sure if it is a general method or if I accidentally changed something during my testing that made it work on my device, but it did. More testing is therefore required.
I tried upgrading from A.09 OTA to A.10 and it seems to be working fine.
I also tried unlocking and relocking the bootloader and it seems to be working fine as well.
Click to expand...
Click to collapse
Nice work again, so we should be able to lock the BL and OTA fine without any issues
Steve0007 said:
Hi Jimmy,
Can you share the screenshot of the Settings showing up the phone ? Does it show CPH model as CPH2449 ?
We will need also the ocdt ocdt_CPH2451.img for those who want to convert to US Oneplus 11.
Last point: why don't we also flash the remaining imgs that are different like :
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs in order to get a fully converted device?
Steve
Click to expand...
Click to collapse
Regarding the provided partition images, thank you very much!
Both the CPH2447 and CPH2449 images are working properly. The version which is displayed is determined by the version you have flashed.
Perhaps this partition is the same in the international version? We need more feedback.
Baseband is one of the hardware-limited components, so flashing images that is incompatible with the hardware might result in problems like no signal and broken Wi-Fi.
I therefore considered merely making the most minimal changes to the system.
Does it still randomly shut down? I had this problem when I converted to oxygen Os.
JimmyTian said:
Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.
Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.
Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.
I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.
The following partitions have the same content:
Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode
The following partitions have different content:
Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a
In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:
Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs
With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.
The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.
When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.
View attachment 5905297
Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.
TLDR:
fastboot flash ocdt ocdt_CPH2449.img
Known issue:
- BeiDou satellite is not available under Oxygen OS.
sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
Click to expand...
Click to collapse
I have flashed your ocdt img to my OP11 that is converted from PHB110 to CPH2447. Auto brightness is working well and there is no major trouble so far. Thanks for your effort.
Let me understand something, if we flash this OCDT file we can boot with OxygenOS oplusstanvbk (without flashing the ColorsOS one), right ?
And another thing, since it _thinks_ we are on the OG European OnePlus 11 model, there should be a way to find how to bypass the region lock that way, right ?
Thanks again, I aslo compare the two images, find this way will work ,thanks
Hi
Does fingerprint authentication work?
And does it mean to flash OCDT instead of flashing color os oplusstanvbk?
Thank you for your work.
Hi
I tried to convert from ColorOS to CPH2449 last night.
I installed the A09 version through Fastboot Enhanced, then flashed ocdt img. The phone got bootlooped at the oneplus logo screen.
Then I flashed the oplusstanvbk from the coloros A09 rom, and the phone booted successfully.
Not so sure what I did wrong, but in my case, I still had to flash the oplusstanvbk for it to work.
i can confirm auto brightness works, and no need to flash oplusstanvbk from cos.
but i still can't get fingerprint to work, during fingerprint enrollment there is no sensor light popup but just typing vibrating like continuously.
esim also not working, won't enable during attempt.
Delete
Delete
oprocks said:
i can confirm auto brightness works, and no need to flash oplusstanvbk from cos.
but i still can't get fingerprint to work, during fingerprint enrollment there is no sensor light popup but just typing vibrating like continuously.
esim also not working, won't enable during attempt.
Click to expand...
Click to collapse
Hi, I actually have a brand new CN OnePlus 11 waiting to be flashed - would you mind to share the steps you did and I will try maybe tomorrow and post the result back?
Regards,
t0ng00 said:
Hi, I actually have a brand new CN OnePlus 11 waiting to be flashed - would you mind to share the steps you did and I will try maybe tomorrow and post the result back?
Regards,
Click to expand...
Click to collapse
1. unlock bl
2. use fastbooteh to flash 2449's payload.bin
3. flash ocdt mentioned in start of this thread
4. lock bl
that's all.
i flashed back cos, wifi no longer worked there. it seems this ocdt messed up wifi back in original cos, something in the baseband got changed?
mhoang99 said:
Hi
I tried to convert from ColorOS to CPH2449 last night.
I installed the A09 version through Fastboot Enhanced, then flashed ocdt img. The phone got bootlooped at the oneplus logo screen.
Then I flashed the oplusstanvbk from the coloros A09 rom, and the phone booted successfully.
Not so sure what I did wrong, but in my case, I still had to flash the oplusstanvbk for it to work.
Click to expand...
Click to collapse
Did you factory reset the smartphone after flashing Oxygen OS?