Database Users

XT1572 every time reboot enter in mode fastboot

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

LG V20 US99610f Flashing TWRP assistance.

So here's my story.
V20 Bootloader unlocked via LG's web site.
US996 version 10f
DEveloper and usb debugging enabled also side load usb.
USB set to photo transfer.
This one setting has me wonder under getvar all (bootloader) secure:yes
I boot into fast boot by plugging in usb cable while holding volume -
Issue the following commands below first to verify device then to flash .(Basically I renamed twrp-3.0.2-1-us996.img to recovery.img)
It then says finished after flashing recovery, I unplug the usb cable and pull the battery.
Put battery back in, hold down volume - and power button. LG splash comes up, I release then
press the power button.
From there I get a white factory reset data sreen.
I feel like I'm missing a step yet I don't.
All suggestions welcome.
My goal is to flash TWRP then Magisk.
c:\adb1>fastboot devices
LGUS99636487ef4 fastboot
c:\adb1>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP 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: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS99636487ef4
(bootloader) kernel:lk
(bootloader) product:MSM8996
(bootloader) unlocked:yes
all:
finished. total time: 0.200s
c:\adb1>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24076 KB)...
OKAY [ 0.588s]
writing 'recovery'...
OKAY [ 0.251s]
finished. total time: 0.839s

If you have flashed TWRP onto the recovery partition you can go ahead and continue with the "factory reset". Typically this would issue a factory reset using the stock recovery image, but if you have TWRP it'll just take you to TWRP instead.
Just be sure to flash TWRP in fastboot and then immediately factory reset to enter TWRP. Once in TWRP make sure to "allow modifications". This will prevent the stock recovery from returning. If you boot into the system without allowing TWRP to "modify" the system (remove the stock recovery restoration) it will reset your recovery back to the stock on system boot. If the stock recovery ends up restored and you issue a "factory reset", it'll actually factory reset.

Nut, you effin rock.
That was it, Twrp and rooted woo-oo!!
Was there another step for safety net to work?

landude said:
Nut, you effin rock.
That was it, Twrp and rooted woo-oo!!
Was there another step for safety net to work?
Click to expand...
Click to collapse
You're welcome! Great to hear it all worked out.
No extra steps for safety net. Just install the latest Magisk (14.0) and you should pass safety net without issue. The magisk manager application can do a check for you to verify you pass.

And it did! Thanks again!

landude said:
And it did! Thanks again!
Click to expand...
Click to collapse
I'll be receiving a US996usatn by the weekend and I'm trying to get the process down. I'm getting confused with all the dirty santa, dirty elf, and recowvery stuff.
In my case, I believe none of that is needed, correct?
Did you flash the "no-verity" zip at all in your unlock and root process? I'm not sure what it is or if it's needed with the US996.
What I think should be done (please correct if I'm wrong):
Unlock BL thru LG dev site instructions
Flash twrp
Boot twrp with button combo
Factory reset white screen>yes
Swipe to Allow modification
Wipe data
Flash Magisk or SU
Done?
From all that I've read, your original post made the most sense to me and hopefully is the only method I need to know to root.

Moto G4 Plus boot to TWRP problem

Morning,
I have a Motorla G4 plus UK model XTN1642 I rooted this and installed TWRP when I first bought it several months back.
Yesterday, I got the 'update is avaialble' notification and follishly I allowed it to download and then install which failed, now the phone will only boot to the TWRP screen each time it restarts.
However, If I boot into bootloader then manually click 'Start' the phone will boot normally, but this is not ideal.
The phone is running stock Android 7.0 build number NPJS25.93-14-4, i've tried reading the forum but there is quite a lot that I don't understand and I don't want to make it worse by killing it completely and then not having a phone to use.
Can anyone give me a straight forward way to get the phone to boot up normally without having to go through bootloader and then manually click start?
I'm hoping that it is something simple, I don't have any backups of the device either!

Look, with twrp installed there's no way to update via ota. That's why I reflashed stock rom for getting the ota update. Although I planned to flash 6.0 M stock initially, I managed to flash 7.0 N stock ROM since it was available on this forum.
The version I have at the moment is 25.93.14.10 which is the September 2017 security patch. My another G4 absolutely untouched received ota today from 14.4 March patch to 14.13 December patch. I am not quite sure what happened to my 14.10 September patch. Why there is no ota? Maybe because this ROM was found on the G4+ forum?
Back to your question, find a stock ROM to flash, don't install twrp as it will modify the recovery. For install ota you will need to keep the ROM completely untouched.

Hi,
Yes, I am aware of that now but at the time I wasn't or else I wouldn't have done it.
But, after reading through teh forum, I followed this https://forum.xda-developers.com/moto-g4/help/ota-upgrade-7-0-twrp-installed-t3727807 after which the device booted normally again.
I should have left it at that, but again, I was notified of the update, so having read the thread above, let it go ahead, it download the update and rebooted., I then tried to root again and install twrp and elementalx and now it doesn't boot just get a black screen, I can still get into twrp and bootloader though.
Here is what I get from fastboot getvar all
C:\Program Files\Minimal ADB and Fastboot>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-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: E492B10000000000000000000000
(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-30-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:53:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.562s
I've blanked out the IMEI and Serial number in the above
I guess I should have left it ater getting it back and booting, but it sort of made sense to do the update then I needed to root it again.
What now?

right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !

ffrlr said:
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
Click to expand...
Click to collapse
How are you rooting, and what software are you using?
The general order for rooting is to:
1)Flash/boot TWRP. Either the official TWRP (3.2.1 - https://dl.twrp.me/athene/ ) or shreps' TWRP should suffice: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
2)In TWRP, backup your stock ROM and make a separate copy of your kernel (boot) partition.
3)Flash ElementalX or another custom kernel. Ensure this happens before you root else you'll bootloop. ElementalX v1.04 or v2.0 is here: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
3a)Wipe cache and Dalvik. At this point, you may wish to boot and check your device is working. If so, proceed to 4)
4)In TWRP (or boot back to TWRP), flash the root manager of your choice, either SuperSU v2.8.2 SR5 https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 or magisk 14/15. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Do not mix and match root managers without fully uninstalling and flashing the stock kernel again (hence the separate backup you made in 2)).
5)Wipe cache and Dalvik if not done in 3a) and reboot.
6)Any issues, revert to your backup made in 2).
This should give you a device booting with the latest stock ROM and rooted. This procedure is working on a XT1642 with NPJS25.93-14-13 (same firmware as you have now) and ElementalX v2.0 and magisk 15.3. As I linked in the other thread you've seen, you may wish to disable the Motorola updater to stop you from getting into another TWRP bootloop.
Hope that helps.
EDIT - have a look at this thread too: https://forum.xda-developers.com/moto-g4/how-to/guide-how-to-root-moto-g4-magisk-stock-t3725712/

Hi
thank you for the reply, very much appreciated, I'm keen to get my phone rooted again as I use 'timed toggles' to switch the phone into aeroplane mode when i'm asleep etc.
When I last rooted it after I bought it, I used magisk from what I recall, but I amnot really fussy to be honest.
Yesterday, I bravely attempted several times to install twrp in fact it was the shreps version which I found a link to, but for some reason I cannot get it to install.
I boot the phone using volume down button and power, then connect to the pc, then type fastboot flash recovery twrp-3.1.1-athene_shreps.img.
during the flash, I get the following
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
I then immediately boot to recovery using the volume keys and power button, after the device reboots, I don't get TWRP, justa dead android lying on it's back with a red exclamation mark above it, beneath is written no command.
I've had about four goes, but each time I get the same, am I missing something?, i've followed various threads and tutorialsd to no avail.

Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.

ffrlr said:
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
Click to expand...
Click to collapse
Good to hear it worked I'm glad that it worked on your other computer - Windows 10 appears to cause some headaches on flashing - I don't know if it's to do with the driver signature enforcement, that I don't think Windows 7 has. I've not had issues with Windows 10 flashing for the most part, though I do have a computer with a BIOS and not UEFI - though that being said, last time I flashed TWRP (shrep's TWRP), it didn't stick and required another re-flash, so maybe it's to do with the updated B1:07 bootloaders in both cases?
By the way, that 'image not signed or corrupt' message when flashing TWRP is normal and expected. TWRP is not cryptographically signed with the keys that the system/fastboot is expecting, so it's simply a message to alert you.
Have fun with your new root powers (please use responsibly )

MOTO G5 PLUS, stuck in fastboot flash mode

Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
C:\ProgramData\RSA\Download\newfolder>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
The Rescue and Smart Assistant software isn't working because the IMEI is showing all 0 (zero) here. And it says something is wrong and should go to customer support. Please help me guys. Let me know what should I do now? It is out of warranty as well.
For the image files I am using the same I downloaded via the rescue and smart assistant software.
#motog5 #motog5plus #oem_locked.

ssoni0097 said:
Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
Click to expand...
Click to collapse
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot

jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
But the phone is not turning on na .. It is stuck on the fastboot flash mode screen. How do I unlock the oem then

Try
Code:
fastboot reboot
to exit Fastboot mode

jwoegerbauer said:
Try
Code:
fastboot reboot
to exit Fastboot mode
Click to expand...
Click to collapse
The fastboot opens again. As I said, it is stuck there.
On selecting start on fastboot, it says
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed.

Try to re-flash phone's Stock ROM.

jwoegerbauer said:
Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
How to do that? Can you please help .. please
I tried following some steps, downloading the files from a website. But it results into fail.
Fix a dead Moto G5 plus and fix bootloop problem Animetrick
Recently my moto g5S plus got stuck on moto screen and I was flash with this method and this got worked on my phone. Now my phone was completely working and
animetrick.com
for example:
C:\Program Files (x86)\Minimal ADB and Fastboot1>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.157s

@sd_shadow can you help please?

What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.

jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s

jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
Motorola devices require an unlock code
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com

ssoni0097 said:
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s
Click to expand...
Click to collapse
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
I generally do not use mfastboot, it has not been updated in years.
but if fastboot.exe fails, it doesn't hurt to try mfastboot.

sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
https://file.io/EEveR0bZCRDV
Tried the rescue and smart assistant tool as well. But it catches the imei as 0, and stops there.
Removed imei line below:
Code:
C:\ProgramData\RSA\Download\newfolder>mfastboot getvar all
< waiting for device >
(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 SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 3fb4905f
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 7D81062600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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.081s

sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.

ssoni0097 said:
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.
Click to expand...
Click to collapse
What does getvar all say?

sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
MOTO G5 PLUS, stuck in fastboot flash mode
Failed to pass validation, backup to fastboot Boot up failed. The flashboot flash mode screen says: Product/Variant : potter 000000000000000 32GB P3B .... oem_locked All variables: https://file.io/rF0SqpBhP398 On running the cammands...
forum.xda-developers.com
Posted it above

ssoni0097 said:
Posted it above
Click to expand...
Click to collapse
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com

Wolfcity said:
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
Click to expand...
Click to collapse
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s

ssoni0097 said:
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Did you check if your devices bootloader is unlockable at all?
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I would recommend to not use mfastboot as it is outdated. Better try this one:
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
As written above, best may be to flash the latest signed firmware and start from scratch.
Follow this tutorial (the upper part):
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com

TicWatch Pro 3 Ultra - Endless bootloop - only fastboot - Kali Nethunter

Hey community,
i bought the watch to be able to use kali linux on it. It is the model "TicWatch Pro 3 Ultra LTE".
Therefore, I have made myself directly to the work:
* DIY USB Data cable built - check
* Flashed Kali Nethunter (https://www.kali.org/docs/nethunter/installing-nethunter-on-the-ticwatch-pro3/) according to instructions - check to point "2.12 - Flash Disabler with “adb sideload".
(No backup made via TWRP - first mistake)
"Flash Disabler with “adb sideload” led to an error message because no volume button was pressed. (Question of the setup if disk quota should be changed).
From there it went off....
* Restarted the watch (probably another mistake:/)
* Afterwards booted into recovery and copied the "Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" to /sdcard via `adb push`.
* With "install ZIP" successfully installed
* Reboot = Bootloop
Now I only get into the "fastboot". Neither booting into the recovery nor into the OS is possible and the watch restarts continuously.
I have tried the following without success:
* Via fastboot flash the recovery and restart ".\fastboot.exe flash recovery rover_recovery.img".
* Via fastboot directly into the recovery boot ".\fastboot.exe boot rover_recovery.img"
* Via fastboot clear userdata and cache "./fastboot.exe -w"
It remains unchanged: Bootloop + only boot into fastboot is possible.
I have refrained from trying other things, because I do not want to destroy the watch irretrievably.
Is there someone who can help me to bring the watch back to life?
I am grateful for any help, because I really despair.
Greets TCL7070x

Hello together,
tried different ways to get live back into the watch.. without success.
Even flashing the stock rom from https://wear.revtechs.me/en/download (scroll to the end of the page) via fastboot did not work and the watch stucks in the bootloop. I've done
* fastboot flash boot boot.img
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
and even tried
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Does anyone have an idea and would share it with me?
Thanks in advance!
Greets TCL7070x

TCL7070x said:
Hello together,
tried different ways to get live back into the watch.. without success.
Even flashing the stock rom from https://wear.revtechs.me/en/download (scroll to the end of the page) via fastboot did not work and the watch stucks in the bootloop. I've done
* fastboot flash boot boot.img
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
and even tried
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Does anyone have an idea and would share it with me?
Thanks in advance!
Greets TCL7070x
Click to expand...
Click to collapse
Hey buddy, I made this account just to reply to this thread lol
I bought a Ticwatch pro 3 ultra GPS (despite having read your post beforehand, thinking it wouldn't happen to me), and ended up getting stuck on an infinite boot screen.
Once the recovery was installed, I was able to boot after these steps:
Flash OneOS with adb sideload
Flash Mobvoi Apps with adb sideload
But once I did these steps, I could no longer boot into OneOS, I just got an "infinite" loading screen:
Make a copy of your Magisk apk file to Magisk-v24.3.zip
Flash Magisk with adb sideload
Flash Disabler with adb push disabler.zip /sdcard/ and Install via TWRP
I don't know why those steps need to be peformed because the OneOS help page doesn't mention it.
Note - it is totally possible that I was too impatient during the first boot & f*cked everything up by not waiting long enough for it to boot. I just saw that the OneOS help page says:
- Restart the system each reboot / first start will take longer than normal, it is because of the deodex.
Once in the bootloader, I am able to get into the TWRP recovery by using the buttons of the watch.
I made a backup before doing all of this so I will try to restore it and see if that let's met boot again, or start from scratch. I just need to re-solder the wires of my USB cable, since they fell off whilst fooling around last night.
I can send you my backup files so you can restore them, there is no personal data on them, it's just a backup of the default storage; which was performed the first time I was able to get into TWRP.

Hold both watch buttons for 10 seconds to get into the bootloader mode.
Press the bottom button to change option selection until you see "recovery mode".
Press the top button to enter/execute selection & boot into recovery mode.
If that doesn't work, maybe you could try:
fastboot boot rover_recovery.img
That should load twrp.
Also, take a look at this thread:
[Solved] Bootloop on FP4 after a wrong "fastboot boot twrp.img"
Hello! I was doing several experiments with TWRP on FP4, always booting it temporally with the “fastboot boot twrp.img” command. Then I did something stupid, I didn’t pay attention and I tried to boot on a FP2 TWRP image that unluckily was still in the same directory (from last month trials...
forum.fairphone.com

Hey @HarmlessHacker,
happy to hear that you've registered just to reply. Welcome @ xda-developers
I've tried so many things that i can't bring it into the right order. But:
One thing i've tried was your mentioned TWRP flashing: `fastboot boot rover_recovery.img`
The closest state i got was that TWRP booted and about 1 to 2 sec. after that the watch restarted right away. The watch "does not care" what is booting... after the bootloader "unlock warning" was displayed it takes another 2 to 3 seconds. Then the watch vibrates and restarts immediately.
Depending on what I flash, still happens the following sequence:
* TicWatch Logo -> Bootloader -> Black Screen -> Vibration (Reboot).
and directly after that
* TicWatch Logo -> Bootloader -> Vibration (Reboot)
It looks like the watch tries to start something for a short time. But afterwards discard this directly, regardless of success (as described above the display of TWRP).
I would be very happy to receive the backup. Even if it is the firmware for the GPS mode. I guess worse than "bootloop of death" isn't possible. And maybe it's worth a try
it can't be that this doesn't work ;D

Can you try the fastboot boot rover_recovery.img with the --verbose or -v option and share the output?
I'm new to android modding, but I noticed some fastboot options that might help (fastboot --help)
Code:
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--verbose, -v Verbose output.
POTENTIALLY DANGEROUS IDEA (use with options above):
You might be able to try to force boot of the image (don't use with flash comand, only boot):
--force Force a flash operation that may be unsafe.
You can get more info about your current slots and all other variables use this:
fastboot getvar all
...look for (bootloader) current-slot: in the output
If it looks something like this:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
maybe try something like this:
fastboot --set-active=b --verbose
Source:
[Solved] Bootloop on FP4 after a wrong "fastboot boot twrp.img"
Here hidden is the full getvar all <details><summary>getvar all</summary>fastboot getvar all (bootloader) parallel-download-flash:yes (bootloader) hw-revision:10000 (bootloader) unlocked:yes (bootloader) off-mode-charge:0 (bootloader) charger-screen-enabled:0 (bootloader)...
forum.fairphone.com

Of course, i can:
Here is the output from booting via fastboot with verbose mode ('.\fastboot.exe boot ..\..\..\rover_twrp.img --verbose'). Unfortunately no change between verbose and non-verbose mode:
Code:
Sending 'boot.img' (26682 KB) OKAY [ 0.843s]
Booting OKAY [ 11.621s]
Finished. Total time: 12.561s
and this is the output of all vars ('.\fastboot.exe getvar all'):
Code:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3770009
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:rover-03.02.38.03.16
(bootloader) logical-block-size:0x200
(bootloader) erase-block-size:0x200
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1feffc00
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x12d0e8e00
(bootloader) partition-type:btlver:raw
(bootloader) partition-size:btlver: 0x400
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:mcfg:raw
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:mdtpbak:raw
(bootloader) partition-size:mdtpbak: 0x2000000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:oem:raw
(bootloader) partition-size:oem: 0x1000000
(bootloader) partition-type:config:raw
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4000000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x20000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x60000000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:ext4
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:dtbobak:raw
(bootloader) partition-size:dtbobak: 0x800000
(bootloader) partition-type:dtbo:raw
(bootloader) partition-size:dtbo: 0x800000
(bootloader) partition-type:abootbak:raw
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:raw
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0xb00000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:DDR:raw
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:raw
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:raw
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x5400000
(bootloader) hw-revision:10000
(bootloader) serialno:<REDACTED>
(bootloader) kernel:lk
(bootloader) product:rover
all:
Finished. Total time: 0.350s
The behavior of the watch directly after trying to boot into the recovery:
It is looping through these stages:
* Logo -> Bootloader -> Logo ~8sec -> Vibration (Reboot) and black screen
(does not reach the TWRP screen at all)
Based on the video you sent me: I understand that vbmeta is a "mini os" that is responsible for verifying the other partitions, including the boot partition. If I understand correctly, vbmeta uses the key stored on the device in the keymaster partition (?)?
By flashing vbmeta with `.\fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img` this cryptographic verification is turned off, right?
All in all, it sounds like it's related to vbmeta blocking the boot process? Or I understand it completely wrong ;D
Anyway, thanks for going through this with me

There has been an update to the documentation from OneOS. They changed domains, I think mobvoi is being hostile towards 3rd party developers (based on the fact that they removed they removed the data pins from the included charger)
https://wear.lunawolf.es/en/ayuda

To force the watch to get into the bootloader, hold both buttons until you see the menu, from there you should be able to use the fastboot command to flash the recovery image again
Make sure to wipe the "data" partition when finished or you will not be able to boot

Hey, every time you answer, i get a bit hope back ;-)
Thanks for the new link to wearOS. Didn't see that.
Another day.. another try... I've tried to boot into TWRP again and followed the steps at the website + your recommendation to clean the data patition:
Code:
.\fastboot.exe erase userdata
.\fastboot.exe erase cache
.\fastboot.exe flash recovery fresh_downloaded_from_wearos_twrp_rover.img
.\fastboot.exe --disable-verity --disable-verification flash vbmeta fresh_downloaded_from_wearos_vbmeta.img
.\fastboot.exe reboot recovery
Another try was, to use the boot.img of the current OneOS release, because i've tried the same with the stock rom:
Code:
.\fastboot.exe flash boot .\OneOS-21.10.8_rover\boot.img
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe reboot recovery
Without any luck :/
No change in it's behavior - even between both tries.
i am confused and do not know what to do :/
It feels that everything i try won't work at all

Make sure that you are flashing the correct recovery and custom rom from https://wear.lunawolf.es/en/descargar
There might have been updates since you last downloaded them. There are many warnings about not being able to boot if done incorrectly.
Can send me a video of the bootloop and your attempt to get into the recovery mode using these steps:
Hold both watch buttons for 10 seconds to get into the bootloader mode.
Press the bottom button to change option selection until you see "recovery mode".
Press the top button to enter/execute selection & boot into recovery mode.
if that doesn't work, maybe try this:
Factory reset from recovery on Ticwatch E? - Wear OS by Google Community
--------------------------------------------------------------------
OneOS news updates:
• NEWS • ONE Projects
ONE Team Projects News Channel Spanish Group: ETASOON English Group: ETASOON MIUI (END OF LIFE): Downloads: @OneOS_Weekly Stable Base: @OneOS_Stable PayPal: https://PayPal.me/badwolfalfa WEB: http://one.revtechs.me System Status: ESTASOON
t.me
https://twitter.com/RevOSTechs
Everything is hackable... you got this.

Also, be careful with "Disable DM Verity"
RECOMMENDED TO DO UNDER CLEAN INSTALL OR DEVICE MAY NOT START
(dont flash it twice)
I don't think you got that far yet, but I just wanted to give you a heads up!

You might also be able to flash the stock rom and hopefully get it out of the boot loop:
Descargar | OneOS Wear
wear.lunawolf.es
Try fastboot boot rover_recovery.img (without the "flash" option) to boot the recovery as a troubleshooting step or fastboot reboot recovery
I also noticed that it helps to store the files on the ticwatch rather than the PC, I forget exactly which one was problematic.
This video helped me figure it out:
Adb useful commands list
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Good Luck!

HarmlessHacker said:
You might also be able to flash the stock rom and hopefully get it out of the boot loop:
Descargar | OneOS Wear
wear.lunawolf.es
Try fastboot boot rover_recovery.img (without the "flash" option) to boot the recovery as a troubleshooting step or fastboot reboot recovery
I also noticed that it helps to store the files on the ticwatch rather than the PC, I forget exactly which one was problematic.
This video helped me figure it out:
Adb useful commands list
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Good Luck!
Click to expand...
Click to collapse
Nice video

TCL7070x said:
Hey community,
i bought the watch to be able to use kali linux on it. It is the model "TicWatch Pro 3 Ultra LTE".
Therefore, I have made myself directly to the work:
* DIY USB Data cable built - check
* Flashed Kali Nethunter (https://www.kali.org/docs/nethunter/installing-nethunter-on-the-ticwatch-pro3/) according to instructions - check to point "2.12 - Flash Disabler with “adb sideload".
(No backup made via TWRP - first mistake)
"Flash Disabler with “adb sideload” led to an error message because no volume button was pressed. (Question of the setup if disk quota should be changed).
From there it went off....
* Restarted the watch (probably another mistake:/)
* Afterwards booted into recovery and copied the "Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" to /sdcard via `adb push`.
* With "install ZIP" successfully installed
* Reboot = Bootloop
Now I only get into the "fastboot". Neither booting into the recovery nor into the OS is possible and the watch restarts continuously.
I have tried the following without success:
* Via fastboot flash the recovery and restart ".\fastboot.exe flash recovery rover_recovery.img".
* Via fastboot directly into the recovery boot ".\fastboot.exe boot rover_recovery.img"
* Via fastboot clear userdata and cache "./fastboot.exe -w"
It remains unchanged: Bootloop + only boot into fastboot is possible.
I have refrained from trying other things, because I do not want to destroy the watch irretrievably.
Is there someone who can help me to bring the watch back to life?
I am grateful for any help, because I really despair.
Greets TCL7070x
Click to expand...
Click to collapse
Bro inbox me i will help u
If i not responding here
Text me o whatsappWasap.my/60142222872

@TCL7070x
According to this thread: Factory reset from recovery on Ticwatch
You can actually boot into recovery by fastboot oem reboot-recovery but it only displays a big exclamation mark and nothing else.
Click to expand...
Click to collapse
Go to 6:24 to see how to get to bypass that exclamation mark

TCL7070x said:
Hey, every time you answer, i get a bit hope back ;-)
Thanks for the new link to wearOS. Didn't see that.
Another day.. another try... I've tried to boot into TWRP again and followed the steps at the website + your recommendation to clean the data patition:
Code:
.\fastboot.exe erase userdata
.\fastboot.exe erase cache
.\fastboot.exe flash recovery fresh_downloaded_from_wearos_twrp_rover.img
.\fastboot.exe --disable-verity --disable-verification flash vbmeta fresh_downloaded_from_wearos_vbmeta.img
.\fastboot.exe reboot recovery
Another try was, to use the boot.img of the current OneOS release, because i've tried the same with the stock rom:
Code:
.\fastboot.exe flash boot .\OneOS-21.10.8_rover\boot.img
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe reboot recovery
Without any luck :/
No change in it's behavior - even between both tries.
i am confused and do not know what to do :/
It feels that everything i try won't work at all
Click to expand...
Click to collapse
@nelikp told me that he was able to use my backup to recover from his bootloop
TicWatch Pro 3 Ultra GPS (Rubyfish) [Complete Stock TWRP Backup]
I heard that many people need the stock backup files for the TWP3 Ultra GPS so here you go! Note, this is the "PMRB.220111.001" base version https://mega.nz/file/1AlCDJ7S#GoX8tWbfkZ7EALwA3gDvX7lOCKPms6oQVogEo5Th32E Enjoy my friends!!
forum.xda-developers.com

I'm in a similar predicament - stuck in a boot loop. I own a TWP3 Ultra LTE and think the reason I have ended up this way is because I've attempted to flash a custom ROM (OneOS-21.10.8_rover.zip) which is only suitable for the TWP3 LTE running build PMRL.210414.002, and is not suitable for the TWP3 Ultra LTE running build PMRL.220111.001.
I also didn't make a backup in TWRP prior to installing the custom ROM, and so I feel your pain Even if I had, I'm not entirely sure it would solve my problems at this point.
I can get TWRP to load, but after a few seconds, the watch restarts, so there's not actually enough time for me to do anything. The only thing that is working ok is fastboot. The watch doesn't restart upon entering fastboot, and I can communicate fine with it (ie issue fastbook commands) via a command window.
I'm not overly optimistic, but perhaps the good folk here might be able to help out and perhaps there is a solution. If someone were to provide me with the stock ROM, and if there is a way to flash that using fastboot rather than TRWP, maybe that would be one way out of this. All thoughts / ideas very warmly welcomed and sorry for the newbie mistake!

I've tried some things again.. even `fastboot oem reboot-recovery`. But this command throws back as non existent, so i am not able to use it. .. but i don't wanna give up. Just nothing positive for now to share. ;-)

Thanks for sharing
On the OneOS Wear site (https://wear.lunawolf.es/en/descargar) there is a PMRB.220111.001 stock ROM available under rubyfish, but no equivalent PMRL.220111.001 stock ROM available under rover. I don't know if they will be releasing one eventually for rover, but I think if we were to get hold of PMRL.220111.001 stock ROM for rover there would at least be some chance.
How quickly are you looking to get back and running? I guess one option is buy a second TWP3 Ultra LTE, make a backup using TWRP, and then use this backup in an attempt to unbrick the first one using fastboot to flash the stock image. Do others think this is likely to work? Obviously requires some outlay £/$ though with no guarantee of success