Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
Related
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 !
Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.
anyone can help
t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14
Still waiting too.
Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck
just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie
HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.
Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks
I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/
Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.
I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?
Looks like no solution
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.
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?
Hello everyone.
I got this problem today. My Mi A1 doesn't want to unlock the bootloader, and I follow all the instructions. In the cmd, when I type "fastboot oem unlock", this error appears "remote: unlock is not allowed".
Besides, the smartphone is frozen on the screen of initialization of Mi, making it impossible for me to go in the administrator options of the device.
Please describe what you did to the phone before it got to this state.
_mysiak_ said:
Please describe what you did to the phone before it got to this state.
Click to expand...
Click to collapse
I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.
As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.
However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.
Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?
_mysiak_ said:
Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?
Click to expand...
Click to collapse
I sure, the system was Android 8.0. Android One.
Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.
Chiggie14899 said:
Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.
Click to expand...
Click to collapse
Like I said, I can't. My smartphone is in mode bootloop.
Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.
nicobelic said:
Like I said, I can't. My smartphone is in mode bootloop.
Click to expand...
Click to collapse
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
_mysiak_ said:
Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_TISSOT2.0_20180504180424
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) slot-count:2
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:7
(bootloader) slot-success:_b:No
(bootloader) slot-active:_b:No
(bootloader) slot-unbootable:_b:No
(bootloader) slot-retry-count:_a:7
(bootloader) slot-success:_a:Yes
(bootloader) slot-active:_a:Yes
(bootloader) slot-unbootable:_a:No
(bootloader) has-slot:userdata: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:keymasterbak: No
(bootloader) has-slot:keymaster: No
(bootloader) has-slot:cmnlib64bak: No
(bootloader) has-slot:cmnlib64: No
(bootloader) has-slot:cmnlibbak: No
(bootloader) has-slot:cmnlib: No
(bootloader) has-slot:lksecappbak: No
(bootloader) has-slot:lksecapp: No
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: No
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slotersist: No
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:abootbak: No
(bootloader) has-slot:aboot: No
(bootloader) has-slot:splash: No
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slotDR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: No
(bootloader) has-slot:devcfgbak: No
(bootloader) has-slot:devcfg: No
(bootloader) has-slot:tzbak: No
(bootloader) has-slot:tz: No
(bootloader) has-slot:rpmbak: No
(bootloader) has-slot:rpm: No
(bootloader) has-slot:sbl1bak: No
(bootloader) has-slot:sbl1: No
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xcd3779e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) crc:1
(bootloader) serialno:349794d29805
(bootloader) kernel:lk
(bootloader) product:tissot
all:
finished. total time: 0.776s
mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
Click to expand...
Click to collapse
This shows up:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
Click to expand...
Click to collapse
This shows up:
PHP:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
nicobelic said:
This shows up:
PHP:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash
mardrest said:
If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash
Click to expand...
Click to collapse
To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.
nicobelic said:
To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.
Click to expand...
Click to collapse
Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .
Custom rom 243 said:
Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .
Click to expand...
Click to collapse
As he said he can't get into the rom
ProchyGaming said:
As he said he can't get into the rom
Click to expand...
Click to collapse
Oh that's why I thought such a obvious reason was not told by anyone .
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
nicobelic said:
I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.
As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.
However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.
Click to expand...
Click to collapse
Could you follow that same procedure of locking OEM and then booting into the ROM ? (,Just asking,not giving a solution)
mardrest said:
Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
Click to expand...
Click to collapse
I install the driver, write "fastboot oem edl" command, nothing changes.
I think I screwed up realy bad.
This is happening
I found a video that shows the SAME PROBLEM I'm having with my Mi A1.
Why can not I fix the problem? I can not unlock the bootloader.
https://www.youtube.com/watch?v=51LnEOrM3nQ
This shows up when I tried: https://imgur.com/uAVuFle