Develop Bugs

Modem flash doesn't upgrade Modem

Hi folks.
I've been playing around with Android for over three years now (including reading XDA from then on) but I have come to a point where I do not quite understand why the following is happening.
I wanted to upgrade the Radio / Modem / Baseband of my E975 from 10b to something higher, as the reception isn't always that good.
I am using CM11 and the z20i Mako Bootloader. Here is a getvar output:
c:\adb>fastboot getvar all
(bootloader) version-hardware: rev_11 (152)
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: MAKOZ20i
(bootloader) version-cdma: N/A
(bootloader) variant: mako 32GB
(bootloader) serialno: (serial no)
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: mako
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 80000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 65e800000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 32000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-sizeersist: 800000
(bootloader) partition-typeersist: ext4
all:
finished. total time: 0.030s
So I downloaded a flashable 10 h Modem for CWM and flashed it succesful. Rebooting and looking into the settings confused me then: the modem still was the 10b from Feb-13!
OK, so I fired up fastboot and flashed it via fastboot flash radion xxx.img. Still the same. It did write data on the device, showing it on the screen by "writing".
So both of that did not work at all and I do not understand why that is! I flashed Radios for HTC Magic, HTC Legend, Nexus One, SGS1, SGS2 and that always worked as intended.
Does anybody of you have an idea what the problem is?
Thank you!

xtitanx said:
Hi folks.
So I downloaded a flashable 10 h Modem for CWM and flashed it succesful. Rebooting and looking into the settings confused me then: the modem still was the 10b from Feb-13!
OK, so I fired up fastboot and flashed it via fastboot flash radion xxx.img. Still the same. It did write data on the device, showing it on the screen by "writing".
So both of that did not work at all and I do not understand why that is! I flashed Radios for HTC Magic, HTC Legend, Nexus One, SGS1, SGS2 and that always worked as intended.
Does anybody of you have an idea what the problem is?
Thank you!
Click to expand...
Click to collapse
cyanogenmod will show the string of the first stock rom/kdz you flashed regardless of any modems you afterwards change.

atifsh said:
cyanogenmod will show the string of the first stock rom/kdz you flashed regardless of any modems you afterwards change.
Click to expand...
Click to collapse
Oh my god, seriously?
That was not the case for the other devices I owned before.
Thank you very much for this answer.
Do you know to to read out the actual modem that is used right now?
Thanks again for the quick reply!

xtitanx said:
Oh my god, seriously?
That was not the case for the other devices I owned before.
Thank you very much for this answer.
Do you know to to read out the actual modem that is used right now?
Thanks again for the quick reply!
Click to expand...
Click to collapse
No idea, never bothered after i knew this
Sent from my GT-P3100 using Tapatalk

Interessting news, guys:
As of today's nightly, 12/17/13, CM reads the Baseband from the Modem, not the misc partition, meaning the recent Baseband is now also correctly displayed in the settings.
Thanks to Seth Shelnutt for this update.

Endless bootloop. Can't get into recovery even with fastboot commands

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.

Bootloop fix for Nexus 7 2013 when flashing doesn't help

This practical solution I wanted to share here after i couldn't find a solution online is for Nexus 7 devices that can boot into Fastboot. If your device can't boot into fast boot anymore try this solution by K23m from here. And if your device have instead a faulty eMMC that might need replacement or else check here instead.
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop two days ago. I used twrp recovery to wipe it all, refresh lineage os or stock ota, yet i couldn't get past the boot loop. Ill spill the beans early here, It fixed and it needed me to zero out all the free space of the eMMC. as soon as i did that i got back to a 100% reliability and fast speeds like the first time i bought it.
But first was how to boot into a working android image to download and run the zeroing utility. The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz" you can google it but ill provide this mirror link just in case it disappears.
I believe that my problem was that i had little space left and it got corrupted in some way maybe because of bad Trim process. in any case the following old factory image is small and have the highest (only?) chance to boot once and allow to reset the empty space values int he eMMC.
I started by following the process under fast boot:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15j.zip
Try booting 4 times if it doesn't work add this step before:
Download the great restore script and files from "[TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)" here at XDA and download the "Nexus7_2013_KTU84P_Restore.zip WIFI Flo" if you're like me or the other corresponding image for your Nexus 7 version.
First copy the files of the razor-jss15j-factory from the compressed archive inside the same folder as the restore archive and
Run these fast boot commands from within:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash recovery twrp-3.2.1-0-flo.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot -w
fastboot -w update image-razor-jss15j.zip
fastboot flash boot boot.img
fastboot reboot
Try booting 4 times with at least one switched off period of 20mn in between till you boot in. ( it is random and its not guaranteed it will work for you like i did for me)
I know some command are redundant and might make you think its stupid to do so but believe me when i say i spent 2 days non stop trying everything i can short of opening the device to heat gun the eMMC chip
These are the last steps i took to finally boot in and i repeated the process as i tried the first time to flash newer images in the hope they will boot too but to no avail.
Now that you booted in the old android version first go to the App Store and download a free zeroing app like" Secure Eraser " by Giuseppe Romano from the app store. after you run it twice, you can reinstall lineage os or your favourite stock version and be relieved.
I hope this amateurish post help you not discard too early your beloved Nexus 7 tablet. its only worth for me is manga reading and youtube sometimes, and for that its a wonder.

jackkill said:
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop... The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz"
Click to expand...
Click to collapse
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers

k23m said:
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers
Click to expand...
Click to collapse
Thank you k23m,
Ill add the Fresh persist solution link for those who can’t boot into Fastboot
and the link to the Hardware Nand bricks fix too
As for my experience, I did try google’s recovery firmware and steps, however it proved ineffective. At some point even the recovery partition stopped working and forced me to only use Fastboot afterward. As i looked everywhere on how to fix the stuck boot and tried the proposed software solutions with no avail, i decided to share my practical experience of what worked for me, in hope it helps someone else facing the same problem.
my Nexus 7 device is already around 4 years old and it was a discounted demo unit form a retail store, It is a fact that the amount of read write have already reached a high level that must have wore the Nand quite a bit already. However, as the secure eraser method solved the problem, I don’t believe that doing so once in the 4 years span is much of a risk in comparison. My device was on post Stock Android 4.3 most of the time and was on Lineage OS Android 7 since last year, Trim clearly failed to perform. And many sources online believe that the way Google implemented Trim isn’t complete and think that the decreasing device performance on android devices must be linked to it.
I am convinced that the problem was software, related to Trim somehow, and as the Land chip i own is a Toshiba, it can be ruled out from the known faulty Nand brand some Nexus 7 have. Moreover, no error message was displayed when performing Fastboot operations. everything was executed with success all the time.
Cheers

jackkill said:
However, as the secure eraser method solved the problem...
Click to expand...
Click to collapse
Many things happened during the repair session and I'd not credit "secure eraser" for the speed improvement.
The "secure eraser" app does not require root (to run fstrim) nor trigger TRIM ever! It just fills up empty storage space. Read the reviews - slow, horrible , inefficient. Let me propose an alternative - boot TWRP and run/install my TRIM script - it will optimize the storage space in seconds, without excessive NAND wear out - see the attachments. Run it whenever you feel that Google's TRIM algo is deficient and it's time for manual override...
:highfive:

About to give up on old Nexus 7 2013 (last ditch)
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years. The last months, I pretty only used it for podcasts via the PocketCast (best Podcast app and runs on both the major mobile OS's.)
Anyways, it had been getting caught in these bootloops off and on. The last time it successfully booted was on Sunday (4/29). That session lasted until this past Sunday until it decided to reboot on its on and hasn't been usable since.
I tried the ADB tools on a Windows 10 but the only way Windows would talk to the device was when I set it to Recovery mode with the "Install from ADB". I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.
I should add that I never installed any custom ROMs ,TWRP, or what have you. In fact, I never really paid much attention to the Android Development scene at all until the past couple of days.
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out. I got my money's from it though.
If anyone has any advice on other things to try, I'd be all ears. I'm probably going to move on try my hand with one of the Odroids.

Burgin said:
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years......
Anyways, it had been getting caught in these bootloops off and on........
I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.........
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out.
Click to expand...
Click to collapse
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Please post the output of the following commands:
turn off the Nexus
connect it to your PC
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache​
Next...
go to your folder with fastboot.exe and adb.exe
download twrp-3.2.1-0-flo.img to the folder
also unzip and copy the attached "twrp-log.bat" to the folder
in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
when TWRP is up and running (may ask for ADB driver) and you see the menu, double-click on twrp-log.bat
Note, the above steps must be done withn 3 minutes to ensure complete dmesg log
then you will find a new file twrp.txt in the folder
zip up twrp.txt and attach it to your next post
Actually, as a new XDA user you may not be able to attach files or post links, so upload twrp.txt to http://pastebin.com and post only the subpage part, eg. from https://pastebin.com/9cat4t4X7 post only this 9cat4t4X7
Cheers :good:

First, thank you for the quick reply
Moving on. My problem is I can't get anything from the fastboot command. It just says "Waiting for device".
I assume that my USB drivers are totally wrong and I need to start all over in that regard.
When I read from this page, "developer.android.com/studio/run/oem-usb#InstallingDriver", I gather that there are actually two drivers to install, one for the Google USB driver and another specifically for the Nexus 7. Am I reading this correctly? What is this second driver?
(Oh and I did manage to find what I think to be a better quality USB cable.)
k23m said:
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Cheers :good:
Click to expand...
Click to collapse

Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
fastboot getvar all
Code:
(bootloader) version-bootloader: FLO-04.08
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 07d98df8
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: locked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.043s
fastboot oem gpt-info
Code:
(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB
(bootloader) partition[4].name = persist
(bootloader) partition[4].first_lba = 524288
(bootloader) partition[4].last_lba = 554287
(bootloader) partition[4].size 15000 KB
(bootloader) partition[5].name = m9kefs1
(bootloader) partition[5].first_lba = 655360
(bootloader) partition[5].last_lba = 656919
(bootloader) partition[5].size 780 KB
(bootloader) partition[6].name = m9kefs2
(bootloader) partition[6].first_lba = 656920
(bootloader) partition[6].last_lba = 658479
(bootloader) partition[6].size 780 KB
(bootloader) partition[7].name = m9kefs3
(bootloader) partition[7].first_lba = 786432
(bootloader) partition[7].last_lba = 787991
(bootloader) partition[7].size 780 KB
(bootloader) partition[8].name = fsg
(bootloader) partition[8].first_lba = 787992
(bootloader) partition[8].last_lba = 794135
(bootloader) partition[8].size 3072 KB
(bootloader) partition[9].name = sbl1
(bootloader) partition[9].first_lba = 917504
(bootloader) partition[9].last_lba = 920503
(bootloader) partition[9].size 1500 KB
(bootloader) partition[10].name = sbl2
(bootloader) partition[10].first_lba = 920504
(bootloader) partition[10].last_lba = 923503
(bootloader) partition[10].size 1500 KB
(bootloader) partition[11].name = sbl3
(bootloader) partition[11].first_lba = 923504
(bootloader) partition[11].last_lba = 927599
(bootloader) partition[11].size 2048 KB
(bootloader) partition[12].name = aboot
(bootloader) partition[12].first_lba = 927600
(bootloader) partition[12].last_lba = 937839
(bootloader) partition[12].size 5120 KB
(bootloader) partition[13].name = rpm
(bootloader) partition[13].first_lba = 937840
(bootloader) partition[13].last_lba = 938863
(bootloader) partition[13].size 512 KB
(bootloader) partition[14].name = boot
(bootloader) partition[14].first_lba = 1048576
(bootloader) partition[14].last_lba = 1081343
(bootloader) partition[14].size 16384 KB
(bootloader) partition[15].name = tz
(bootloader) partition[15].first_lba = 1179648
(bootloader) partition[15].last_lba = 1180671
(bootloader) partition[15].size 512 KB
(bootloader) partition[16].name = pad
(bootloader) partition[16].first_lba = 1180672
(bootloader) partition[16].last_lba = 1180673
(bootloader) partition[16].size 1 KB
(bootloader) partition[17].name = sbl2b
(bootloader) partition[17].first_lba = 1180674
(bootloader) partition[17].last_lba = 1183673
(bootloader) partition[17].size 1500 KB
(bootloader) partition[18].name = sbl3b
(bootloader) partition[18].first_lba = 1183674
(bootloader) partition[18].last_lba = 1187769
(bootloader) partition[18].size 2048 KB
(bootloader) partition[19].name = abootb
(bootloader) partition[19].first_lba = 1187770
(bootloader) partition[19].last_lba = 1198009
(bootloader) partition[19].size 5120 KB
(bootloader) partition[20].name = rpmb
(bootloader) partition[20].first_lba = 1198010
(bootloader) partition[20].last_lba = 1199033
(bootloader) partition[20].size 512 KB
(bootloader) partition[21].name = tzb
(bootloader) partition[21].first_lba = 1199034
(bootloader) partition[21].last_lba = 1200057
(bootloader) partition[21].size 512 KB
(bootloader) partition[22].name = system
(bootloader) partition[22].first_lba = 1310720
(bootloader) partition[22].last_lba = 3031039
(bootloader) partition[22].size 860160 KB
(bootloader) partition[23].name = cache
(bootloader) partition[23].first_lba = 3031040
(bootloader) partition[23].last_lba = 4177919
(bootloader) partition[23].size 573440 KB
(bootloader) partition[24].name = misc
(bootloader) partition[24].first_lba = 4194304
(bootloader) partition[24].last_lba = 4196351
(bootloader) partition[24].size 1024 KB
(bootloader) partition[25].name = recovery
(bootloader) partition[25].first_lba = 4325376
(bootloader) partition[25].last_lba = 4345855
(bootloader) partition[25].size 10240 KB
(bootloader) partition[26].name = DDR
(bootloader) partition[26].first_lba = 4456448
(bootloader) partition[26].last_lba = 4456463
(bootloader) partition[26].size 8 KB
(bootloader) partition[27].name = ssd
(bootloader) partition[27].first_lba = 4456464
(bootloader) partition[27].last_lba = 4456479
(bootloader) partition[27].size 8 KB
(bootloader) partition[28].name = m9kefsc
(bootloader) partition[28].first_lba = 4456480
(bootloader) partition[28].last_lba = 4456481
(bootloader) partition[28].size 1 KB
(bootloader) partition[29].name = metadata
(bootloader) partition[29].first_lba = 4587520
(bootloader) partition[29].last_lba = 4587583
(bootloader) partition[29].size 32 KB
(bootloader) partition[30].name = userdata
(bootloader) partition[30].first_lba = 4718592
(bootloader) partition[30].last_lba = 61079518
(bootloader) partition[30].size 28180463 KB
(bootloader) partition[31].name =
(bootloader) partition[31].first_lba = 0
(bootloader) partition[31].last_lba = 0
(bootloader) partition[31].size 0 KB
(bootloader) partition[32].name =
(bootloader) partition[32].first_lba = 0
(bootloader) partition[32].last_lba = 0
(bootloader) partition[32].size 0 KB
(bootloader) partition[33].name =
(bootloader) partition[33].first_lba = 0
(bootloader) partition[33].last_lba = 0
(bootloader) partition[33].size 0 KB
(bootloader) partition[34].name =
(bootloader) partition[34].first_lba = 0
(bootloader) partition[34].last_lba = 0
(bootloader) partition[34].size 0 KB
(bootloader) partition[35].name =
(bootloader) partition[35].first_lba = 0
(bootloader) partition[35].last_lba = 0
(bootloader) partition[35].size 0 KB
(bootloader) partition[36].name =
(bootloader) partition[36].first_lba = 0
(bootloader) partition[36].last_lba = 0
(bootloader) partition[36].size 0 KB
(bootloader) partition[37].name =
(bootloader) partition[37].first_lba = 0
(bootloader) partition[37].last_lba = 0
(bootloader) partition[37].size 0 KB
OKAY [ 0.289s]
finished. total time: 0.290s
fastboot format cache
Code:
fastboot format cache
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 143360 4k blocks and 35840 inodes
Filesystem UUID: 582c2894-53a4-11e8-8bf9-f98baf2837a1
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.510s]
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.522s
---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.

Burgin said:
Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
.....
fastboot format cache
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
....
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.
Click to expand...
Click to collapse
Thank you. It looks like you had to unlock it before running TWRP. I see some errors which should go away after you flash the latest factory image from fastboot. Then before you boot the fresh system, please make sure it is still connected to USB3 or a 2 Amp charger. If or when Android is up and running start an app like StabilityTest or some other heavy load benchmark tool. If there are no problems, disconnect the charger and see how it goes without it.
Your battery's stats:
Code:
<5>[ 3.908325] bq27541_get_psp voltage_now= 4040000 uV
<5>[ 3.909149] bq27541_get_capacity = 70% ret= 71
<5>[ 3.909973] bq27541_get_psp temperature= 287 (0.1¢XC)
<5>[ 3.910980] bq27541_get_psp current_now = 356 mA
<5>[ 3.911804] bq27541_get_psp charge_now (compensated) = 2235000 uAh
<5>[ 3.912811] bq27541_get_psp charge_avg (uncompensated) = 2365000 uAh
<5>[ 3.913635] bq27541_get_psp charge_full = 3161000 uAh
<5>[ 3.914611] bq27541_get_psp charge_design = 4090000 uAh
<5>[ 3.915466] bq27541_get_psp energy_now = 8067000 uWh
<5>[ 3.916442] bq27541_get_psp charge_counter = -51000 uWh
<5>[ 3.917266] bq27541_get_psp power_now = 1438000 uW
<5>[ 3.918243] bq27541_get_psp cycle count = 600
There is a huge drop of "charge_full" and very high "cycle count". I'd say the battery is definitely finished. I bet there are no problems or bootloops when it is connected to a good external power source via a short USB cable.
:highfive:

k23m said:
....
[*]in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
....
Cheers :good:
Click to expand...
Click to collapse
I am a newbie to using TWRP and this is the first time I have attempted to try a Custom ROM for my Nexus 7 2013 (flo).
The above command saved me. I was able to go into TWRP, Wipe, Advanced Wipe, and perform a Wipe of everything except the internal storage.
I then did the adb flash recovery <latest TWRP.img> and now I get the most welcome sight of the TWRP GUI.
Many many thanks.

Help! I cannot unlock the bootloader on my tmo z2 force

I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid

vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei

41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s

wtf xda turned some of it into emojis

Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.

vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work

vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options

vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs

vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.

fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2

41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.

vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.

41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow

Need help with very weird soft brick

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.