Hi everybody, today I unlocked the bootloader of my TicWatch E, and I want to root it.
(just for your info, you can unlock bootloader of the watch by connecting it to your PC using the magnetic charging cable and using the usual "fastboot oem unlock")
Problem is, I don't find a TWRP version for TicWatch 2, E or S, which share the same hardware. Can you help me?
We're currently working on one, stay tuned. As soon as we have a user-friendly and working version we'll post it
So far the Ticwatch always overwrites the recovery with it's stock one when you reboot the watch, there is a workaround but it'll only work one time. You could root it but we want something consistent.
That's wonderful, thanks for the answer!
What link?
Any updates on this?
Related
Hello! I've got a Mexican Moto X Force XT1580 (64 gb version). I've got a big problem.
After I unlock the bootloader , installing custom recovery TWRP and root my device....my Micro USB connecter broke. Not charging , I can't connect to computer. So...I charge it using a wireless charger. The problem is...I got software updates.
I need a method to...do something. Because the screen with software update just appear 50 times a day. If I download it...and try to flash , go to TWRP recovery. And I don't know if I can flash the update from there , I tried to see where is downloaded and try to flash manually, but I can't figure out.
And if I download it...and then I reboot because I can't flash from custom recovery...it just restarting..so I have to factory reset.
Please , can someone help me? I need a method to download and install stock recovery without using USB. Or to install update...manually ..without using a PC....Or to stop that message ''software update'' that just pop-up on my face everytime.
Or...another change...to flash a new rom....but I don't see any rom for this phone..like Ressurection/CM..I don't know.
Any help , please?
Kinzie LOS 14.1 ROM
Hello,
supposing your TRWP is still alive.
I am running this LOS 14.1 Rom on my XT1581 64GB in Germany
https://forum.xda-developers.com/devdb/project/?id=18860#downloads
Thread about:
https://forum.xda-developers.com/droid-turbo-2/development/rom-cyanogenmod-14-1-kinzie-t3536148
Hope this may help you
Ok, so a couple months ago, my phone sensors died and after a long time of procrastinating, I decided to try to fix it, I've managed to do it and I'm sharing the fix with you guys, as I didn't found any fix online.
So first, why this happens?
It's because of the phone's persist, that can be corrupted, this can happen if you flash roms, or even with updates, like it was in my case.
How to fix it?
Ok, so first you will need a few things.
Adb and Fastboot
persist.img file (and a couple more files for the flash to work, but I will place a link here)
Xiaomi Miflash (this version will install the drivers, but if don't, uninstall and boot Windows with Driver Signature Enforcement disabled and install it again)
Download All here - it's already modded to flash persist only. It will not wipe your data.
After installing Xiaomi Miflash, you will need to boot the phone in edl mode. You can do this even with you bootloader locked and it will work. To do this, first boot in Fastboot mode (Vol down + Power), plug the USB cable on phone and computer, then open cmd on the folder of fastboot and use the command:
fastboot oem edl
After that, your phone's screen will turn off and the led will keep blinking red.
Now, open Xiaomi Miflash.
Click on Select
Select the folder that you downloaded earlier.
Click refresh, your phone should appear on the list, if don't, reinstall drivers.
Now click flash.
The flashing is quick, and now your phone is fixed.
Any doubts, free feel to ask!
Tested on Redmi Note 4 Global Snapdragon Version
Known errors:
cannot receive hello packet,MiFlash is trying to reset status! - You will need to reflash stock ROM.
thanks a ton
you made my day
ayazuddinkhan said:
thanks a ton
you made my day
Click to expand...
Click to collapse
You're welcome. please let me know if it works for you.
worked, everything is fixed
Hello sir im facing same problem on Redmi 4x 32gb and can u use this fix file on my Redmi 4x thank you
Thank you so much buddy.
it fixed my problem.
Great guide ?.
How can I port it to the Mi A1, actually the phone doesn't even boot if there's something wrong with the persist.img. Really need your help.
Can i use for mtk version?
My phone camera laggy, video play laggy, and acceloremeter not working... @FalconMaster
Please help me! I did the flash, it worked correctly! but now you're saying that you have your account and my device is locked! 170 ****** mi account number. there it is reporting that it is linked to your account. please contact me at PM, and help me.
This method is not working for redmi 4x
Please give me persist.img file for redmi 4x for locked device. I tried your given method but it's not working in my device it show file and device does not match
..
sorry for my bad English
Different phones
For everyone with different phones, you need to get to Mi website, download the fastboot ROM for your phone and flash the persist only. This can be done by removing all lines from the xml file, except the one that flashes the persist. After that, flash it normally as in this guide.
Redmi note 5a prime
Hi, is this working on note 5a prime?, When I bought it the only problem is when I use camera, causing some lag, need to open and close again. Also when video recording.
Hello. For the first time I write on this forum and I want first of all to thank all of you for sharing your work and knowledge.
I would like to know if I can follow this procedure having already installed the pixel experience rom and the mido 8.2.1 firmware.
Thanks in advance and forgive my bad english.
Aaa
Please help me. I cant boot into edl wih Mi Note 3.
Aa
I cant boot into EDL. So, can i flash it with fastboot. Please help me. Im using mi note 3
Man, I don't really know how that worked for you. Your script erases persist and flashes rpm.mbn to persist, that file isn't even present images folder.
then open cmd on the folder of fastboot...... which folder do u mean ?
i used "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" it detects the device but the phone's screen doesn't turn off and the led isn't blinking red, it stay at the LOGO FASTBOOT ....
i tried to flash it with XiaoMiFlash.. it detects the phone but it errors out...
i have Redmi Note 4 Global Snapdragon Version
Does this method work on custom roms?
Im on Los 15.1 and my gps doesnt work. Will this fix it?
fixed my problem on redmi note 4x
Thank you so much FalconMaster.
it fixed my problem on redmi note 4x (mido).
Thank Thank you very much.
Great guide :good:
So I read everything. Will this method work for my MI 9 global version ? After unlocking the bootloader, I flashed de Android Q beta from the official web page, using MiFlash(I think that's the correct name). So I didn't like the Beta one and downloaded the global stable version, flashed with MiFlash. Everything was perfect, but my Accelerometer and Gyroscope won't work. What do you suggest? Thanks a lot!
Hey guys,
there are some SM-T230NW available via ebay. They come from BMW 7 series cars with their feature called "Touch Command".
I bought one of those off ebay and thought I might be able to remove the BMW-branded OS, set a neutral boot screen and use it as a normal tablet.
My problem is, I cannot flash a new recovery via odin (security check fail), and I do not know how to root such a device.
Can anyone help me with that?
Edit: I forgot one thing: It has knox enabled.
Woud you still have you BMW touch tablet?
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
next time try to get more comercial, vastly sold, phone. choosing Qualcomm helps a lot
metafaniel said:
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
Click to expand...
Click to collapse
Hi, how did you change the updater script file? I have an Y6 MYA-L11 phone but i'm not able to skip model error message (I tried to change all "SCL-L02" with "hwmya_L6737" in the updater script file but it didn't work).
Another question, did you finally find a working rom?
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.