Moto g5 plus IMEI 0 after flashing anything? Read on! - Moto G5 Plus Questions & Answers

After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!

Did you get voLTE to work?

What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.

stonewolf05 said:
What carrier are you on? I am on Verizon and this only gets me 3G like all of other fixes for this issue on here.
Click to expand...
Click to collapse
Was with Verizon, was only getting 3g, frequent drops. Switched to AT&T just because they're so much better in my area.

thankyou soo much . helped me

I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance

mohitzr said:
I dint get my signal/IMEI back after installing custom rom
any suggestions??
Thanks in Advance
Click to expand...
Click to collapse
Unfortunately, none of these methods work no more, the question is why?. Personally, I believe something further has been borked in oreo development, just like the volte issue. Absolutely no methods restore my ime, some actually make it very difficult to even get a signal now. I spent several hours last night trying every option available just to get a signal, whereas before I flashed the latest vladious rom, flashing pixel experience, or any oreo rom for that matter, would restore 4g on first boot. My ime is 0 and i give up. In all my years with android modding (since zte blade), I have never had a device with so many issues, and so unpredictable. You can use a method to fix something, and next thing you know it does not work, for example, encryption can be really hit and miss when you first flash twrp, even flashing no verity does not always work.

Tried every possible combination as per guides/fixes....no luck..

The only thing that's worked for me without fail every time is wiping everything with twrp, Dalvik, Data, System, Cache, internal storage, hitting that dreaded Format Data button, and flashing the earliest stock firmware (which I believe is 137-33 for the XT1687) using fastboot. Having a backup can save a ton of time and headaches too. If there's any point where you DO get at least LTE working, back up that EFS partition before you do ANYTHING else. But try flashing the earliest stock you can find, or preferably the one that was on your device when you bought it.

Worked like a Charm!
Dude, i was looking for the same since yesterday, come to this thread and follow all the steps carefully. My IMEI was showing 0 before and now everything is working fine including both SIM cards.
Thanks
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

(bootloader) Permission denied. Please help
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.121s
beatlesfan5858 said:
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required!
Prerequisites:
U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on other versions)
8.1 custom Oreo ROM (I used Validus, we only use this to get signal and imei back to default)
Moto g5 plus STOCK ROM https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Patience
***************************
That's it!
Down to the nitty gritty. Your imei is zero or 0000000 or some funky number, and no sim cards/cellular service works in your device, right? I finally found the simple solution after hard work. You have TWO options, read on.
1. Flash custom recovery, erase everything, and get on 8.1 Oreo ROM (delete modemst1 and 2 in fastboot beforehand) and STAY THERE. Signal will work.
2. OR go back to stock everything and locked bootloader, which is what I did. My fastboot says software status official oem locked and I get updates.
******************
The TRICK is, if your imei is 0 and cellular doesn't work, you have to delete your modemst1 and 2 in fastboot before installing anything new, so that it can reset back to default. The other TRICK is if you are reverting back to stock, follow all the normal commands for reflashing, but DON'T do anything with modemst. say I was following normal commands for flashing, then ran across these three commands....
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
SKIP THEM. What we're attempting to do is keep your EFS folder as it was on the 8.1 OREO, aka WORKING. Flashing rom itself doesn't delete the EFS folder, but when you run those commands (which is in most tutorials) IT WILL WRECK YOUR IMEI AGAIN.
************
So, to recap. To fix IMEI issue, use these two commands in fastboot
fastboot erase modemst1
fastboot erase modemst2
THEN, flash 8.1 custom oreo rom, and if you like it stay with it, your signal will be working again, or go back to stock everything oem locked, your choice, just make sure you don't delete your modemst1,2 in commands WHILST doing so.
And that's it! Your imei and signal is working again. What's stupid is that this happens in the first place, but life happens. FIXED!
Click to expand...
Click to collapse

deep_raman said:
Can anyone help on this error. I'm having IMEI 0 error, was working fine in morning after that my friend messed up and now same error. I was not able to fire any command now. please help.
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
Other might helpful info:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245K4LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 372C889E00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958068640199
(bootloader) meid:
(bootloader) date: 07-20-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 6:53:42 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.121s
Click to expand...
Click to collapse
Is your device got fixed?

riyan65 said:
Is your device got fixed?
Click to expand...
Click to collapse
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.

deep_raman said:
No yet brother! I've to take it to the customer center but they are stating that it can't be solved through software and need to replace motherboard LOL.
I took back and its with me now. Waiting for some solutions here.
Click to expand...
Click to collapse
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.

riyan65 said:
Your network problem can be solved since IMEI no is shown getvar. You can try installing latest stock Oreo, or trying custom ROMS. Many times custom ROM bring back the IMEI.
Click to expand...
Click to collapse
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too

deep_raman said:
Bro, I've tried and what I'm getting is below, i think becuase of flashing_locked:
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.410s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.419s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.526s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.540s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 6.117s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.175s
I can't able to flash too
Click to expand...
Click to collapse
Did you try Lenovo moto smart assistant? It will flash the device for you.

riyan65 said:
Did you try Lenovo moto smart assistant? It will flash the device for you.
Click to expand...
Click to collapse
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!

deep_raman said:
Yeah , tried that as well. It is failing at 67%. Tried in USB debugging as well as fastboot mode.!!
Click to expand...
Click to collapse
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.

riyan65 said:
Use the firmware downloaded by LMSA and flash the device manually. And did you try any custom ROMs? Mostly they help you to get back your IMEI.
Click to expand...
Click to collapse
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:

deep_raman said:
I tried the LMSA and custom ROMS but the main problem is I dont even have flashing permission too. As mentioned earlier I' m getting flashing permission denied. I dont have TWRP install, dont have flashing permission...!! So cant flash anything anymore !!! :crying:
Click to expand...
Click to collapse
Solution
I was using previous/old version of ADB files(Fastboot.exe and ADB.exe). Post downloading latest version, I was able to fire below command through bootloader:
fastboot.exe flashing unlock
Now I'm all happy.

Related

[SOLVED] [XT1572] Fully bricked or is there a solution ?

Hey there,
To make it short, the phone was rooted, bootloader unlocked, and it was on Resurrection Remix (don't know which one, it was Nougat 7.1.2).
I tried to restore it back to stock, lock the bootloader etc (following this guide : https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 which has files for xt1572 too ).
During the process, I got the error that a lot of people get about the Preflash validation error and yet i went through, except that I still locked at the end (I did not notice the Note about it below the command lines, I so regret it).
I also flashed the original Motorola logo (instead of "Bootloader is unlocked"), but I don't think this has anything to do with the fact that it got bricked (I can be wrong though).
Now, I can't access the phone through the cable. adb devices (with killing and restarting server) doesn't detect anything, I'm just stuck on the big Motorola logo splash screen.
Anyone has any idea on any possible way to unbrick it ? (I heard about qualcomm hsusb something but I'm just not sure where it can lead)
Thanks !
@pef6000
Bootloader is locked? What is status code...?
can't you use fastboot (from device turned off hold power + vol down) and flash stock motorola rom?
Hey there, thanks for your answers.
I can't access bootloader nor fastboot. adb doesn't show any device anymore.
I cannot even turn on or off the phone. It just reboots even if I long-press the power button. It just boots back up, and I can only leave it like this until battery is depleted.
Hold power, when screen turn off hold only vol-. It should go to bootloader.
Check and post here BL status. @pef6000
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Btw, if you will go to bootloader mode(locked) - you can only flash again stock 6.0.1(newest).
Without bootloader and gpt.
Check how many sparsechunks you have in zip file, I think from 0 to 11.
Sorry for being late. I tried that yesterday, but one problem after another, Windows died
I'll pass some time on it whenever I get the computer working.
I tried starting in BL and it worked !
I think the fact that it wasn't working before was due to the phone bootlooping directly on splash screen (maybe, I don't know).
Here, battery was dead since I couldn't turn it off. So I plugged the phone in while keeping vol- pressed, and it booted immediately in.
Couldn't get a hold of the status code though, the computer rebooted and crashed, so I had something else in mind, sorry :/
Anyway, I'll do that whenever I can, thanks for your help !
Here again. I accessed bootloader and I get :
AP Fastboot Flash Mode (Secure)
[…]
Console [NULL]: null
Battery OK (charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Before this problem, when I tried to flash everything, I have parsechunks from 0 to 8, not 11.
Now, I don't really know what to do. Should I do everything back again with a 6.0.1 zip ?
pef6000 said:
Should I do everything back again with a 6.0.1 zip ?
Click to expand...
Click to collapse
Yes.
Without bootloader, gpt and Don't lock BootLoader.
Hey.
I did it, didn't lock bootloader, didn't flash bootloader.img nor gpt.bin, but it still freezes on the splash screen logo. I suppose it woudn't take as much as 15 to 30 minutes to switch from that splash screen to any other screen.
The bootloader is still accessible, and I still have the same things (unlocked, status 3, etc).
Am I doing something wrong ? :/
What is your model and what rom are you flashing?
What do you have on pc after: "fastboot getvar all"? @pef6000
It's a XT1572, European (got it in France).
I'm trying to flash the one for XT1572 in the link with the instructions : https://dl.prazaar.de/?dir=Android/XT1572/Factory/6.0.1/MPHS24.107-58-5_September_2016
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA3910197I
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 42C5D7001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...]
(bootloader) meid:
(bootloader) date: 11-12-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 6 10:58:55 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g0ec7138 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Tue Nov 3 05:05:40 CST 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 2/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retfr
all: listed above
finished. total time: 0.242s
Did you flash: boot, recovery, all sparsechunks(0-11), modem, all erases? Each command ended with OK? @pef6000
Yes, I did all of this, everything turns out ok except one error (the Preflash Validation).
Now that I read it again, the post says it happens on gpt.bin, except I didn't flash it as you said.
I just did it again and I get it again at this step :
> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41699 KB)...
OKAY [ 0.923s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
Do I also not flash the modem ? :/
EDIT :
Btw, the bootloader log on the phone says "Image is too large" after the "cmd: flash:modem" line.
pef6000 said:
It's a XT1572, European (got it in France).
Click to expand...
Click to collapse
You should edit your post and remove the IMEI number...
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
dzidexx said:
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
Click to expand...
Click to collapse
From the getvar output, the bootloader is on 6.0
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
Click to expand...
Click to collapse
on MPHS24.49-18-4... I would suggest using the same version or XT1572_CLARK_RETEU_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and NOT 6.0.1. The 6.0.1 versions were only for certain variants, and I do not know if the RETFR ones had that.
And don't skip the bootloader or gpt UNLESS they actually fail... It is best to do it like this:
Also, if possible boot into the factory recovery and perform a full factory reset before beginning.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
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 [Verify number of sparse chunks and make sure you are doing the correct #]
fastboot flash modem NON-HLOS.bin [May need to be done more 2 or 3 times to "take", make sure it returns an "OKAY"]
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
My 2 cents worth... hope it helps.
@acejavelin Oh damn, thank you. I thought I checked correctly but I didn't notice the IMEI in there.
Thank you both for your help. Phone booted up on original rom, I'm happy
I'll mark this post as Solved, but I have a quick question : Can I use the XT1575 logo.bin found here :https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Or is it better not to do so ?
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/boot-animation-logo-bin-t3558942 @pef6000
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
dzidexx said:
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/[email protected]
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
Click to expand...
Click to collapse
@pef6000 Any of these or the one you mentioned is fine.
Sorry for the late answer, I flashed the 18-8 in the end.
Thanks again, I'll mark this as solved !

Flashing back to Stock, Trying to understand Errors

So I ran into some issues installing LOS15 and flashed back to stock using POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Being paranoid I am concerned about the errors I have gotten, mainly because if the ROM messed with my system and I cannot replace it, well, who know what nefarious actions might be taking place.
I have booted the system and it works fine, but again, just being cautious.
Here are the errors:
Code:
[B]fastboot flash partition gpt.bin[/B]
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.074s
[B]fastboot flash bootloader bootloader.img[/B]
sending 'bootloader' (5115 KB)...
OKAY [ 0.233s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.510s
[B]sudo fastboot flash boot boot.img [/B]
ending 'boot' (16384 KB)...
OKAY [ 0.771s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.442s]
finished. total time: 1.213s
[B]sudo fastboot flash recovery recovery.img [/B]
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.973s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.532s]
[B]
sudo fastboot erase customize[/B]
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
[B]sudo fastboot erase clogo [/B]
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
Is your moto g5 plus reteu?
InsaneNexuS said:
Is your moto g5 plus reteu?
Click to expand...
Click to collapse
I guess you meant retail? Yeah, it is retail. No amazon ads.
Well I need to know if it was reteu software channel. Otherwise it wont work for you. Maybe because your not flashing the right files? Mine was RETEU, which means its a european model.
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Well then you need to find the right firmware for you US model. And start with locking the bootloader. And flash every line one by one (copy paste). Dont copy all of them and paste them otherwise it wont work. You really have to do it one by one.
Bootloader relock commands:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
After you locked the bootloader start flashing the firmware. Use this site to find the right firmware:https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I gues you should try the one that says RETAIL in the name.
---------- Post added at 23:01 ---------- Previous post was at 22:59 ----------
NODE06 said:
No, not European. US Version. At least I bought it on Amazon in the US.
I want to add that I have flashed the stock before and did not get these errors. It only happened after I flashed LOS15.
Click to expand...
Click to collapse
Well if you have done it before then I guess I don't really know what the problem is
Here's what happened putting in that code:
Code:
sudo fastboot oem lock
[sudo] password for user:
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
sudo fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.012s]
finished. total time: 0.012s
sudo fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75638 KB)...
OKAY [ 3.432s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.499s
I guess I would just like to know why this is happening. like what does "(bootloader) Security version downgrade" even mean?
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
acejavelin said:
Your are downgrading, trying to flash a version of firmware that is older than what is installed already.
You either need a newer factory image, or are using the incorrect one. "Preflash validation failed" is basically saying the digitial signature doesn't match what is already there or is older than what you have currently.
Exactly what image are you flashing and what is the output of "fastboot getvar all" except mask out the IMEI number(s).
Click to expand...
Click to collapse
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(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: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
NODE06 said:
Yeah, I thought that was the issue. I guess I just kind of fracked my phone then because I installed Lineage 15.0 which uses Android O. I guess there will not be a newer firmware image anytime soon.
The flash back to stock works but I would rather have everything original. This code is with Resurrection ROM. Will be glad if you can explain any of it!
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(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: MSM8953
(bootloader) serialno: ZY224538B8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8a
(bootloader) uid: 7C6B3F8100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-18-2017
(bootloader) sku: XT1687
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:41:43 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:7.0/NPN25.1
(bootloader) ro.build.fingerprint[1]: 37-35/37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.37.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.08R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g6508460 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Feb 14 06:47:06 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.026s
Click to expand...
Click to collapse
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
acejavelin said:
No, you don't understand... Your "firmware" in this case means bootloader/partition table/radios, it has nothing to do with any custom ROM you would flash, but the last stock firmware you had installed, which in your case was NPN25.137-35 (Blur_Version.25.11.37.potter.retail.en.US) and a radio of M8953_02.03.07.08R POTTER_NA_CUST, so you need that version or higher.
Which seems odd, because that is newer than my version which is completely stock and untouched.... NPNS25.137-33-5/M8953_02.03.07.06R... So I am assuming you were on a special Verizon test build? You will need one of those except the same version or newer than when you were last stock.
Click to expand...
Click to collapse
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
NODE06 said:
I use Consumer Cellular, and the only thing I did that started screwing everything up was install Lineage 15 which is based on Android Oreo. Could that have change it to the newer version?
Click to expand...
Click to collapse
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
acejavelin said:
I don't know about Consumer Cellular but I think they are an AT&T MVNO so it probably isn't relevant.
Any custom ROM you flashed is not relevant either... to go back to stock you must flash a same or newer firmware than what you have, and you are confusing what that means. Lineage, or any custom ROM, does not modify your firmware, only your system and boot partitions, your firmware is in the bootloader/radios and is related to your gpt.bin (the partition table). You need a factory image that is the same or newer than what you have, which I don't think is available since Moto isn't very forthcoming with factory images (and your version is very new, newer than mine), but this has nothing to do with flashing a custom ROM.
I haven't tried this on this device, but on older Moto devices you would downgrade by flashing the firmware but skipping gpt.bin and bootloader.img (you also cannot relock the booloader) and continuing with the other parts of the firmware image. Yes, the booloader and partition table no longer match the radios and rest of the ROM, but that usually fixes itself during the next major OTA update.
Click to expand...
Click to collapse
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
NODE06 said:
I understand what you are saying, but I am telling you I flashed the same stock firmware a month ago with no issues.
The only thing that changed everything was installing the Lineage ROM. Could the Linage ROM have messed up my partition tables? I was having issues when I tried to install it relating to data encryption. But I have no idea how I could have flashed a newer version of anything. This is why I am so confused.
Click to expand...
Click to collapse
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
acejavelin said:
Eh, not mess up, but it could change the filesystem type for a partition or two, sometimes system or data. You could use TWRP and try a repair on them.
Can't you just restore a TWRP backup first, then flash stock?
Sorry, but I may be a considered a wizard by some with some Moto devices, but I am really new to this one and it seems to have a few different quirks. Hopefully someone else can jump in here.
Are you using an official image? They usually contain a file called flashfile.xml, that will tell you what commands you need to enter to flash and what version it is, the above instructions are to relock a stock device, not return to stock.
Click to expand...
Click to collapse
He's flashing a stock.zip I believe.
aaronrw said:
He's flashing a stock.zip I believe.
Click to expand...
Click to collapse
Not with fastboot...
@NODE06 What exactly are you flashing and how?
acejavelin said:
Not with fastboot...
@NODE06 What exactly are you flashing and how?
Click to expand...
Click to collapse
I am flashing
POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
on Linux using ADB, yes, fastboot. I have done it often enough on this phone and used to do it on my G4.
I am wondering, looking at the flashfile.xml, if I should flash them in the same order they are listed in that file. But again, it does not make sense since the only think I did was install Lineage 15 when I was running Resurrection. I will try again to repair with TWRP, maybe I am missing something.
I am back on Resurrection and things are running fine, but I am concerned now that Lineage 15 might be doing some really weird stuff.
I notice the flashfile.xml has
Code:
<sparsing enabled="true" max-sparse-size="536870912"/>
<step operation="getvar" var="max-sparse-size"/>
in it.
Do they matter at all?
When I run the fastboot command I get a different number
Code:
sudo fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.008s
So, I fixed it. And yeah, you need to fastboot stock in the same order as the flashfile.xml and include the getvar max-sparse-size. Here is what worked for me. I got no errors besides the "bad key" for boot and recovery images.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash oem oem.img
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
sudo fastboot reboot

[solved] failed to load kernel - cant do anything

hey,
I am a noob when it comes to rooting devices and I kinda ****ed up on my 2 year old device.
When I try to start my device, I get this error:
Start up failed:
Your device didnt start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume key pressed
USB connected
cmd: getvar:slot-count
cmd: getvar:slot-suffixes
cmd: getvar:slot-suffixes(note: yes, 2 times)
cmd: getvar:has-slot:recovery
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:009ff000
cmd: flash:recovery
Error: failed to load kernel!
Boot up failed
my problem is, that no matter how I try to start or factory reset my phone, I sooner or later land on that screen. I can use fastboot commands just fine, but I dont know which I need to use. TWRP cant be started, because I need to press "Recovery Mode" at one point which sends me back to the above error.
I am stuck since half a day and I honestly cant figure it out myself. I hope you can help me to root my phone. many thanks,
Termii
Edit 1: trying the following commands:
C:\Users\Desktop\reboot\platform-tools>fastboot devices
ZY2245QMTN fastboot
C:\Users\Desktop\reboot\platform-tools>fastboot erase recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Desktop\reboot\platform-tools>fastboot flash recovery recovery.img (note: recovery = TWRP 3.1.1-0 Moto G5S Plus [sanders])
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10236 KB)...
OKAY [ 0.284s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.231s]
finished. total time: 0.519s
C:\Users\Desktop\reboot\platform-tools>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.007s
the error my moto shows me:
Start up failed:
Your device didnt start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from recovery boot mode USB connected
Edit 2:
C:\Users\Desktop\reboot\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245QMTN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 24F61D6D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from recovery boot mode
(bootloader) imei: ********
(bootloader) meid:
(bootloader) date: 05-16-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 14 3:14:15 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.11.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.06R POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g64ca40a-0012
(bootloader) kernel.version[1]: 8-g77c6b6b ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Aug 8 08:37:28 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.177s
solution
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
termii10 said:
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
Click to expand...
Click to collapse
You might want to edit out your IMEI from the post.
thanks. what is it for btw?
termii10 said:
thanks. what is it for btw?
Click to expand...
Click to collapse
It uniquely IDs a mobile phone, used by carriers to identify stolen devices and disconnect them from the network. If someone else gets a hold of it, they could use it for their illegal device rendering your phone unusable.
termii10 said:
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
Click to expand...
Click to collapse
This worked for me as well.
Failed to load Kernel.
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Tropicalvibes said:
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Click to expand...
Click to collapse
I suggest you to use lenovo moto smart assistant app to flash the device, as it will flash your device for you.
riyan65 said:
I suggest you to use lenovo moto smart assistant app to flash the device, as it will flash your device for you.
Click to expand...
Click to collapse
thanks for your answer, I did it already, it does not work cuz it cannot get enough information from the phone.
Tropicalvibes said:
Failed to load Kernel.
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Click to expand...
Click to collapse
hello, could you solve it?

slot-count not found, slot-suffixes not found,bootloaer working fine

Hello,
I've recently tried to flash stock recovery to be able to receive update . I had TWRP installed already . But whenever I type fastboot command , I get error like slot-count not found .
And that's not the case . I've tried with flashing bootloader and gpt.bin as well and get the same error ! My bootloader is working fine! Also whenever I try these steps, I end up losing my WiFi/hotspot connectivity !
Here take a look . I get these errror in ADB :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe O
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\User
s\MAYUR Desktop\New folder recovery.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.529s]
writing 'recovery'..
<bootloader) Image signed with key bad key
OKAY [ 9.668s]
finished. total time: 1.204s
rs\MAYUR\Desktop\New folder\gpt.bin"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition "C:\Use
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
<bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing partition'.
(bootloader) Flashing prinary GPT image..
(bootloader) Flashing backup GPT image...
OKAY [ 9.093s]
finished. total time: 0.106s
C:\Program Files (x86)\Minimal ADB and Fastboot >fastboot flash bootloader "C:\US
ers\MAYUR Desktop\New folder\bootloader.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.124s]
writing 'bootloader'.
(bootloader) validating: bootloader.default.xml
(bootloader will pass: flash:aboot
<bootloader) will pass: flash:tz
(bootloader) will pass: flash: rpm
(bootloader) will pass: flash: hyp
(bootloader will pass: flash: keymaster
(bootloader) will pass: flash:cmnlib
(bootloader will pass: flash sbli
(bootloader) committing: bootloader.default.xml
bootloader> flashing 'emmc_apps boot.mbn' to 'abooty
(bootloader) flashing 'tz.mbn' to 'tz'
<bootloader) flashing rpm.mbn' to rpm'
(bootloader) flashing 'hyp.mbn' to 'hyp'
(bootloader flashing 'keymaster.mbn' to 'keymaster'
bootloader) flashing 'canlib.mbn' to 'canlib'
OKAY [ 0.608s]
(bootloader) flashing 'sbll.mbn' to sbli'
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
(Getvar all) returned this : ?
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe
C:\Users\MAYUR\Desktop\New folder>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
<bootloader) version: 0.5
(bootloader) version-bootloader: moto-nsm8952-B1.07
bootloader) product: athene 16mp
<bootloader board: athene_16mp
<bootloader) secure yes
<bootloader) hwrey: P2A
<bootloader) radio: 4
<bootloader) storage-type ennc
<bootloader) emnc 16GB SAMSUNG QE13MB RU-08 PU-7 FU-OOOOOOOOOOOOOOOD
<bootloader) ran: 2GB SAMSUNG LP3 DIE=8Gb M501 M6-05 M2=00 M8 -17
(bootloader) cpu MSM8952
(bootloader) serialno: *protected*
<bootloader) cid: Ox0032
<bootloader) channelid: Oxco
(bootloader) uid: 2E2FAAOOOOOOOOOOOOOOOOOOO000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvo id: yes
(bootloader) reason: Volume down key pressed
bootloader> max-download-size: 536870912,
<bootloader) meid:
(bootloader) imei: *protected*
<bootloader) date: 05-31-2016
<bootloader) sku: XT1643
<bootloader) battid: SNN5966A
bootloader> max-sparse-size: 268435456
<bootloader) iccid:
<bootloader) cust_md5:
(bootloader> current-time "'Sat Apr 30 0:19:14 UTC 2016"
(bootloader) ro.build.fingerprint [0]: motorola/athene/athene:2.0/NPJS25.
bootloader) ro.build.fingerprint(1): 93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
bootloader) ro.build.version.full[1]: il.en.US
bootloader) version-baseband: M8952_70030.25.03.62.02R DFLT_FSG
(bootloader) kernel.version [1]: 2526f <hudsoncneilclbld72) (gcc version
<bootloader) ro.build.version.qcon: LA.BR.1.3.6-01210-8926.0
bootloader) kernel.version [0]: Linux version 3.10.84-ge03508d-00131-944,
bootloader) kernel.version [2]: 4.8 (GCC) > 111 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version [3]: :58:16 CDT 2018
(bootloader) tz.git: git-69dd24b-dirty
(bootloader) rpm.git: [email protected]
<bootloader) sbl1.git: git-MBM-NG-UB1.07-6-952d1343
(bootloader) hyp.git: git-69dd24b-dirty
(bootloader) cmnlib.git:git-69dd24b-dirty
(bootloader) aboot.git: git-MBM-NG-UB1.07-0-9f9b89ba
bootloader> keymaster-git: git-69dd24b-dirty
(bootloader) ro.carrier: retin
(bootloader) frp-state: no protection (0)
<bootloader> qe: qe 0/1
all: listed above
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I've read all the related forum but none of them is similar to mine ! They say we've have to blank flash the bootloader . But mines working fine . Do I really need to blank flash or something else would work fine ? If i really need to blank flash , then pls guide me !
Thank you very much in advance !
Have a great day ?
P.S. = sorry if the related thread already exist !
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Sir I've flashed RR, INVICTA,and many other ROMs but... Didn't face this issue before ... I've recently flashed stock firmware provided by @rajatgupta1998 in this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/amp/ .. and ended up here !! The thread you provided as reference is an older discussion where he downgraded his bootloader by flashing ROM from different Android version ... But I've done nothing like that ! Please help me how to het the radio working ! Thanks in advance sir !
echo92 said:
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Click to expand...
Click to collapse
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply ??
Vs1607 said:
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply
Click to expand...
Click to collapse
Does your computer detect your device when you connect via USB whilst booted in TWRP (does your device appear in Device Manager if you're using Windows?) and what version of TWRP are you using? What version of fastboot/ADB do you have installed on your computer?
I'm not that familiar with helping to losing baseband - that's why I referred you to that thread - though it's old and perhaps not exactly what happened to your device, there may be some useful information as to fixing your device.

Im in a chicken egg situation, please help!

So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...
cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Thanks
sd_shadow said:
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Gonna try, i will post the updates as soon as i can!
Update
sd_shadow said:
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
"Failed to match the connected device.
Reconnect device, then try again."
The phone is connected and in fastboot mode.
UPDATE 4
cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...
Click to expand...
Click to collapse
I attach a getvar all for you
>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY3232R25R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(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: IHAVEIMEIBUTICENSOREDIT
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 4068
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.203s
cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...
Click to expand...
Click to collapse
If your phone is currently flashed with the stock rom, the only way to fix bootloader lock would be to enter edl mode. That means hard bricking on purpose ?
reply
mrsiri said:
If your phone is currently flashed with the stock rom, the only way to fix bootloader lock would be to enter edl mode. That means hard bricking on purpose
Click to expand...
Click to collapse
can you explain to me how i can do that? also sorry for not replying on time,i have same internet issues.
Also i need all the help i can get, because my moto g4 is slowly dying, having ghost touchs, etc. i want to use the g6 +
actualization
So i found a nano sim to try on, and the phone didnt read it, its like i didnt put the sim.
Now im desperate, i tried to formate the phone via fastboot, got this message:
PS C:\Users\cowb0y\Desktop\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.387s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.392s
i noticed that one partition is on raw format.
I dont know what to do anymore.
cowb0y said:
I attach a getvar all for you
>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY3232R25R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(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: IHAVEIMEIBUTICENSOREDIT
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 4068
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.203s
Click to expand...
Click to collapse
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml
reply
sd_shadow said:
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml
Click to expand...
Click to collapse
i think a got a netbook with w7 to try rsd lite, gonna try in a few hours and post the results.
No, im trying with the 116-11-16 versions https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-16_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml.zip (and the same but from 2019 date)
i will try with the version you handed me.
I give up
sd_shadow said:
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml
Click to expand...
Click to collapse
Well i installed w7 to try rsd, but all i got is "failed to switch to fastboot" the phone is already in bootloader mode.
Also try to flash manually the version that you give me, but got error on at least 5/6 files, retry, and all good, but still the same problem.
I dont know what to do anymore, tomorrow i will take the device to a "technician" i dont have hope on this...

Resources