Related
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Insaniity said:
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Click to expand...
Click to collapse
can you provide more information please, (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n), but since you can't get to download mode, can we have some screenshots of bootloader, a copy/paste of your command prompt output when typing the fastboot commands
and most important, what were you trying to flash (link to thread and file please)
nkk71 said:
can you provide more information please, (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n), but since you can't get to download mode, can we have some screenshots of bootloader, a copy/paste of your command prompt output when typing the fastboot commands
and most important, what were you trying to flash (link to thread and file please)
Click to expand...
Click to collapse
I can do all command on bootloader so :
C:\minisdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA54SYJ03650
all:
Insaniity said:
I can do all command on bootloader so :
C:\minisdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA54SYJ03650
all:
Click to expand...
Click to collapse
that's what I meant with "usually" (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n, but since you can't get to download mode)
on the M9, the "fastboot getvar all" informational data, comes from download mode, not bootloader, so unfortunatly the above is quite useless,
let's go back to
* some screenshots
* copy/paste of fastboot commands (fastboot devices, fastboot oem rebootRUU, fastboot oem reboot-download)
EDIT: and what were you trying to flash (link to thread and file please)
nkk71 said:
that's what I meant with "usually" (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n, but since you can't get to download mode)
on the M9, the "fastboot getvar all" informational data, comes from download mode, not bootloader, so unfortunatly the above is quite useless,
let's go back to
* some screenshots
* copy/paste of fastboot commands (fastboot devices, fastboot oem rebootRUU, fastboot oem reboot-download)
Click to expand...
Click to collapse
Ok, I managed to get into download mode by writing this in bootloader mode ( I used the firmware 2.10.401.x )
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash cota cota.img
fastboot flash cpe cpe.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash modem_st1 modem_st1.img
fastboot flash modem_st2 modem_st2.img
fastboot flash persist persist.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
This is getvar
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.17
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
It is very strange, If i try to flash another firmware, for example 1.32.401.xx, after flashing I can't get to download mode again.
Insaniity said:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash cota cota.img
fastboot flash cpe cpe.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash modem_st1 modem_st1.img
fastboot flash modem_st2 modem_st2.img
fastboot flash persist persist.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
This is getvar
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.17
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
It is very strange, If i try to flash another firmware, for example 1.32.401.xx, after flashing I can't get to download mode again.
Click to expand...
Click to collapse
Please dont do firmware/low-level stuff that way, unless you are sure what you're doing
baseband has been updated to 2.10.401.1 firmware, obviously version-main wont reflect that change since it's not a "proper" flash... and serisously don't mess with "fastboot flash aboot, hosd, sbl, etc" .... you're heading into trouble
stop rushing things, relax, and take it one step at a time (slowly)
nkk71 said:
Please dont do firmware/low-level stuff that way, unless you are sure what you're doing
baseband has been updated to 2.10.401.1 firmware, obviously version-main wont reflect that change since it's not a "proper" flash... and serisously don't mess with "fastboot flash aboot, hosd, sbl, etc" .... you're heading into trouble
stop rushing things, relax, and take it one step at a time (slowly)
Click to expand...
Click to collapse
Ok, now I'm here.
C:\minisdk>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
I can access only to download mode and my firmware is ok.
It is matching with the download mode.
What should I do now?
Insaniity said:
Ok, now I'm here.
C:\minisdk>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
I can access only to download mode and my firmware is ok.
It is matching with the download mode.
What should I do now?
Click to expand...
Click to collapse
I'd recommend taking a break; I have no idea how you got there, because you keep forgetting that we need to know what you are flashing and how
for example, this is me flashing my firmware:
http://forum.xda-developers.com/showpost.php?p=62552232&postcount=646
and how I choose to copy/paste my information
^^ you don't need to follow those steps, I'm just saying you're going from:
I'm at location D ... okay now I'm at location K ... you're probably doing just fine, but not saying what and how you are flashing, it's difficult to help
nkk71 said:
I'd recommend taking a break; I have no idea how you got there, because you keep forgetting that we need to know what you are flashing and how
for example, this is me flashing my firmware:
http://forum.xda-developers.com/showpost.php?p=62552232&postcount=646
and how I choose to copy/paste my information
^^ you don't need to follow those steps, I'm just saying you're going from:
I'm at location D ... okay now I'm at location K ... you're probably doing just fine, but not saying what and how you are flashing, it's difficult to help
Click to expand...
Click to collapse
I know how to flash a firmware....
Now I'm tryng to flash a RUU
Insaniity said:
I know how to flash a firmware....
Now I'm tryng to flash a RUU
Click to expand...
Click to collapse
fine, have it your way
flashing RUU is exactly the same procedure as flashing firmware
but you continuously refuse to say, what you are flashing or how, if you look at my first reply, I asked for more details, including what you are trying to flash ("link to thread and file please")
{
"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"
}
I see some things change and some things never do
as a final hint (dont know if that's the case or not, since you wish not to share, the information), in a word: htc_fastboot.exe (try version 3.0.9.2)
do you try the ruu.exe or the zip? it will be MUCH better to use the zip. also mostly only the zip seems to work
DeeZZ_NuuZZ said:
...also mostly only the zip seems to work
Click to expand...
Click to collapse
elaborate, thank you
I have something similar, I flashed NoRedTxt_Aboot+2.11.531.19 once in my m9 tmo. Supposlly it flashed good. Now I can't get to download mode or ruu mode. In ruu mode after 1 sec it gets me back to download mode. Which is where it takes me everytime, besides that twrp is the other place I ca go too.
---------- Post added at 11:51 AM ---------- Previous post was at 11:44 AM ----------
Insaniity said:
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Click to expand...
Click to collapse
I'm stuck in same place as you. But different reason.I'm running stock 2.11.531.19 tmo m9. Just twrp s off and unlocked. What can I do to get to work again ruu or download again
Hello Guys,
I have a problem with my HTC M9 prime Camera Edition yesterday I paid 25 $ for S-Off with sunshine App everything was working great (great App thanks)
after that my phone was S-OFF i was excited and wanted to flash a other Stock Rom but something went wrong and my download mode is deleted now or not more availlable.
Information about my Phone: HTC_Himar 128 SHIP S-OFF
before CID was HTC__034 CID
before MID was 2PRG10000 MID
LK-1.01.0000
OS-2.18.401.10
Bootloader UNLOCKED
The device is rooted and recovery is twrp-3.0.2-0-himar
Android version: marshmallow 6.0
What i did is i wanted to flash the 3.35.401.12-Firmware to change my stock i did it with renaming the file in 0PJAIMG.zip and flashing with sd card in download mode
file could be not flashed some zip error displayed i rebooted the phone everything was ok no problems after that.
I also changed the MID before flashing to: OPJA10000 and CID to HTC__J15. After that i wanted to try it again with the firmware from xda forum 3.35.401.12-Firmware.zip
Phone was flashing the file after that i rebooted and i opened the developer options to check the firmware info but the firmware stayed the same 2.18.401.10
and after that i wanted to reboot to Download mode but it seems after the last flash the Download mode is deleted or missing.
I can boot into Bootloader mode recovery twrp is working very fine system is working very fine everything is working just the problem is that i want the download mode back
but i can´t flash my stock rom without download mode. I was sitting yesterday half night and reading and searching for solutions and help, but withoud success so im now here and hope that someone of u guys
can help me to solve my problem. The thing is that i wanted to change my stock because i am not able with the 2.18.401.10 to flash any custom rom for the M9 nothing is working for example the viper rom
or cyanogenmode also the recovery name is different for my HTC M9 prime CE name is himar and on the M9 original is hima nothing is working for this phone..... please help
hi, i have the same probleme, but I can't flash anything, since My M9 have s-on :S
soo, I cant install a ruu exe, because it says low battery (by go to log_ruu I see it cant do adbdevices)
I can't enter in download mode, it jumbps to bootloader
I can do only some commands on fastboot, for exemple Fastboot oem get_identifier_token don't work, only in download mode (I can't go to download mode, because it doesnt exists)
I can't do comands by adb
C:\adb>fastboot flash zip M9_2.10.401.1_NoWipe_TWRP_2871b1_rename_to_ROM.zip
target reported max download size of 536870912 bytes
sending 'zip' (64024 KB)...
OKAY [ 1.418s]
writing 'zip'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.436s
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:MB523YJ06983
all:
finished. total time: 0.138s
Click to expand...
Click to collapse
C:\adb>Fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
Guys ,pls share hosd_signed himaul img for m9.I don't have download,recovery mode with s on too..pls help me
Way forward
EclipseX said:
hi, i have the same probleme, but I can't flash anything, since My M9 have s-on :S
soo, I cant install a ruu exe, because it says low battery (by go to log_ruu I see it cant do adbdevices)
I can't enter in download mode, it jumbps to bootloader
I can do only some commands on fastboot, for exemple Fastboot oem get_identifier_token don't work, only in download mode (I can't go to download mode, because it doesnt exists)
I can't do comands by adb
Click to expand...
Click to collapse
Hi, were you able to fix this eventually?
Yeah, did send it to HTC without invoice. HTC change the entire motherboard for free
lubaid said:
Hi, were you able to fix this eventually?
Click to expand...
Click to collapse
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.
TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.
Hello guys,
I need a help. I was trying to update my moto using this thread: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153
Everything seemed to be fine until the restart. Phones starts imidately in Fastboot mode with ERROR: Failed to pass validation, backup to fastboot. Now I can't do anything. I've tried to flash other roms, using also that thread: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479 but during the installation it gives many error about downgrading to older security version. Any Ideas? I was trying to find blanckflash but qboot doesn't see the phone. What can I do with that?
with command getvar all I get this. Maybe it will be helpfull.
HTML:
D:\moto recover\>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(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: ZY2249PJMN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EDCCE8F000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 351888080876090
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1710-09
(bootloader) carrier_sku:
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jan 25 4:33:24 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus_playpl/albus:7.1.1/
(bootloader) ro.build.fingerprint[1]: NPSS26.118-33-9/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.301.12.albus_play
(bootloader) ro.build.version.full[1]: pl.playpl.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g2371d89-0010
(bootloader) kernel.version[1]: 2-g249f1d8 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Sat Feb 3 11:22:52 CST 201
(bootloader) kernel.version[4]: 8
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC1.82-0-gbd19194
(bootloader) tz.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) devcfg.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) keymaster.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) prov.git: git=MBM-NG-VC1.82-0-gfbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(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.047s
Do you unlock bootloader before?
Mark2014 said:
Do you unlock bootloader before?
Click to expand...
Click to collapse
Actually not... I assumed it was unlocked...
rembick said:
Actually not... I assumed it was unlocked...
Click to expand...
Click to collapse
You flash rom without unlock bootloader !!!
sorry, I cant help.
Mark2014 said:
You flash rom without unlock bootloader !!!
sorry, I cant help.
Click to expand...
Click to collapse
Thanks anyway, cheers.
How did you flash the Oreo stock ROM in the first place, did you use the script or did you manually flash the commands? Do you still have the flashing log to upload (i.e. the output from the ADB terminal)?
If that's your getvar output after the flash, then it looks like the Oreo update did not work (you're still on 7.1.1). Is your device on the Play.pl carrier btw? It looks like you're receiving some Play.pl specific firmware?
Code:
Blur_Version.26.301.12.albus_playpl.playpl.en.US
Your bootloader is locked, which is why it's falling back to fastboot mode
Code:
(bootloader) securestate: oem_locked
- OEM_locked represents a locked bootloader.
EDIT - Having downloaded and looked at the albus Oreo update, it looks like your bootloader got updated to the Oreo bootloader (version C0.CD), but the rest of your device was not updated. Hence, your device bootloader performed the integrity checks expecting Oreo firmware and failed to boot as you still have 7.1.1 firmware on your device.
Are you able to re-flash the Oreo stock firmware, and if so, can you provide us with a flash log please? If another flash does not work in getting your device working, you may have to consult your carrier or retailer for assistance.
Here's the info for the Oreo stock ROM:
Code:
BUILD REQUEST INFO:
SW Version: albus-user 8.0.0 OPS27.76-12-25 26 release-keysM8953P_41.50.07.63R
MBM Version: C0.CD
Modem Version: M8953P_41.50.07.63R
FSG Version: FSG-8953-08.120
Build Fingerprint: motorola/albus/albus:8.0.0/OPS27.76-12-25/26:user/release-keys
CQATest App Version: 6.0.3
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 27.21.26.albus.retail.en.US
Model Number: Moto Z2 Play
Android Version: 8.0.0
Baseband Version: M8953P_41.50.07.63R
Build Id: OPS27.76-12-25
SW Display Build ID: OPS27.76-12-25
Build Date: Wed Apr 4 07:17:22 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.27.21.26.albus.retail.en.US
Version when read from CPV: albus-user 8.0.0 OPS27.76-12-25 26 release-keys
AB Update Enabled: False
Full Treble Enabled: False
Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Hi. I have a same version - 09. Just bought on days and manually updated to Oreo.
Just use easily this commands set from post you mentioned:
Click to expand...
Click to collapse
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.
rembick said:
Thanks for reply guys, I was away couple of days. I will try your solutions today and give feedback.
EDIT:
Thank you man! You've saved me! your solution works and also I got rid of carrier software from my phone. Thank you one more time.
Click to expand...
Click to collapse
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.
kuro_neko said:
May I know If you flash through fastboot with locked bootloader or not ?
Thanks.
Click to expand...
Click to collapse
I didn't unlock bootloader. Just flashed through Fastboot using the commands one by one not using any .bat file.
You problem (bootloader) cid: 0x0032
Hey, I also got a problem with XT1710-09, but it's a little bit different one.
I rooted it with Magisk and wanted to install an OTA, so I unrooted it.
Then all my problems started to come to light.
Somehow I managed to modify content of /system partition, so OTA installation was unsuccessful.
Then I remembered that before rooting I made a backup with TWRP, so I tried to restore only system partition from that backup.
Unfortunately, my phone couldn't boot. Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Ok, my phone started working again, but then I noticed that no OTA were available for my phone.
Today I investigated a bit, found OTAs and tried to sideload them.
This time error was: build fingerprint error.
Well, yeah, at first I tried to install http://erfanoabdi.000webhostapp.com...on.26.241.16.albus.retail.en.US&carrier=reteu which was meant for "albus", but my phone is branded for Play.
Then I tried to install http://erfanoabdi.000webhostapp.com...51.29.albus_playpl.playpl.en.US&carrier=reteu. This time I got the version for "albus_playpl", but build version was not right, due to flashing system partition which I described above.
And here is my question: what I should do now?
I really don't want to lose any data, nor do I want to install my apps all again.
Is there any solution for me to get it right?
zaq21wsx said:
Then I made a decision to flash just system partition from some other image (well, this one in particular: ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
Click to expand...
Click to collapse
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.
wsemi said:
NPSS26.118-19-14 is "November 2017". Did you have that version before? If not, restoring only the System partition will break the OTA upgrade script because it verifies Boot and Oem partitions as well.
My suggestion is to flash the following partitions from the stock image: gpt, bootloader, logo, boot, oem, system
With that the data remains intact then you can try to check for OTA again.
Click to expand...
Click to collapse
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?
zaq21wsx said:
But now I don't really know what version I had before, because of that branded software. It's nowhere to be found on the internet...
Is changing ro.product.name in build.prop any solution for "albus" from "albus_playpl"? Or how does it change when I'll be flashing another image?
Click to expand...
Click to collapse
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".
wsemi said:
Don't change build.prop. Product name should not change, albus_playpl version is probably for different device.
Try to flash ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip without "erase userdata".
Click to expand...
Click to collapse
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?
zaq21wsx said:
But now I have "albus_playpl" with system image from NPSS26.118-19-14.
Btw what is the difference between ALBUS_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ALBUS_RETAIL_7.1.1_NPSS26.118-19-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip? And will it be good for my XT1710-09?
Click to expand...
Click to collapse
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.
wsemi said:
Ok, I get it know. At the first reading I didn't catch that "Play" is also the name of your mobile carrier. They sold the device with "albus_playpl" firmware. Probably they just put some bloatware or limitation on top of the retail version.
Currently your partitions are inconsistent and seems there is no way to get a full "playpl" firmware. So to make the partitions consistent again you can flash a full retail (carrier independent) firmware. I believe if you do that (as previously described) you will get the OTA updates as well.
Click to expand...
Click to collapse
Yeah, that's a sad coincidence in my case... Well, I'll come back to it, when I have more free time to have fun with flashing new firmware.
You only suggest not to flash data partition, but which one is it?
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata # is it this one? should I just omit it?
fastboot erase DDR
fastboot oem fb_mode_clear
zaq21wsx said:
Code:
fastboot erase userdata # is it this one? should I just omit it?
Click to expand...
Click to collapse
Exactly. Omitting that line should keep the data and internal storage. But to be sure you can make backup to a usb stick.
Moto Z2 Play
My Moto Z2 Play is bricked after system update November 2017.
Bootloader was unlocked.
Now phone is showing on PC as Qualcomm HS-USB QDLoader 9008.
Please help
Hey everybody, here's my story: I bought earlier today a second-hand G5, it was already soft bricked when I purchased it. It was already unlocked (had the warning message when turned on), so I first proceeded to install TWRP, try and flash a custom ROM.
Everything was working fine on bootloader mode, phone was snappy (more on that in a bit) and not lagging.
Then the issues started: on TWRP, it took ages to do anything. The phone's boot logo lasted almost a minute, then TWRP's splash screen stood there for over another minute, and each action I made in it (like touching options on menus and stuff like that) needed a good 10+ seconds to be processed. Tried formatting data, changing FS to from F2FS to EXT4, and other stuff like that, nothing solved the tremendous lag. I also faced some random reboots and many USB disconnecting/reconnecting episodes (like one per second, sometimes) at TWRP as well. Getting the phone to boot TWRP is also a pain, because it keeps switching between a bootlogo with "N/A" (as if there is a custom ROM/recovery installed) and a bootlogo with "bad key" (as if bootloader is unlocked, but ROM and recovery are stock), remains a few minutes in each, and eventually it decides to boot up on TWRP.
Eventually I just gave up and flashed a stock firmware using both RSDLite and fastboot. Flashing times were just about alright, as was everything done via bootloader mode, no stuttering here. Stock recovery (which is operated via volume/power keys, not touch) seemed to work without speed issues as well.
At some point (after many failed efforts, reboots that went straight to recovery, wiping everything multiple times using both TWRP and stock recovery, and so on) I managed to start booting it and... It was sluggish as hell. The boot animation took around 10 minutes to complete (not looping through the animation multiple times, it was just really slow, and it actually just showed about 2 or 3 frames from different moments of the animation and stuck in these frames for several minutes each), the "Hello Moto" tone also played very slowly (as if I were streaming it in 1080p using a 256kbps modem), and when it reached the Lenovo logo (which I presume is the last stage in the boot animation), it bootlooped back to the first frame (Motorola's logo, same as the splash screen but without the "bad key" or "N/A" warning - I had changed from that annoying "bootloader unlocked, device can't be trusted" screen by flashing a modified logo.bin, thus the only difference between splash screen and bootanimation's first frame was the abscence of the text), did so a few times (I think I let it run that way for about 40 minutes) before battery got depleted. Never got into OS.
I did run into a few secondary issues (tried to relock bootloader then unlock again just to find that I couldn't get an unlock code from Motorola's site; had it booting straight into recovery; couldn't wipe data and cache, had TWRP ask for encryption key; etc), but managed to solve all of them.
The point is that right now I have a phone that I can boot either TWRP or stock recovery, or go into bootloader (or sometimes bootloop whilst taking 10 minutes to display the boot animation), but TWRP is slower than a Celeron rendering GTA V, barely usable. Flashing custom (through TWRP) or stock (through fastboot or RSDLite) ROMs seem to complete successfully, but they never get to boot.
If there's any difference, I don't know which version the phone was when I purchased it, but right now bootloader is B8.31, and I tried flashing both 16-2 then 16-4 Oreo versions. Phone model is 1672.
Any help is appreciated, I bought this phone as a gift to my girlfriend and it's specially frustrating I didn't manage to fix it for her.
K3n H1mur4 said:
Hey everybody, here's my story
Click to expand...
Click to collapse
Bro Try To Flash No verity opt zip
it might help you boot
Sonisudhanshu said:
Bro Try To Flash No verity opt zip
it might help you boot
Click to expand...
Click to collapse
Device seems to be unable to get into recovery, now. Just goes into a bootloop with "bad key" (even though TWRP has been flashed). When I try to boot TWRP straight from fastboot (like boot twrp.img instead of flash recovery twrp.img), it shows the usual splash screen (also with neither "bad key" nor "N/A"), but then bootloops into "bad key" again. Will try flashing a different firmware (tried with a random RETBR Nougat and the latest, 16-4, RETBR Oreo) to see if I get any luck.
this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?
Exanneon said:
this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?
Click to expand...
Click to collapse
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
there isn't one yet, but that seems to be your only option atm
Exanneon said:
there isn't one yet, but that seems to be your only option atm
Click to expand...
Click to collapse
K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Why would he need a blank flash? There's nothing wrong with his bootloader
Also we can already revive hard bricked devices with mmcblk0 image but that's not the issue here
Also you obviously won't get another unlock code from Motorola - your device is already unlocked - just because you locked it again doesn't actually lock it the same way
You can just unlock it via fastboot with an unlock command
Anyway moving on
Goto https://mirrors.lolinet.com/firmware/moto/cedric/official/
And downloaded the latest firmware for your device
Flash it via fastboot - note that the firmware must be the same or later version than what is already there
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5 (only oreo firmware)
fastboot flash system system.img_sparsechunk.6 (only oreo firmware)
fastboot flash system system.img_sparsechunk.7 (only oreo firmware)
fastboot flash system system.img_sparsechunk.8 (only oreo firmware)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Make sure gpt and Bootloader flash successfully - a pre flash validation error means that the firmware is too old
Post the output if you get errors
K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Did you try a clean flash or a dirty flash, sometimes dirty flash can result this so I prefer you to clean the data inside first by using twrp advance wipe select all and the format yes and again do a advance wipe after boot into bootloader and flash the latest firmware with bootloader and gpt codes also so bootloader also can reflash. Once you are clean without any other software in Device. the device will work like a champ, and please post the flashing command you get in fastboot as well as getvar also by removing the IMEI and serial number.
Here is the link for latest firmware:-
https://mirrors.lolinet.com/firmware/moto/cedric/official/
TheFixItMan said:
-
Click to expand...
Click to collapse
Hey pal, I appreciate your advice and understand you're a very helpful member in the G5 forums, but I have around 10 years on the modding community (even before Android), and am pretty familiar with flashing via recovery, fastboot or vendors' flashing tools. I've already tried, so, the steps you suggested, to no result either.
Just as a sideline, I've actually managed to get an unlock code from Motorola's online support, but that doesn't make a difference anyway.
I gave a shot on three of the RETBR versions (Oreo 16-2 and 16-4, and Nougat 93-8, this last one obviously without flashing bootloader and gpt). In all of the attempts I got either one of two results: it gets to recovery (TWRP runs slow as hell, stock recovery seems fine) or it keeps bootlooping when I try to get to recovery.
Just tried a RETAIL 16-4 firmware (with gpt and bootloader from RETBR being flashed instead of RETAIL's files), the only error messages I got in fastboot were the expected "Image signed with key bad key when flashing boot and recovery .imgs, but they both flashed just as expected. Same result as before: bootlogo with unlocked warning (showing bad key), then a "boot animation" that was really just the first frame from each part (Motorola logo same as boot logo, the first frame of the animation that plays with the "Hello Moto" sound - also, only some parts of the tone played, like it was lagging too much; then Lenovo Logo; then Motorola logo with "Motorola, a Lenovo company" below; then Lenovo logo again - I really suspect that, if one pulls a bootanimation.zip from a stock firmware, each of the "0", "1", "2" etc parts will have as their first frame exeactly the frames I just described, as if the phone was unable to properly display the animation) displaying for a few minutes each, then it jumps back to bootlogo. It's definitely in bootloop even though I just flashed just per instructions, and also with this issue of being veeeeeeeryyyyyy sloooooooooowwww... After that, it just keeps going into bootlogo for several minutes, than screen off for a few seconds, then bootlogo again for several minutes.
riyan65 said:
-
Click to expand...
Click to collapse
There's no dirty flashing via fastboot AFAIK. When I managed to get into TWRP, I had an issue with /data being encrypted and in F2FS, and some issue with /cache, too (but /cache was in EXT4), both of them were showing as 0B in size at that "repair or change file system" screen.
I read somewhere that F2FS can make TWRP very slow, so I though it could be that, but I formatted /data to EXT4 as well and the phone was still very slow. I also was having issues with TWRP not being able to mount /data and /cache, formatting solved that as well.
After formatting, I managed to flash Bootleggers. It took a good 30-40 minutes to flash, and TWRP restarted right after that so I couldn't flash GApps. It went again into a bootlogo-only bootloop (no frames from boot animation appeared before it restarted into bootlogo again). Then I just gave up on TWRP and tried finding some stock firmware that could boot, but, as stated on the answer above, I still didn't manage to do so.
Right now I'm suspecting either a hardware fault or something very messed with GPT (but I can't really tell for the second one since I've already flashed both RETBR's GPTs and both of them gave me the same result).
What I'd like to try now before just giving up are both very unlikely options to find: first, a custom ROM that's fastboot flashable (Iif I remember well some files in fastboot must be signed by Motorola else they won't flash, so there's no way to create a fastboot-flashable custom firmware, am I right?); second, to find out if the bootloader is stored in the same NAND/eMMC as the other partitions, or if it is a separate chip. If it's the same chip, I could easily rule out a hardware fault and try to find other possible solutions. If it's stored separately, than it explains why bootloader works without stuttering and the other modes (except for stock recovery, but that's kinda slow by itself so I could simply be unable to tell the difference) like TWRP and normal booting are so slow and failing everytime.
New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?
K3n H1mur4 said:
New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?
Click to expand...
Click to collapse
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.
riyan65 said:
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.
Click to expand...
Click to collapse
I have tried it as well, no success whatsoever
I managed to flash Bootleggers again last night, took a couple hours to complete but at least TWRP didn't reboot during the process. Differently from stock ROM, however, phone didn't even get to the sluggish boot animation. It just stays in bootlogo, then eventually reboots (again to bootlogo).
Later tonight I'll try your suggestion again, I plan to do a Format Data, then changing it to ext4 again (if I remember well, Format Data puts the partition into f2fs), perhaps reflashing the no-verity zip and then Bootleggers again. I'm not hoping to get it working anymore, though.
Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC? @TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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
K3n H1mur4 said:
Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC?
@TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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
Click to expand...
Click to collapse
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard
TheFixItMan said:
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
Click to expand...
Click to collapse
Well, if the phone gets no signal it'll sure be an issue. But first I need to get it to boot before I can worry with that.
TheFixItMan said:
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard
Click to expand...
Click to collapse
Already tried RETBR and RETAIL, neither worked (they flashed just fine via either via fastboot or RSD, but got on bootloop with sluggish bootanimation and/or just bootlogo bootlooping). I'm trying with TIMBR right now, but I doubt it will make any difference. Device is a 1672, since I bought it second-hand and already bricked can't tell if the previous owner flashed anything wrong on it. If it did so, I think the device would be hardbricked, not with this weird slowness on TWRP and boot animation, and bootloops would be solved by reflashing stuff on fastboot.
Ok so a quick insight into what happened first I was trying to manually upgrade my phone (XT1955-4) via fastboot to Android 10 since I never received the update about half way through the flash the phone slipped and disconnected from the cable.
I've tried forcing a reboot, (power button held for 10 secs) nothing shows on screen, no vibrating what so ever, I've tried booting into fastboot (power button and volume down button) still nothing on screen, no vibrating.
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753 I've tried this but all I get is the following.
lsusb (It's detected)
Code:
Bus 001 Device 036: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Terminal output
Code:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
FAILED: qb_flash_singleimage()->device_open()->error opening device
qboot_log.txt
Code:
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
[ 0.000]
[ 0.000] qboot version 3.40
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "/dev/ttyUSB0",
[ 0.000] flags = "0x60",
[ 0.000] addr = "0x5CE6C0D8",
[ 0.000] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1/1-1:1.0/ttyUSB0",
[ 0.000] api.bnr = "0x123E560",
[ 0.000] }
[ 0.000]
[ 0.000]
[ 0.000] Backup & Restore {
[ 0.000] num_entries = 0,
[ 0.000] restoring = "false",
[ 0.000] backup_error = "not started",
[ 0.000] restore_error = "not started",
[ 0.000] }
[ 0.000]
qboot detects the device is EDL
Code:
/dev/ttyUSB0 "QCOM emergency download"
UPDATE 1:
After a little tinkering I managed to get some readout but still no life in the device.
Code:
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.003] ...cpu.id = 186 (0xba)
[ 0.003] ...cpu.sn = 3056566883 (0xb62f8263)
[ 0.003] Opening singleimage
[ 0.004] Loading package
[ 0.010] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.314] Handling things over to programmer
[ 0.314] Identifying CPU version
[ 0.322] Waiting for firehose to get ready
Is there anything else I can do as I do believe it's out of warranty.
roadkill42 said:
Try this have couple more
Click to expand...
Click to collapse
Hi Roadkill yes I tried that blankflash earlier this morning and it did work I managed to get back to the bootloader and flash a stock rom but now I'm unable to downgrade the bootloader to reinstall Stock Pie via LMSA (Lenovo's repair tool doesn't recognise the device after trying to update to Android 10) is there anyway to downgrade the bootloader on moto G devices, my old phone was a Nexus 5 which never gave me the amount of problems the Moto G's are doing.
I am now unable to boot into any "special" mode due to flashing firmware from lolinet and there's no bootable A/B slot on the device if that helps.
BioT3rm said:
half way through the flash the phone slipped and disconnected from the cable.
Click to expand...
Click to collapse
That's not a problem and won't cause any problems.
Each single flash command runs like this:
1. sending the image to the RAM of your device
(that's the reason why using sparse image parts for large files)
2. only after the file has been completely transferred, fastboot will start writing it to the partition out of your RAM
As you can see in your output when flashing a firmware via fastboot, every command states sending... and writing.... It's not possible to interrupt the flashing process by disconnecting the USB cable. If it happens that you disconnect your device, then connect it again and go ahead with the next command.
WoKoschekk said:
That's not a problem and won't cause any problems.
Each single flash command runs like this:
1. sending the image to the RAM of your device
(that's the reason why using sparse image parts for large files)
2. only after the file has been completely transferred, fastboot will start writing it to the partition out of your RAM
As you can see in your output when flashing a firmware via fastboot, every command states sending... and writing.... It's not possible to interrupt the flashing process by disconnecting the USB cable. If it happens that you disconnect your device, then connect it again and go ahead with the next command.
Click to expand...
Click to collapse
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.
BioT3rm said:
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.
Click to expand...
Click to collapse
Which country? I need to know the software channel for your firmware. XT1955-4 seems to be the whole planet...
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
Here are versions for Android 10 available:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
BioT3rm said:
Other than the phone disconnecting it fell to the floor and for whatever reason seemed to have corrupted partitions, I've now managed to flash a stock ROM back onto the device.
But unfortunately it will not allow me to use LMSA to flash official firmware due to the upgrade to Android 10 (no way of downgrading the firmware) I can reflash Android 9 but I'm unable to open lock the device to get rid of the bad key message on boot due to the bootloader being upgraded.
Click to expand...
Click to collapse
That bad key is cause of unlocked bootloader
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0a6142d67e0-200524
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: removed for security reasons
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 63822FB600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: removed for security reasons
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 07-26-2019
(bootloader) sku: XT1955-4
(bootloader) carrier_sku: XT1955-4
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 25 3: 9:22 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.52-
(bootloader) ro.build.fingerprint[1]: 29-2/397fb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: <not found> <-- This is another issue
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Sun May 24 10:3
(bootloader) kernel.version[3]: 3:41 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-315bc626c6-200524
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-200524
(bootloader) tz.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) devcfg.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) keymaster.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) prov.git: MBM-2.1-ocean_retail-03d85fce32-200524
(bootloader) aboot.git: MBM-2.1-ocean_retail-0a6142d67e0-200524
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No <-- This is supposed to say Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P0FB
Ok so I think I found the problem @roadkill42 & @WoKoschekk it looks like something went extremely wrong during the flash maybe I was on slot b ?
finally relocked the bootloader fully back to stock, booted the phone up and no sim card is detected, no signal bars are showing and the phone is literally wifi only.
Also another weird thing is that the IMEI is shown in fastboot but not in the sim card menu ?!?
@WoKoschekk My country is England, I've never had a phone do this to me before.
BioT3rm said:
Ok so I think I found the problem @roadkill42 & @WoKoschekk it looks like something went extremely wrong during the flash maybe I was on slot b ?
finally relocked the bootloader fully back to stock, booted the phone up and no sim card is detected, no signal bars are showing and the phone is literally wifi only.
Also another weird thing is that the IMEI is shown in fastboot but not in the sim card menu ?!?
@WoKoschekk My country is England, I've never had a phone do this to me before.
Click to expand...
Click to collapse
It doesn't matter which slot was active while the ROM has been flashed. First of all you flash the gpt.bin (partition table) which will set the active slot to _a.
The downgrade from A10 to 9 is responsible for your mobile network issue. You should unlock your bootloader again and flash the complete firmware a second time.
roadkill42 said:
That bad key is cause of unlocked bootloader
Click to expand...
Click to collapse
WoKoschekk said:
Which country? I need to know the software channel for your firmware. XT1955-4 seems to be the whole planet...
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
Here are versions for Android 10 available:
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Click to expand...
Click to collapse
WoKoschekk said:
It doesn't matter which slot was active while the ROM has been flashed. First of all you flash the gpt.bin (partition table) which will set the active slot to _a.
The downgrade from A10 to 9 is responsible for your mobile network issue. You should unlock your bootloader again and flash the complete firmware a second time.
Click to expand...
Click to collapse
Should I unlock - reflash - relock or just unlock - reflash ?
Code:
#!/bin/bash
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem lock
fastboot reboot
That should be enough to completely reflash and lock the device ?
BioT3rm said:
Should I unlock - reflash - relock or just unlock - reflash ?
Click to expand...
Click to collapse
You should have a running system without any errors before locking the bootloader. There is no need to hurry with that. Make sure everything is working.
WoKoschekk said:
You should have a running system without any errors before locking the bootloader. There is no need to hurry with that. Make sure everything is working.
Click to expand...
Click to collapse
Booted and went through device setup still the same issue no network
Screenshot:
https://ibb.co/30zWYyR
Final update
Managed to get networking back by flashing the following rom
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm going to test the device and then relock it later hopefully this is now a solved issue @WoKoschekk @roadkill42 thank you to the both of you during these harrowing times
BioT3rm said:
Ok so a quick insight into what happened first I was trying to manually upgrade my phone (XT1955-4) via fastboot to Android 10 since I never received the update about half way through the flash the phone slipped and disconnected from the cable.
I've tried forcing a reboot, (power button held for 10 secs) nothing shows on screen, no vibrating what so ever, I've tried booting into fastboot (power button and volume down button) still nothing on screen, no vibrating.
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753 I've tried this but all I get is the following.
lsusb (It's detected)
Terminal output
qboot_log.txt
qboot detects the device is EDL
UPDATE 1:
After a little tinkering I managed to get some readout but still no life in the device.
Is there anything else I can do as I do believe it's out of warranty.
Click to expand...
Click to collapse
I have something that might work .was u just flashing certain files not the modem if I were doing that I have something that might get u back to bootloader
Try this have couple more