Related
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
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
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
Hello guys,
I need help. Definitely
My phone stopped booting into system after some service.
First a little brief:
Phone never showed any problems before.
LCD+Touch were replaced.
Phone stopped booting into system.
Stills boots/ works perfectly in fastboot, recovery and userdebug.
Tried:
factory reset
unlocking and relocking bootloader
flashing several factory and stock RAWs
stock recovery and TWRP
stock raw alone
update stock system from stock raw
twrp + stock rom + magisk
twrp + lineageos + magisk
several guides on this forum
Nothing works. Problem remains the same, doesn’t matter the alternative I try.
Now the whole story:
I’ve had this phone for a while. Always did the OTA updates. Never had problems… at all.
Some days ago, I dropped it and was finally able to break the screen. The lcd became black in some spots and had different brightness in others. Touch kind of worked, kind of got crazy after some seconds (and I had to turn the screen off and on again).
I’ve got some experience in repairing electronics and phones. So, I watched/read a dozen guides about this particular service, bought an original LCD+Touch kit, and replaced myself.
No apparent problems with that. The process is quite simple and straight forward. (I knew what I was doing. But if you tell me something might be wrong with that, I will look into it. I will take any help. Just tell me what to do.)
And so it begins.
I set my phone up again - without gluing anything, as it was the first test – and turn it on. It seems to boot normally… boot logo shows normally… boot animation seems to take longer than usual… the screen suddenly goes black.
I open the whole thing again, check every connector, everything is ok.
I try to turn it on again, now the phone turns off after just one or two seconds of boot animation.
I did then a factory reset, problem persisted just the same.
I thought to myself: “ok, then. System must be somehow corrupted.”
I updated the system to the lasted version in ASUS website trough adb sideload. Problem persisted.
“ok, maybe I must clear the system partition then… let’s go a little further”.
I read some guides, and proceeded to unlock the bootloader (flash factory raw, fastboot commands, flash oreo raw), flash TWRP and LineageOS.
When I turn it on again, a bit of hope. Boot animation takes, again, a long time. An “encrypting device” screen comes up and I believe it’s finally over. But no. The phone goes off after about 10 seconds of supposed encrypting and, when I turn it on again, same as before… two seconds of boot animation and then darkness.
After that I Just went deeper into the habbit hole.
Tried several brick fixes in sent by the XDA community.
Tried flashing RAWs using Asus Flash Tool (v1.0.0.86 (20201124)) and flashall_AFT.cmd (that comes inside de RAWs.
Tried all combination and orders I could imagine of the following RAWs:
CSC_ZE552KL_13.1301.1603.53_WW_Lock_20171128
CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug
WW_ZE552KL_13.20.10.137_M3.10.35_Phone-user.raw
WW_ZE552KL_14.2020.1703.28_M3.10.47.3_Phone-user.raw
WW_ZE552KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw
WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
It doesn’t matter. Whenever I flash a RAW, the phone goes to this encrypting process and then goes black. From there on, I can flash anything through adb sideload, fastboot or twrp…. It shows the boot logo, (possibly shows the dm-verity screen, depending on the set up), and goes off after about 2 seconds of boot animation.
Tested everything I could with TWRP: LCD, Touch, mounting partitions and storage seem to be working fine.
Tested everything I could with the factory RAW userdebug (using command fastboot oem enable-userdebug boots a very simple system (there’s an image below)): Again, LCD and touch work fine. Also, hard keys, wifi, Bluetooth, calling, messaging, 4G and both speakers are working.
And there we get to present time. I just don’t know what else I can do.
My next steps would be going into QFIL flashing. That would actually be new to me. But since I can use all these functions properly, it doesn’t seem to me that that’s the way to go.
Please help. I will take anything. Tell what I may have passed by. Send me the guides you think may help me, even if I’ve already tried.
I can give you any information you guys believe is pertinent.
I will start leaving here some info I think may help:
ZE552KL Z012DC ASUS_Z012DC Brazilian model BRAZIL
4GB RAM. 64GB storage.
Code:
C:\Users\Vanisi\Desktop\ZE552KL>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4236000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:O-CS4 - 4 - user
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd683f7000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf0000000
(bootloader) cpuid:046
(bootloader) project:ZE552KL
(bootloader) serialno:H2AZB601E85****
(bootloader) kernel:lk
(bootloader) product:MSM8953
all:
Finished. Total time: 0.281s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Device is_authorized: false
(bootloader) ssn_num: H2AZB601E85****
(bootloader) isn_num: MB352KL0AB****
(bootloader) check_fused: 0
(bootloader) Device resize: false
(bootloader) BOOT_COUNT : 175
(bootloader) SB=Y
(bootloader) Re-partition: false
(bootloader) Device had been rooted: >>> YES <<< (Warranty void)
(bootloader) Device has copy fsg to fsgCA: false
(bootloader) Device last copy fsg status: fail
(bootloader) verity_mode: 1
(bootloader) is_ffu: false
(bootloader) verity_counter: 0
(bootloader) total verity_counter: 0
OKAY [ 0.203s]
Finished. Total time: 0.203s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem system-info
(bootloader) board_info: msm8953
(bootloader) mem_info: 4GB
(bootloader) mmc_info:
(bootloader) product_name: ASUS_Z012D
(bootloader) product_locale: en-US
(bootloader) product_carrier: US-ASUS_Z012D-WW_Phone
(bootloader) csc_build_version: WW_ZE552KL-13.20.10.152-20161222
(bootloader) bt_mac: 2C4D5****B18
(bootloader) wifi_mac: 2C4D5****E38
(bootloader) imei: 35905207393****
(bootloader) imei2: 35905207393****
(bootloader) ssn: H2AZB601E85****
(bootloader) isn: MB352KL0A****
(bootloader) color: 1B
(bootloader) country: BR
(bootloader) customer: CKD
(bootloader) revenuecountry: BR
OKAY [ 0.188s]
Finished. Total time: 0.188s
(the **** don't actually come up... it's just to hide the information I believe may be sensitive)
Help. Please
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