Related
Hi,
I have a Vodafone (UK) branded Desire Z which today froze whilst I was using it. This left me no option to remove the battery and re-insert it to clear the phone.
Unfortunately the phone will not fully boot now - all I get is the standard HTC screen, followed by the Vodafone logo screen. It then goes black and restarts.
I have tried removing the battery and leaving it for a while before reinserting. I have also removed and replaced the sim and the SD card, but still no joy.
Is there a 'safe mode' way of booting the Desire Z that I could try or has my phone just died?
Any help gratefully received.
http://forum.xda-developers.com/showthread.php?t=842495
Hi again,
Thanks for that link - I have read and re-read as suggested and attempted to follow the instructions but the second link (cwm recovery) is dead - it takes you to a 'removed by mod' post, so I didn't get far!
Just to give a bit further info, I took my device into a local 'fone doctor' shop, where they managed to fix it (or so I thought! - cost me £22 as well! ). The phone was back with the stock HTC Sense on it.
Anyway, within about three hours of the phone working, it froze again - and is now back to being stuck on the White HTC boot screen (rather than the looping it was doing previously). I have a feeling that my phone may just be knackered!
If I do the hold volume and switch on thing, I get the following:-
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
Apr 11 2011,23:36:27
....plus the usual HBOOT, FASTBOOT, RECOVERY options etc.
To confirm, I have NEVER rooted my phone. Up to the point it originally froze it had only had the official over the air updates.
I do have HTC Sync installed on my PC, so all of the required USB drivers should be available.
I also have the Android SDK installed (I have dabbled in development) so have adb.
I have read many posts over the last couple of days, but the majority seem to say that if you have "S-ON" you could well be screwed.
Also, adb does not seem to recognise my phone - I have no idea if I had "enable USB debugging" checked or not - again, if this was not the case then I fear I could be screwed!
If anyone has any further idea's of how I could possibly bring my phone back to life it would be hugely appreciated.............or should I just give up and look to get my old G1 unlocked?!
Many thanks.
ok ...you can´t reach your phone with adb if your are not booted into a rom.
do you have fastboot installed on your pc?
if yes then enter fastboot menu (power & tp) and then type fastboot devices on your pc...
your device should be listed.
then type fastboot oem boot and if you are lucky your phone boots again
EDIT: or push power & volume+ to enter recovery and wipe cache or do a factory reset... and do some researching about emmc chip
Many thanks hoffmas. I managed to run the fastboot commands you mentioned which did indeed force a reboot, but unfortunately only back to the white HTC splash screen.
The output from the commands was:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot devices
XXXXXXXXXXX fastboot
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP001
(bootloader) setting->cid::VODAP001
(bootloader) serial number: XXXXXXXXXXX
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=VODAP001 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=VODA-UK androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BERT06529 androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:66802 msec
FAILED (status read failed (Too many links))
finished. total time: 8.078s
I am guessing that the "FAILED" line at the bottom is another way of saying "Sorry Mate, your phone is knackered!".
I also tried selecting "Recovery" from the menu - that brought up a black screen with the two green arrows around the device picture. This lasted for about 10 seconds, then the phone vibrated about 6 times and went totally blank again - no reboot, no splash screen nothing.
When I try and select the "Factory Reset" option, nothing happens at all. I can move up and down to it using the vol keys, but when I click the power button to select it, nothing happens.
Thanks for all the suggestions anyway - I guess I'll have to get the trusty old G1 unlocked.
I don't think I'll ever tie myself into a two year contract again - bit annoying to be paying for two years when you only get 13months out of the phone!
sry to hear that it didn´t work... but delete the serial number of your phone in your posting.
maybe there is a way to use fastboot for factory reset... but i don´t know how :S
ok... this should be the commands:
fastboot erase userdata
fastboot erase data
fastboot erase cache
Thanks again hoffmas - unfortunately when I run those commands I get this:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Not looking good.
I'm guessing the "FAILED (remote: not allowed)" means pretty much nothing will work.
Thanks again for your help - it is much appreciated.
yes you are right... looks like you need eng hboot to do this
sry, but i have no idea what else you could try... maybe someone else knows better
Update: I'm still a noob, but I learned something new today and you were very helpful. Btw thank you for the rom link for Lineage OS, I was going to search for it after my issue was resolved and now I'm running it. :highfive:
Yeah, I ended up clicking twrp wipe without going into advanced options... (I had no idea what nandroid was before this because I didn't research enough ). With the only back up I have left for my phone being the files that I transferred to my laptop (I dragged every file and copied to a folder basically). So I went into recovery (twrp 3.0.2-2) and tried transferring all my files from my laptop to see if it would work (I'm pretty sure that wasn't a good idea but at the time I kind of wanted hope). Now my fastboot won't register my device on minimal adb (but it can register it when I'm in recovery mode). I reinstalled the usb drivers so that it could connect but again it only connects on recovery not flashboot. In all honestly I have no clue what to do now because I'm pretty sure bootloader is locked in some way so I kind of need a lot of guidance on what I should do now.
So I guess my question is:
What should I do now?
Also is my phone basically a chunk of dead metal now?
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.077s]
finished. total time: 0.077s
Burnedone said:
Yeah, I ended up clicking twrp wipe without going into advanced options... (I had no idea what nandroid was before this because I didn't research enough ). With the only back up I have left for my phone being the files that I transferred to my laptop (I dragged every file and copied to a folder basically). So I went into recovery (twrp 3.0.2-2) and tried transferring all my files from my laptop to see if it would work (I'm pretty sure that wasn't a good idea but at the time I kind of wanted hope). Now my fastboot won't register my device on minimal adb (but it can register it when I'm in recovery mode). I reinstalled the usb drivers so that it could connect but again it only connects on recovery not flashboot. In all honestly I have no clue what to do now because I'm pretty sure bootloader is locked in some way so I kind of need a lot of guidance on what I should do now.
So I guess my question is:
What should I do now?
Also is my phone basically a chunk of dead metal now?
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.077s]
finished. total time: 0.077s
Click to expand...
Click to collapse
You can grab fastboot information, so why don't you simply flash TWRP, boot it up, flash ROM ?
To flash recovery while in fastboot:
Code:
fastboot flash recovery path_to_twrp.img
You can download TWRP here (grab the latest version, which is 3.0.2-2).
Then, simply
Code:
fastboot boot path_to_twrp.img
to boot into your new recovery.
After that, you can
Code:
adb push rom_path.zip
where ROM can be stock ROM (download here) or custom ROM (such as LineageOS for example).
Flash the ROM, and you have a bootable OnePlus 2.
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
https://www.youtube.com/watch?v=njXQYn53SPc
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
AlexAndroid said:
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
Click to expand...
Click to collapse
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
acejavelin said:
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
Click to expand...
Click to collapse
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
AlexAndroid said:
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
Click to expand...
Click to collapse
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
acejavelin said:
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
Click to expand...
Click to collapse
You mean this? (attached image)
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
AlexAndroid said:
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
Click to expand...
Click to collapse
Do you know how to use fastboot and adb? This is from a computer...
acejavelin said:
Do you know how to use fastboot and adb? This is from a computer...
Click to expand...
Click to collapse
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ---
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: 368A71011E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: -----
(bootloader) meid:
(bootloader) date: 12-13-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Feb 5 7:26: 3 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_APAC_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga389d53 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:27:17 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retapac
AlexAndroid said:
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) date: 12-13-2016
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
Click to expand...
Click to collapse
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
acejavelin said:
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
AlexAndroid said:
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
Click to expand...
Click to collapse
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
acejavelin said:
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
Click to expand...
Click to collapse
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
AlexAndroid said:
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
Click to expand...
Click to collapse
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
acejavelin said:
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
Click to expand...
Click to collapse
Do Motorola's official technical services have the necessary firmware?
AlexAndroid said:
Do Motorola's official technical services have the necessary firmware?
Click to expand...
Click to collapse
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
If you are in warranty and u haven't unlocked your boot loader yet you can give silly reason's like i revived updates last night but battery was low and while updating it turned off and now my phone isn't booting up
acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Hello, finally I take the equipment to an official technical service of Motorola, where they told me that they could not repair it since the cell phone did not take Software. Is this possible or would it be that the technical service did not have the necessary software version?
acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Good afternoon, I return the subject after a long time since yesterday I thought to try again, and I found that the cell now turns on, but when trying to complete the initial configuration, after choosing the language gives me to select the wifi networks, where it does not detect any, and I do not enable the jump or forward button, and I'm stuck there again, it's very strange, as soon as I enter that screen, it gives me the option to add a new network, and I can see that says Mac Address with pure zeros, as if it did not have MAC.
If I try to enter the recovery, now I see "No Command" (previously not directly entered), and there is no way to skip this "No Command", I have tried all the methods that appear online.
EDIT: I was able to get into recovery, but I do not know if it can help me now.
Any ideas? he seems to be brigado, but not as much as before
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Edvin73 said:
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Click to expand...
Click to collapse
I still have a problem, when the device is turned on, it always turns on Bootloader mode, and I have to select "Start" to turn it on. This is why when you want to upgrade to Android 7 via OTA, when the device is restarted during installation, it enters Bootloader mode, select "Start", restarts the update, restarts in Bootloader, and remains in an infinite cycle.
Is there a solution to this? I have already activated USB debugging in order to unlock the Bootloader.
Thank you!!
Hi guys, I'm new here and I just wanted to know if someone else have had this issue too and knew how to solve it.
Yesterday I was playing pool on my phone when suddenly it turned off. I though the battery was very low but I had barely charged it. When I was trying to turn it on it didn't respond, I connected the charger and noticed that the only thing that was working was the LED and the screen never turned on again, I realized that it was a hardbrick.
I guess the cause was that a few days ago I changed the kernel, I installed Elemental X kernel, but I didn't like how it was working on my device so I restored the backup with the RR ROM I always use and everything was normal until yesterday.
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
I use a zip file as help through adb commands on my laptop and the Fastboot Flash Mode (Secure) on my device.
I don't know what else to do and the problem is unknown for now.
Would it be the bootloader?
Is there a problem if the OEM is locked?
Is the non-existent IMEI interfering?
Am I doing things right?
What else should I do?
PS: It's obvious that I'm desperate and I know that is possible to save it.
Thanks for reading I hope someone answer.
Caney said:
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
Click to expand...
Click to collapse
That's not good, flashing wrong firmware can be dangerous to losing fingerprint and losing IMEI.
Get latest December's patch ROM from link thred and try to flash it. : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Caney said:
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Click to expand...
Click to collapse
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
stehaworth said:
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
Click to expand...
Click to collapse
stehaworth said:
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
Click to expand...
Click to collapse
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Caney said:
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Click to expand...
Click to collapse
Tbh.... I'm not too sure... But I would start at looking into flashing full Moto stock image via fastboot (see other thread for details)
Hey, I think I have lock my bootloader accidentally :'c When I try to put the commands to flash firmware it throws me this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin'
How do I unlock it?
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
C:\Users\hp>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: b61bc8aa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 57A9A70100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(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) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.291s
@Caney from this data, i can see bootloader version is old, so you can try blank-flash with September's gpt and bootloader.
Follow (link below) thread for it, and where it says about download gpt and Bootloader files, go for September's one (2nd link there)...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
When you get bootloader (after blank-flash), flash December's update.
____Mdd said:
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
Click to expand...
Click to collapse
Why isn't that good?
Caney said:
Why isn't that good?
Click to expand...
Click to collapse
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
____Mdd said:
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
Click to expand...
Click to collapse
Oooh man, can you please attach the link of that gpt here? I don't find it.
Caney said:
Oooh man, can you please attach the link of that gpt here? I don't find it.
Click to expand...
Click to collapse
GPT and bootloader of the September 2017 stock ROM update (NPJS25.93-14-10) - bootloader version B1:06. https://drive.google.com/open?id=0B-GUyOfb8Ogzc25FdW1WUDBMS1U
GPT and bootloader of the December 2017 stock ROM update (NPJS25.93-14-13) - bootloader version B1:07.
https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
However, I would caution against just using these files, and suggest that you update fully by flashing the entire stock September or December 2017 ROM. Your bootloader is from the November/December 2016 firmware (B1:03) so just updating your bootloader isn't a good idea, especially when it comes to OTA updates.
Alternatively, if you want to reflash the stock ROM that has the same bootloader version as your reported bootloader, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Caney said:
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Click to expand...
Click to collapse
Are you following a guide to help you flash?
Generally for any flashing via fastboot (e.g. for stock ROMs or for TWRP)
1)Install the ADB and Motorola drivers as directed by the guide.
1a)Extract the stock ROM zip file (should be about 2 GB in size extracted), copy all the files to your ADB folder (so they're on the same level as your adb.exe and fastboot.exe).
2)Reboot your device to the bootloader (fastboot mode) and connect to your computer via USB. Preferably this should be the same cable as came with your device or another high quality data + power USB cable.
3)Open the ADB terminal on your computer and verify that your device is communicating by typing 'fastboot devices' in the ADB terminal, without quotes. This should return your device's serial number.
4)If so, then proceed with flashing as per the guide's fastboot commands. They are the same as the stock ROMs for Moto G4/Plus devices have followed the same layout (7 sparsechunks for system, for example). If you do not wish to re-lock your bootloader, then do not use the two OEM lock begin or the OEM lock commands. If you wish to try to keep your data, then you can omit fastboot erase userdata. However, with your device in the state it is, it may be worth thinking about a fresh start and erasing your userdata.
For omitting bootloader re-locking and trying to preserve your data (though be aware you may have to wipe anyway, the following fastboot commands should suffice.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
You can either edit a flashing script to mirror these commands and use the script or enter the commands, individually and in order, by copypasting each line into the ADB terminal, then executing. Ideally, you want to see [OKAY] before you proceed. You may see errors about 'Image signed with bad key' if you're actually still unlocked, that's normal.
However, if you see any other errors, such as pre-flash validation or security downgrade, then you will need to use a newer stock ROM. Depending on which blankflash you used, the September 2017 or December 2017 stock ROMs would be suitable candidates.
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
Click to expand...
Click to collapse
After flashing bootloader file from September ROM, your bootloader will be automatiically updated to B1.06 and same apply for December ROM.
But you have used the blank flash file so it is recommended to downloading the June 2017 fastboot ROM and flashing that in fastboot.
Caney said:
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
As of Windows PowerShell of WIndows 10 still it doesn't fully supported for all Commands and Features so Its better to use CMD or ADB.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
Then you may wish to try manually flashing each command individually, and in order, ensuring you see [OKAY] before continuing. The script may proceed too quickly to see if it's all worked, so manually flashing is another option. You could always add 'pause' before 'reboot' in the script (without quotes) to let you review the flash before rebooting.
As for Powershell instead of cmd, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/help/installing-twrp-using-powershell-t3727761/
As for updating bootloaders, I would recommend it - your bootloader is a crucially important piece of firmware and should stay at the same patch level as your system/device firmware. This should reduce the number of complications you may face and also ensure that OTA updates go more smoothly.
Be aware that the B1:06 bootloader in the June 2017 and September 2017 security patches (NPJS25.93-14-8 and NPJS25.93-14-10) close a bootloader vulnerability, which makes downgrading to an older stock ROM even more risky as it appears Motorola does not like you downgrading. Strictly speaking, it's not the act of downgrading, but the act of taking an OTA update whilst downgraded - the mismatch between your newer bootloader patch level and the older stock ROM can hard brick your device should you attempt to install an OTA update.
Furthermore, with the December 2017 stock ROM patch, bootloaders are updated to B1:07, meaning our current latest blankflash is not likely to work (blankflashes older than your current bootloader, corrupted or not, do not appear to be permitted to flash to your bootloader). So be careful when updating and flashing anything to your device if you choose to update to the December 2017 patch.
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