I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.
bmurphr1 said:
I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.
Click to expand...
Click to collapse
1. forgot to remove dm-verity
2. There is a specific guide to return stock rom and undo warning menu, but it has flashing stock recovery b15 with jasminetool and install update.zp b17
stock recovery
stock rom
edit.
this is what appears if I am right?
juniorgerman said:
this is what appears if I am right?
Click to expand...
Click to collapse
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.
bmurphr1 said:
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.
Click to expand...
Click to collapse
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk
juniorgerman said:
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk
Click to expand...
Click to collapse
That makes more sense to me than just not including it in the guide. When my EDL cable comes in, I should be able to force the tablet into EDL mode and use jasminetool to return the tablet to the stock recovery image I backed up, and then use fastboot to push the original firmware on to the device or re-install TWRP and attempt to flash a working custom ROM. That makes me feel better about not knowing about the no-verity situation. I've seen the video of someone using a piece of copper and plugging the tablet into their computer and removing it about 5 seconds after plugged in, which forces the tablet into EDL mode just like a physical EDL cable does, and use jasminetool to restore the stock recovery. I will probably do it in Linux this next time around since you need to do some rather wonky things in Windows 10 to run jasminetool and zadig, including booting Win10 into Test Mode to remove driver signature reinforcement.
Related
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.
I have a old phone that had been stuck at this state for a while,
`orange state, your device has been unlocked and can't be trusted. Your device will boot in 5 seconds`
Should I follow this guide to un-brick it?
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
mrchow19910319 said:
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
Click to expand...
Click to collapse
What should I do? You need to read, the answers to your questions are here a million times over. Always do your homework first. Also thank someone who helps you. Otherwise they will not continue helping you.
FlashOne: Why are you using FlashOne? You are not bricked. Also FYI, if using FlashOne , you have to be in EDL mode. not fastboot.
Now here is probably good news, since you can enter fastboot then you are very likely just fine,and you are definitely not bricked. However, you will probably end up losing any files that you had on the phone, because the user data( storage ) will most likely need to be formatted, (type yes reboot to recovery)
So my instructions are to help get your phone working again, not to recover data. Unfortunately, you didn't provide much information so I have to assume some things.
Is the bootloader unlocked?
Have you flashed custom roms before?
Which phone do you have? A Leeco X5?? A Leeco X6??
Let guess and say that maybe bootloader is unlocked, you are asking a question on XDA so maybe that is a safe guess?
What you need to do is use ADB or the the Tool all in One and flash Recovery and root. Here comes the reading part again, I can't explain everything or I will be here all day. I assume that you know how what Recovery and root is?
Download the correct TWRP Recovery for your device, if you don't know your way around ADB too well.
You can use Mauronofrio's "TOOL ALL IN ONE" for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
Read that thread for instructions or for any questions.
If your device not recognized it is a usb driver issue, ensure that device drivers are installed and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date. The All in One tool can do all of this for you, its with the advanced menu section. ** You will need to temporarily disable Windows defender for installation. **
Use the All in One tool to flash Recovery, then boot to recovery.
Ensure that you have TWRP installed permanently by rebooting to Recovery and then rooting the phone.
Always reboot to Recovery and check the boxes to install TWRP when rebooting to recovery
To remove encryption you will always need to format the storage
Not wipe >> Choose Format > type yes> Reboot to Recovery)**
(If you see a message that says there is no OS installed are you sure> Click Yes, then reboot to Recovery, ignore message about no OS)
When you reboot to recovery swipe to be able to read and write to the device.
Use an OTG Usb adapter to connect a USB to your phone and flash your prefered rom, Gapps, and root. Reboot to recovery, thenn reboot to system. If you were successful, the error message will be gone and you will be able to set up the phone.
As mentioned the tool will help you with installing your rom, Gapps, and root.
The All in One Tool can completely restore your phone to stock if absolutely needed. It actually links to Mauronofrio's server and it has all of the significant EUI Stock Roms, in case you want to restore the stock rom.
Hopefully this helps you, Good luck.
tsongming said:
.
Click to expand...
Click to collapse
thank you so much for the in depth explanation.
sorry for the super delayed reply.
I will try to follow the instruction and will update here soon.
again thank you.
I have the same problem with umidigi bison, I tried to root with the mtkroot tool v2.5.8, the process ended correctly but when I turned on it showed orange, the problem is that I cannot enter with any combination of keys, it does not recognize adb, please help
*Details on situation provided first. Skip to last paragraph for question.*
I'm starting to get back into the Android game after being away for some time and successfully rooted my 8 Pro on Android 10. About a week later, I got the notification to upgrade to Android 11 and found there was a way to upgrade while retaining root. Awesome!
While walking through the process, I missed a step and only used Magisk Manager to install to the "inactive slot". When the rest of the process finished and I was up on Android 11, I couldn't get root; it would only say N/A. I worked on it for a while and, eventually, managed to somehow fully brick my phone to the point it would only boot to Fastboot. Normal start ended in Qualcomm Crashdump Mode (QCM), booting to recovery would put me in Fastboot and if I tried to 'Fastboot boot recovery recovery.img' with the oem recovery extracted using Payload Dumper, it would also end up in QCM. I tried for a few hours to get into EDL Mode but never could get it to work. I would only ever end up in Fastboot or QCM.
I resigned to contacting OnePlus and started the process to have my phone sent in yesterday, but knew I had time to mess with it some more before getting the shipping labels and such. While working on it for a few hours last night and getting no where, I had a revelation. the 8 Pro has A/B Parititioning! Using Fastboot, I was able to switch my phone to Partition B and reboot. After 30 agonizing seconds, the boot screen finally showed and it eventually spit me out at the setup screen. Success!
Finally for my actual question. I know my Partition A is still borked, so I'm tempted to boot into EDL Mode (which I think I can finally do using ADB) and reflash everything but I'm curious. Will reflashing in EDL Mode on affect Partition B since that's what I'm currently on, or will it do both A and B? I'm okay with reflashing both and starting all the way over if necessary but if I can specifically only reflash Partition A , that would be preferable. I did a quick search but couldn't find any info on this.
Keeping this up and posting the answer as I've been able to determine it through additional research/trial and error.
From what I can tell, flashing via EDL Mode resets both slots and flashes the factory firmware back to Slot A. So even if you've wrecked it as bad as I did, you can change to Slot B via Fastboot, get booted into Android, use ADB to get into EDL and reflash with the MSM Tool.
PassingInTime said:
Using Fastboot, I was able to switch my phone to Partition B and reboot.
Click to expand...
Click to collapse
Hello!
How did you do it with locked bootloader. Please, write step by step instruction.
Sorry. You had unlocked bootloader...
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself