My system crashed and I can't do anything with fastboot(access denied). But I watched a video that if I can play the same rom it might work. Does anyone have this rom version of the moto g8 power?
version-bootloader: MBM-3.0-sofiar_retail-0f8934adaf-210928
version-baseband: M6125_43.45.03.48R SOFIA_LATAMDSDS_CUST
I've already searched the main google sites.
C:\Users\charl\Desktop\platform-tools> fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiar_retail-0f8934adaf-210928
(bootloader) product: sofiar
(bootloader) board: sofiar
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF5233S5VJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 9B49D2F1
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 353623111368835
(bootloader) imei2: 353623111368843
(bootloader) meid:
(bootloader) date: 08-15-2020
(bootloader) sku: XT2041-1
(bootloader) carrier_sku: XT2041-1
(bootloader) battid: SB18C64833
(bootloader) battery-voltage: 4099
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_retail/sofiar:11/R
(bootloader) ro.build.fingerprint[1]: PES31.Q4U-47-35-9/54bc43:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.11.r1-02100-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.48R SOFIA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.180-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue S
(bootloader) kernel.version[4]: ep 28 11:07:44 CDT 2021
(bootloader) git:xbl: MBM-3.0-sofiar_retail-1186df2c3-210928
(bootloader) git:xbl_config: MBM-3.0-sofiar_retail-1186df2c3-210928
(bootloader) git:rpm: MBM-3.0-sofiar_retail-2579863-210928
(bootloader) git:tz: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:hyp: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:devcfg: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:cmnlib: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:cmnlib64: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:keymaster: MBM-3.0-sofiar_retail-7bae8fe-210928
(bootloader) gitrov: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) git:abl: MBM-3.0-sofiar_retail-0f8934adaf-210928
(bootloader) git:qupfw: MBM-3.0-sofiar_retail-7c7ba69-210928
(bootloader) git:uefisecapp: MBM-3.0-sofiar_retail-a41049fe-210928
(bootloader) frp-state: protected (144)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 4
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C65089
(bootloader) primary-display: tm_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.106s
What kind of moto g power is it? Can you still get into bootloader?
When I'm asking this what service was it bought under?
Your baseband and bootloader say that it is a sofia and a sofiar? did you make a backup first with rescue and smart assistant?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
that could be the right one, but if its not you can hard brick it. I got lucky I accidentally flashed my visible g power with the vzw 10 one thinking that'd work...
Mine is actually the sofia Retus builds.... Retus stands for no carrier....
if your not on any of the carriers listed id try retus first if you don't have a backup....
Whatever carrier you got your phone with at certain time of year try googling that with xda or duckduck go....
Also use latest version! https://github.com/Vachounet/moto_flash_toolhttps://github.com/Vachounet/moto_flash_tool
to flash a stockrom from the bootloader.....
I wish they had better guides here. Also save yourself some headache, I tried to use twrp and I'd just recommend to not use it. Use fastbootd instead...
There is no how to guide in here just grab the how to from whatever rom your downloading.
Be sure to flash a android 10 stock rom not a 11. All of the customs here are based on 10....
I swear it took me hrs of reading just to gather all of that intel and why they don't have a guide here for new people is beyond me....
revengesrage said:
... Retus stands for no carrier....
Click to expand...
Click to collapse
More precisely Retail US, which means the unbranded US version
revengesrage said:
What kind of moto g power is it? Can you still get into bootloader?
Click to expand...
Click to collapse
sofiar xt2041-1 64 gb pvt (from brazil). Yes, but flashing_lock :/ I can't run anything, access is always denied.
revengesrage said:
When I'm asking this what service was it bought under?
Click to expand...
Click to collapse
I didn't really understand the question, I'm translating it.
revengesrage said:
Your baseband and bootloader say that it is a sofia and a sofiar? did you make a backup first with rescue and smart assistant?
Click to expand...
Click to collapse
Yes, baseband sofia and bootloader sofiar_retail-0f8934adaf-210928. I didn't backup.
revengesrage said:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
that could be the right one, but if its not you can hard brick it. I got lucky I accidentally flashed my visible g power with the vzw
Click to expand...
Click to collapse
I'm traying flashing several roms, so far without success.
revengesrage said:
10 one thinking that'd work...
Mine is actually the sofia Retus builds.... Retus stands for no carrier....
if your not on any of the carriers listed id try retus first if you don't have a backup....
Whatever carrier you got your phone with at certain time of year try googling that with xda or duckduck go....
Also use latest version! https://github.com/Vachounet/moto_flash_toolhttps://github.com/Vachounet/moto_flash_tool
to flash a stockrom from the bootloader.....
I wish they had better guides here. Also save yourself some headache, I tried to use twrp and I'd just recommend to not use it. Use fastbootd instead...
There is no how to guide in here just grab the how to from whatever rom your downloading.
Be sure to flash a android 10 stock rom not a 11. All of the customs here are based on 10....
I swear it took me hrs of reading just to gather all of that intel and why they don't have a guide here for new people is beyond me....
Click to expand...
Click to collapse
I need the exact rom to make the cell come back to life. :/
{
"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"
}
:/
EDIT: Looking at your first post again, looks like your bootloader is locked.... if it is
EDIT" If you skipped unlocking your bootloader theres a guide on here for unlocking the bootloader.
Since you still have access to your bootloader refer to that guide and unlock the ***** and then jump back to these instructions....
according to that picture you shared your using the wrong stock rom. I love rescue and smart assistant hehe. Give this one a shot here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
or more specifically, since your trying to go custom use this link below.
Download BELOW!
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Also since you can get into the regular boot loader follow these instructions
below...
Download this
moto_flash_tool_windows_v0.6.6.zip | by Vache for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
extract to folder on desktop
copy zip from above into firmware folder
"Firmware Folder Example"
moto_flash_tool_windows\firmware\XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
"firmware folder example"
on phone hold vol - and power key to enter bootloader
on pc run moto_flash_tool-win.exe from within moto_flash_tool_windows
if it doesn't run, redownload the tool and reextract it again using a different zip program, reboot pc......
select flash/extract stock firmware
and choose your firmware in the folder.
Let the process run till your phone reboots a couple of times, Don't interrupt it as it will take 5-10 min to do its thing. the first reboot you'll see the software do is bring you into fastbootd and then flash a couple more things. So its going to do all the work on auto pilot....
After you do all of this, DO NOT USE TWRP! If you do don't flash it and don't reboot from side "B!" it will BRICK...
Good luck....
revengesrage said:
EDIT: Looking at your first post again, looks like your bootloader is locked.... if it is
EDIT" If you skipped unlocking your bootloader theres a guide on here for unlocking the bootloader.
Click to expand...
Click to collapse
I can't activate oem unlocking and usb debugging because I can't access the system which is broke. And as a consequence I can't unlocking the bootloader.
revengesrage said:
Since you still have access to your bootloader refer to that guide and unlock the ***** and then jump back to these instructions....
Click to expand...
Click to collapse
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_retail/sofiar:11/R
(bootloader) ro.build.fingerprint[1]: PES31.Q4U-47-35-9/54bc43:user/rele
I have a question, why can't I find a rom with the same specification? I've looked everywhere.
there are several roms.... ex: RPES31.....QPES31 ........less than I want. (PES31.Q4U-47-35-9). <----
(bootloader) version-bootloader: "MBM-3.0-sofiar_retail-0f8934adaf-210928" <----
The only way to bring my cellphone to life is to get this rom that I update in motorola.
revengesrage said:
according to that picture you shared your using the wrong stock rom. I love rescue and smart assistant hehe. Give this one a shot here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
or more specifically, since your trying to go custom use this link below.
Download BELOW!
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Also since you can get into the regular boot loader follow these instructions
below...
Download this
moto_flash_tool_windows_v0.6.6.zip | by Vache for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
extract to folder on desktop
copy zip from above into firmware folder
"Firmware Folder Example"
moto_flash_tool_windows\firmware\XT2041-1_SOFIAR_RETBR_10_QPES30.79-124-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
"firmware folder example"
on phone hold vol - and power key to enter bootloader
on pc run moto_flash_tool-win.exe from within moto_flash_tool_windows
if it doesn't run, redownload the tool and reextract it again using a different zip program, reboot pc......
select flash/extract stock firmware
and choose your firmware in the folder.
Let the process run till your phone reboots a couple of times, Don't interrupt it as it will take 5-10 min to do its thing. the first reboot you'll see the software do is bring you into fastbootd and then flash a couple more things. So its going to do all the work on auto pilot....
After you do all of this, DO NOT USE TWRP! If you do don't flash it and don't reboot from side "B!" it will BRICK...
Good luck....
Click to expand...
Click to collapse
The stock rom your referring to is this one. " You really can't figure out that rescue and smart assistant shows your ro carrier as retbr?" I'm being really nice about giving you the same location and everything on it. In Fact I'd say your pretty go lucky that the same one is there.
I'm gonna be a good human here and give you the link again.
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_11_RPES31.Q4U-47-35-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Your phone is not retail it is RETBR. look at the 47 35 9. I forgot about checking the unlock option in the developer options. Actually you don't need usb debugging. If it is retail go get it! Go TRY IT! all the stock roms are there....
If I were You I'd try to load this stock rom through rescue and smart assistant first. If it don't work then also try the moto flash tools.
if you don't know how to put the stock rom there google it...
I showed you the links and pointed out that your retbr. Its up to you to figure this mess out that you created now.
revengesrage said:
The stock rom your referring to is this one. " You really can't figure out that rescue and smart assistant shows your ro carrier as retbr?" I'm being really nice about giving you the same location and everything on it. In Fact I'd say your pretty go lucky that the same one is there.
I'm gonna be a good human here and give you the link again.
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETBR/XT2041-1_SOFIAR_RETBR_11_RPES31.Q4U-47-35-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Your phone is not retail it is RETBR. look at the 47 35 9. I forgot about checking the unlock option in the developer options. Actually you don't need usb debugging. If it is retail go get it! Go TRY IT! all the stock roms are there....
If I were You I'd try to load this stock rom through rescue and smart assistant first. If it don't work then also try the moto flash tools.
if you don't know how to put the stock rom there google it...
I showed you the links and pointed out that your retbr. Its up to you to figure this mess out that you created now.
Click to expand...
Click to collapse
Each folder is an attempt. I've tested almost everything, I think it's time to give up.
Anyway, I appreciate it, I really created the problem and it's up to me to solve it. Thanks!
colingbcc said:
View attachment 5455045
Cada pasta é uma tentativa. Já testei quase tudo, acho que é hora de desistir.
De qualquer forma, agradeço, realmente criei o problema e cabe a mim resolvê-lo. Obrigado!
Click to expand...
Click to collapse
olá queria saber se voce conseguiu resolver este problema?
LEVI TEC said:
olá queria saber se voce conseguiu resolver este problema?
Click to expand...
Click to collapse
Please use English on XDA
Google translation below.
LEVI TEC said:
Hi, I was wondering if you managed to solve this problem?
Click to expand...
Click to collapse
sd_shadow said:
Por favor, use o inglês no XDA
Tradução do Google abaixo.
Click to expand...
Click to collapse
hello I wanted to know if the problem was solved after I have a moto g8 power I tried to downgrade from android 11 to android 10 and the device simply does not turn on or connected to the charger it does not charge nor does the pc recognize it, can someone help me and me explain what happened, thank you in advance
LEVI TEC said:
hello I wanted to know if the problem was solved after I have a moto g8 power I tried to downgrade from android 11 to android 10 and the device simply does not turn on or connected to the charger it does not charge nor does the pc recognize it, can someone help me and me explain what happened, thank you in advance
View attachment 5553437
Click to expand...
Click to collapse
Managed to solve?
Related
I found it support qualcomm 9008. We can flash twrp for A6 then get root.
I bought fastboot ROM from taobao.com cost my 15$, I hope someone can make twrp in QPST 9008.
https://drive.google.com/file/d/1D3R531XnI52dzwHL21rRTGszs12on_sr/view
C:\Program Files (x86)\>fastboot getvar all
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3996
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B445F7800
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x148000000
(bootloader) secure:yes
(bootloader) serialno:5242da66
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.060s
We need twrp for hisense A6，someone can help with it? I want to do it but I dont' know how to do that.
I have the rom of current version and wonder how to make twrp....
You can get it free on the official forum of Hisense.
evilwjg said:
I have the rom of current version and wonder how to make twrp....
You can get it free on the official forum of Hisense.
Click to expand...
Click to collapse
Hisense official doesn't releases fastboot flashing ROM, only offers SD flashing ROM including 2 bin files. So please use my ROM.
yklaxds said:
Hisense official doesn't releases fastboot flashing ROM, only offers SD flashing ROM including 2 bin files. So please use my ROM.
Click to expand...
Click to collapse
You are right,I misunderstand of them.Thanks!
hi thank you for open qpst rom.
I made gapps rom by your rom.
working in progress
most of function working.
I will open gapps rom.
it is not working ota update. so old version only
if you can accuire latest rom.
let me know thanks.
joygram said:
hi thank you for open qpst rom.
I made gapps rom by your rom.
working in progress
most of function working.
I will open gapps rom.
it is not working ota update. so old version only
if you can accuire latest rom.
let me know thanks.
Click to expand...
Click to collapse
Does hisense deleted some apps? I dont know why I installed google play store and it not work(just always loading……). And does A6 rooted possiblely?
Thanks.
I don't root but modified system.img
and working all of them.
please wait. I'll open custom rom.
hisense a6 custom rom thread
https://forum.xda-developers.com/android/general/hisense-a6-l1488-6-4-01-custom-rom-t3932041
Sorry for my broken English,
Hey guys i just unlocked the boot-loader to install android 9.0 in it to just enjoy android PIE
and another day i didn't find that custom ROM stable so i flashed the android 7.0 nougat Rom in it through a video a guy posted(how to go back to stock Rom)
Stock Rom name - XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (this is the Rom that i had flashed)
and after that an OTA update just arrived and i quickly started downloading it and after it was going to update through restating the phone it just got hard bricked
i searched the whole day then got a fix through QCOM blank-flash file okayyy then went back to boot-loader,
and after this i have tried every moto g5 plus rom out there but none of it works
i have even tried to flashed the latest firmware
Name - XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but still the boot-loader says security version downgrade,
.
.
This is exactly what it says :
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.501s
.
i have tried to boot into recovery through TWRP and the Stock and had done everything but it loops in this
{ Your device has been unlocked and cant be trusted.
to learn more , visit motorola bla bla bla
ID: bad key
Your device will boot in 5 seconds. }
.
.
.
.
This is the fastboot getvar all about bootloader
-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2243GTRP
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 00409F3400000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351892082852554
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 13 20: 0: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
.
.
.
please guys every help is appreciated
thank you in advanceeeee
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
outis151 said:
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
Click to expand...
Click to collapse
thank you but still nothing is working
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
devhere_ said:
thank you but still nothing is working
Click to expand...
Click to collapse
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
Sent from my Moto G5 Plus using XDA Labs
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
yes exactly this way but no luck still looping in bootloader
Wolfcity said:
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
devhere_ said:
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
Click to expand...
Click to collapse
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
i cannot even boot into my recovery not stock nor TWRP
how can i attach that recovery.log here ??? if i could boot into twrp i"ll flash a custom rom but unfortunately i cannot boot into recovery
all i can do things is my boot-loader nothing else is working
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
coltswalker said:
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
coltswalker said:
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
Click to expand...
Click to collapse
Looks ok to me.
Maybe the boot.img you downloaded is corrupt.
Did the .zip look like right size?
I guess I would download the next newest firmware and try to flash that boot.img
If that works flash the rest.
I have some Windows instructions Linux should be the same.
[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
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version. Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
On another note: In all of the research I have done online with this model there are some sites that confuse sofia and sofiar as I have seen firmware for G advising sofiar which is clearly wrong. I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8. As I understand the model XT2041-4 is the G however some other sources online have it the other way. It is unfortunate that Motorola / Lenovo made the distinction of models of such similar hardware so confusing.
coltswalker said:
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
Click to expand...
Click to collapse
Yes
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
Click to expand...
Click to collapse
yes
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version.
Click to expand...
Click to collapse
I meant if it flashes without error, not fit boots.
Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
Click to expand...
Click to collapse
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8.
Click to expand...
Click to collapse
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
sd_shadow said:
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
Click to expand...
Click to collapse
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
coltswalker said:
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
Click to expand...
Click to collapse
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
justinr34gtr said:
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
Click to expand...
Click to collapse
Code:
fastboot reboot fastboot
Hi all,
I am a newbie to custom ROM's world and this is my attempt to it. My device is Moto G5s Plus.
To start with I had an encrypted phone running Android 8. Encryption was mandatory to install some work related apps. Because of sluggish performance I thought to install custom ROM.
Here are the steps I followed:
1. Installed minimal ADB on my laptop running Win10. Connected phone and successfully unlocked bootloader.
2. Rebooted phone in recovery mode and installed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'.
3. Rebooted the device and everything was working fine till now (restored from google backup and restarted several times to make sure things were working fine).
4. Now as I mentioned I need to encrypt phone for bussiness reasons. So I selected 'Settings->Encrypt Phone'. For very small time a green iconed screen appeared and then phone rebooted.
5. After reboot, a screen with google logo (G) with a small progress bar (kept moving left to right and vice-versa) appeared. I left it for more than 12 hours still hung at same screen.
6. Now I tried to wipe Dalvik/ART cache and cache. This is where problem started happening. I tried few other things (could not recollect exactly). I even tried to erase 'data' from fastboot using 'fastboot erase userdata'.
7. When nothing worked, I thought of installing Pixel Experience 11 plus again from TWRP. The process went smooth but towards the end it showed:
'Failed to mount '/data' (invalid argument)' error.
I am attaching snapshots and logs. Its been more than 3 days being stuck on this issue. Really appreciate any help.
Please let me know if any info is required.
Also since I dont have any data to worry about, so I am open to any suggestion (wipe/format). I have SD card and OTG with me.
Once the phone is up and running, I need to encrypt it back. So please suggest steps while keeping this requirement in mind.
Look for this issue on youtube and you'll find the steps to fix it.
It looks like you have a corrupt file system.
You can fix it using TWRP.
Good luck !
Hi,
I tried multiple steps to fix this issue but none helped.
As for now looks like I have made some progress. What I did was i flashed official firmware for Moto G5s plus as mentioned on below page:
Flash official firmware Moto G5s Plus [sanders]
So far, we have had the guides for you to unlock the bootloader in Moto G5s Plus or how to install TWRP on Moto G5s Plus and today, I am going to show you how to download and Install stock ROM in Moto G5s Plus. So if you probably have already...
forum.xda-developers.com
With this I got the device up and running with Android 7. Below is the full log of fastboot getvar all command:
<<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all > and7_var
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 4:57:41 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-4/4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.201.4.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g419eefd0-000
(bootloader) kernel.version[1]: 54-g1b4a83e ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Mon Oct 16 22:03:44 CDT 2
(bootloader) kernel.version[4]: 017
(bootloader) sbl1.git: git=MBM-NG-VC2.06-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) devcfg.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) keymaster.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib64.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) prov.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.121s
>>>
Now i have Android 7 up and running. Now I opened TWRP again, and flashed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'. Though this process works fine but after reboot it is again stuck at Google logo (G) screen.
Please help. I have spent 2-3 days working this out.
Regards.
Hey man.
In order to flash PE 11, like the ROM topic says, you "MUST" be on latest modem baseband ...
You "ONLY" obtain that by flashing the latest OREO 8.1 ROM.
So, you should flash latest Oreo you have and update it till there are no more updates.
Read PE 11 topic again. There you can find out about what i'm saying here.
Hope this helps and again,
Good luck !
Thanks a lot Damage1972 for showing the way forward
Between how did you figured out if this is the issue here?
Based on your suggestion, I flashed stock Android v8.1 and updated it till there are no updates. Phone was rebooting fine. After this, I flashed PE 11 plus and again phone is stuck at Google logo (G) screen.
Between below are logs:
<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 9:30:53 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.065s
>>
Please suggest.
Thanks and Regards.
No problem,man.
About the issue, it's listed on the pre requests in order to flash PE 11 !
It's very clear written on the first page and comments on the topic.
Carefully read the ROM's topic before flashing...
About your phone still stuck on boot : did you go through the steps to correct your phone file system ? And (sorry to ask you this) how did you flash the ROM ?
Did you do a Clean Flash ?
Check your messages.
Also, try this , that's what worked for me :
How to fix unable to mount data internal storage 0mb in twrp permanently :
Note : This will wipe/format your Data partion and your data will be reset. INSTRUCTIONS : 1) Reboot your device into TWRP Recovery. 2) Go to Wipe menu. 3) Go to Advance Wipe. 4) Select Data and go to Repair or Change File System. 5) Click...
forum.xda-developers.com
So few updates:
1. Looks like my mount data internal storage 0 mb issue is resolved (flashed stock ROM and then custom ROM and did not see this error).
2. Regarding how I flashed stock ROM Android 8.1. I downloaded 'Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0.zip' image from:
Motorola Moto G5S Plus XT1804 Stock ROM Firmware (Flash File)
Download the official Motorola Moto G5S Plus XT1804 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
and executed below commands in order:
<<
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition sanders81/gpt.bin
fastboot flash bootloader sanders81/bootloader.img
fastboot flash modem sanders81/NON-HLOS.bin
fastboot flash fsg sanders81/fsg.mbn
fastboot flash dsp sanders81/adspso.bin
fastboot flash logo sanders81/logo.bin
fastboot flash boot sanders81/boot.img
fastboot flash recovery sanders81/recovery.img
fastboot flash system sanders81/system.img_sparsechunk.0
fastboot flash system sanders81/system.img_sparsechunk.1
fastboot flash system sanders81/system.img_sparsechunk.2
fastboot flash system sanders81/system.img_sparsechunk.3
fastboot flash system sanders81/system.img_sparsechunk.4
fastboot flash system sanders81/system.img_sparsechunk.5
fastboot flash system sanders81/system.img_sparsechunk.6
fastboot flash system sanders81/system.img_sparsechunk.7
fastboot flash system sanders81/system.img_sparsechunk.8
fastboot flash system sanders81/system.img_sparsechunk.9
fastboot flash system sanders81/system.img_sparsechunk.10
fastboot flash oem sanders81/oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg sanders81/fsg.mbn
fastboot oem fb_mode_clear
fastboot reboot
>>
After that I was able to turn ON phone with Android 8.1.0. Checked for updates and installed them (i guess there were 3 security updates). Once done, entered bootloader and installed TWRP and flashed PE 11 plus. After reboot, it is again stuck at google logo (G) screen.
One more suggestion i need: Since I have spent a lot of time debugging this and ultimately I have to encrypt my phone. So below queries:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
andromeda1410 said:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
Click to expand...
Click to collapse
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Thanks sBinnala for help. At this point I am convinced that I will not install custom ROM. So I want to have stock ROM (Android 8.1) preferably.
Thing is yesterday I installed Android 8.1 stock rom (exact steps mentioned above), worked fine. Flashed PE 11 plus and phone got stuck at google logo screen. Searched again and though it to be some modem related issue hence I did below steps as mentioned on https://forum.xda-developers.com/t/rom-11-sanders-pixelexperience-normal-plus-aosp.4247243/ by Jorge:
<<
It is recommended that you are using the latest firmware for the Moto G (5S) Plus.
to update via twrp:
Modem only:
https://sourceforge.net/projects/ne...5-36-14_v2.0-modem-only_20210307.zip/download
Modem, Fsg & dsp:
https://sourceforge.net/projects/ne...S28.65-36-14_v2.0-modem_20210307.zip/download
>>
So I flashed Modem, Fsg & dsp: (second zip) and re-flashed PE 11 plus. Again that did not worked. Now again I tried to flash stock Android 8.1 ROM. It worked but now it is not detecting SIM., showing IMEI as 0 or not available.
I have found multiple pages on similar issue but none is working. Looks like this issue is because of persist file and epf partition which I dont have (infact i dont have any backup).
So can someone please help me in installing stock Android 8.1 which should work fine (sim should be detected). Any help will be deeply appreciated.
Edit: Tried installing Validus and following steps mentioned on https://forum.xda-developers.com/t/...ork-imei-0-after-flashing-custom-rom.3745474/ but issue not resolved.
If it matters, mine is 4 GB/64 GB, XT 1804 variant.
On some threads, i found inconsistency in architecture (like 32 bit and 64 bit). What is that? I know i have 32 bit TWRP running on a 64 bit Windows 10 machine. I am not sure about stock ROM architecture. Can someone tell me how to check stock ROM architecture?
On another notes: I have tried flashing below stock roms but none of them are working fine (device boots but unable to recognize SIM):
- Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0_Android8.1.zip
- SANDERS_NPSS26.116-26-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_Android7.zip
- SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- Stock-Sanders_OPS28.65-36-14_v2.0-modem_20210307.zip
- Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
Regards.
Further update:
Looks like I have created a backup using TWRP of original ROM (which was Android 8.1 but encrypted). Zipped it using Android app and then I transferred it to Windows laptop (later realized i should not have done it). Unzipped in android device and placed it in OTG. Restored using TWRP but it is not booting.
Can I do anything now? That is, should I preserve any file which I can later use with stock Android 8.1 ROM which can help me with getting sim signal/IMEI number back.
sBinnala said:
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Click to expand...
Click to collapse
Encryption works flawlessly with Arrow 11 vanilla.
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
okayk said:
Encryption works flawlessly with Arrow 11 vanilla.
Click to expand...
Click to collapse
Arrow isn't enforcing - it's permissive, which in itself is a huge security risk. Like I said, we don't have a ROM which supports both SELinux enforcing and encryption at the same time.
andromeda1410 said:
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
Click to expand...
Click to collapse
Normally in such cases, restoring EFS backup will do the trick. Have you already tried that?
After days of investigation, debugging and trying out everything which any post said, I have resolved my issue now. I now have a fully functional Android 8.1 installed on my phone, I am able to make calls, IMEI number is back.
In interest of wider public let me post what worked for me:
Note:
My device is Moto G5S Plus XT1804, 4 GB/64 GB, Retin Channel, India based phone. It is unrooted but has unlocked bootloader.
I have tried a lot many things, flashed many ROMs from different channels but none of them worked.
Below is what worked for me.
Probable issue: During flashing gpt.bin I was getting below error:
<<
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.074s
>>
I guess this is the core issue. I searched on it and got many forums. Finally below solution worked for me:
Downloaded stock Android 8.1 rom 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' for my device from: https://www.stockrom.net/2020/04/xt1804-retin-oreo-ops28-65-36-14.html
Unzipped this file and placed it at 'C:\Program Files (x86)\Minimal ADB and Fastboot'.
Created my own batch file using instructions mentioned in 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/flashfile.xml'.
Imp note: Do not use fastboot commands mentioned on any forum. Every rom (custom/stock) has a flashfile.xml or servicefile.xml. Open this file and create your own batch file with steps in order mentioned in xml file.
Booted my phone in fastboot mode (volume down + power). Connected phone with PC using usb cable.
Launch 'Minimal ADB and Fastboot' on windows PC. Note: i am attaching all tools that i used to rest version related questions.
Run the batch file you created in step #3.
With these steps, I was able to get my phone up and running. Thanks a lot to all members for their help.
Regards.
Reference links:
How to Restore Stock Firmware on Moto G (All Models)
Follow this guide to restore stock firmware on Moto G. The instructions will work for Moto G 1st Gen, 2nd Gen, 3rd Gen, 4th Gen, Moto G5/Moto G5 Plus, and Moto G5S/Moto G5S Plus. The Moto G series is…
www.thecustomdroid.com
G5s Plus XT1804 RETIN (SANDERS) 8 Oreo StockRom OPS28.65-36-14
Download Firmware + Tutorial Completo para Instalação Stock Rom Moto G5s Plus XT1804 (SANDERS) Android 8.1.0 Oreo Loop, Boot Infinito ou Hard Reset
www.stockrom.net
Tutorial – Instalação Stock Rom Motorola no Modo Fastboot (Snapdragon, Moto G, Moto E, Moto X, Moto Z, Moto C, Moto M, One) + Video Tutorial - Stock Rom
Como instalar firmware nos motorolas com processadores snapdragon, moto g1 ao g7, procedimento simples, instalador com 1 clique, sem linhas de comando.
www.stockrom.net
(These pages are in non-english. I used google translator for understanding it)
I stupidly locked my OEM and Flashing ability before wiping the disk through the bootloader, after a while of trying to get an operating system back on the phone and failing miserably due to the flashing being locked, the error I mostly seen :FAILED (remote failure). Now, I cant even get into Recovery Mode, it just goes to the Fastboot Flash Mode again. I can't flash or boot any disc, it wont let me unlock flashing or unlock the OEM again, even though i have the unlock code..
Is there anyway to get an operating system on my phone again? I just switched from xfinity to boost and it was working good all but some apps didnt work.
When you say you locked your OEM, did you re-lock your bootloader with a fastboot command or simply re-lock the OEM unlocking switch in Developer options in Settings? In the first case, you most likely now have an expensive paperweight - in the second case you may still be able to recover. Suggest you go to the Lolinet telegram channel and give a detailed description of what you did, what firmware version you were on and the output from the fastboot command: getvar all
Try booting into twrp but not flashing if you haven't on the off chance. Fastboot boot recovery (twrp.img). If that doesn't work try getting the unlock code from fastboot oem get_unlock_data and get the unlock code from Motorola again. If that doesn't work try getting it into edl mode and blank flash it with one of the blank-flash roms from here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work come back here and share your results. I agree share the "getvar all" command will be helpful to know more just delete your IMEI before posting
Update: I can now access the recovery boot option from the initial bootloader
lolinet seems to be down for me and everything I try results in an error
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.522s]
booting...
(bootloader) Fastboot boot command is not available in locked device
FAILED (remote failure)
finished. total time: 1.603s
fastboot oem unlock (the key from moto website)
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.083s
fastboot getvar all info
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-borneo_retail-22355d27121-22
(bootloader) version-bootloader[1]: 0601
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DP6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY22D68BLF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: 6F927615
(bootloader) token: inactive
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35689$%$&%*$&%*(
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 08-21-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4315
(bootloader) iccid: 89148000007142793377
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: comcast
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:11/R
(bootloader) ro.build.fingerprint[1]: ZBS31.Q2-143-27-13/b542c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-02200-KAMORTA.0
(bootloader) version-baseband: HA10_29.11.02.95.01R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[4]: un 1 01:20:19 CDT 2022
(bootloader) git:xbl: MBM-3.0-borneo_retail-df5e9403f-220601
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-df5e9403f-220601
(bootloader) git:abl: MBM-3.0-borneo_retail-22355d27121-220601
(bootloader) git:rpm: MBM-3.0-borneo_retail-834e250d-220601
(bootloader) git:tz: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:hyp: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:devcfg: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:keymaster: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) git:storsec: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-6bd3d249-220601
(bootloader) gitrov: MBM-3.0-borneo_retail-2b4edb90a-220601
(bootloader) git:qupfw: MBM-3.0-borneo_retail-d308e84-220601
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D12963
(bootloader) primary-display: tm_ili9881x_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.178s
snuffinaround said:
Try booting into twrp but not flashing if you haven't on the off chance. Fastboot boot recovery (twrp.img). If that doesn't work try getting the unlock code from fastboot oem get_unlock_data and get the unlock code from Motorola again. If that doesn't work try getting it into edl mode and blank flash it with one of the blank-flash roms from here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work come back here and share your results. I agree share the "getvar all" command will be helpful to know more just delete your IMEI before posting
Click to expand...
Click to collapse
not sure how to access this edl mode any tips?
withinwaves said:
not sure how to access this edl mode any tips?
Click to expand...
Click to collapse
Your problem is here in the getvar all : "(bootloader) securestate: flashing_locked"
First you'll have to download and install QDLoader_HS_USB_Driver_64bit_Setup.exe
In fastboot mode, try this command: fastboot oem edl
- other wise you'll have to use button combinations - you can google for a how to.
First, however, you might want to down load and try the
Rescue and Smart Assistant Tool - Motorolaif you haven't already, since you can get into fastboot mode.
Re-locking your bootloader is a big no-no ...
I repeat, if you re-locked your bootloader, you may now have an expensive paperweight - again, I suggest you get on the Lolinet Telegram channel - they have some VERY experienced core members who know their stuff when it comes to these problems, unlike some of the members here.
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Do you have download instructions for getting QDLoader_HS.. and installing? After it installs it doesn't seem to do anything.. fastboot oem edl prints "waiting for devices..." and never attaches to the phone. Thanks in advanced
sdembiske said:
Your problem is here in the getvar all : "(bootloader) securestate: flashing_locked"
First you'll have to download and install QDLoader_HS_USB_Driver_64bit_Setup.exe
In fastboot mode, try this command: fastboot oem edl
- other wise you'll have to use button combinations - you can google for a how to.
First, however, you might want to down load and try the
Rescue and Smart Assistant Tool - Motorolaif you haven't already, since you can get into fastboot mode.
Re-locking your bootloader is a big no-no ...
I repeat, if you re-locked your bootloader, you may now have an expensive paperweight - again, I suggest you get on the Lolinet Telegram channel - they have some VERY experienced core members who know their stuff when it comes to these problems, unlike some of the members here.
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Click to expand...
Click to collapse
withinwaves said:
Do you have download instructions for getting QDLoader_HS.. and installing? After it installs it doesn't seem to do anything.. fastboot oem edl prints "waiting for devices..." and never attaches to the phone. Thanks in advanced
Click to expand...
Click to collapse
You really must learn to Google ... a simple search could have yielded this ...
Link: https://www.droidwin.com/boot-android-edl-mode/
any further questions, log in to the Lolinet telegram channel and get help there.
P.S. It is a long standing XDA tradition to use the Like (formerly known as the Thanks button), bottom right of the post when you are logged in - please learn to use it when members try to help or provide directions, roms etc., for download.
sdembiske said:
You really must learn to Google ... a simple search could have yielded this ...
Link: https://www.droidwin.com/boot-android-edl-mode/
any further questions, log in to the Lolinet telegram channel and get help there.
P.S. It is a long standing XDA tradition to use the Like (formerly known as the Thanks button), bottom right of the post when you are logged in - please learn to use it when members try to help or provide directions, roms etc., for download.
Click to expand...
Click to collapse
Thanks for the response(s), I've spent a few hours now searching google for the solution. There are a few ways to fix this problem and yet some website are kind of scammy and may have resulted in increasing the severity of my phones issue. I truly do appreciate the help provided thus far but I haven't found a solution yet. Once I do I will surely hit the thanks button. Honestly downloading all these files and installing them may have bricked my phone so I want to find the proper solution before I express my gratitude. I will be sure to update you all once I've locked down the solution that best suits my problem, thanks for taking the time to try and understand my phones problem!
OK made some headway, turns out I was in edl mode this whole time but how do I boot to TWRP or install operating system from edl mode?
{
"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"
}
withinwaves said:
De acuerdo, hice algunos avances, resultó que estuve en modo edl todo este tiempo, pero ¿cómo iniciar TWRP o instalar el sistema operativo desde el modo edl?
[ADJUNTAR=completo]5707961[/ADJUNTAR]
Click to expand...
Click to collapse
puedo ayudarte a llegar a mi facebook Licandro Burzum y tratare de revivirlo