Database Users

Oneplus 2 Bricked, Help!

Hi!, I have a bricked Oneplus 2 so heres how it happened
My device was running oxygen os 3.0 with TWRP 3.0 and I decided to flash the resurrection remix ROM on my phone through twrp, and when I did flash it I think it gave me some error code, and then I rebooted my phone and now its stuck in a bootloop with no OS installed.
I tried going to TWRP and adb was not working and adb side load was not working, I went to fastboot and my computer wont detect my device through fastboot. I tried first aid kit and my phone was not being detected. I did try this with using 2 other computers running windows 10 and I tried it with a computer running Linux Mint. How ever when I check in Device Manager It shows "communications port (COM1) I tried updating that driver with the Oneplus 2 Qualcom drivers and it gave me a error code 10 and I tried installing an ADB interface driver to that to and I got the same error code 10. I also tried this method below with no luck.
"https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/"
Please help me and the community facing this problem, Thanks!

I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini

SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution

SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
And does your phone get recognized by fast boot? because you were saying that you used first aid to get recovery, and first aid uses fastboot, because you will beable to fix your phone through fastboot

yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom

SirMika said:
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
Click to expand...
Click to collapse
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot

fahad999 said:
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
Click to expand...
Click to collapse
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.

SirMika said:
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
Click to expand...
Click to collapse
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot

fahad999 said:
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
Click to expand...
Click to collapse
not sure but i did similar procedure yesterday. see second post http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 but i had no idea what i suppose to do..all i had was stock recovery..
in adb, running command fastboot device it shows my phone

Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
it seems there is no way to fix it..my skills and knoledge aint high, but i´v done all by the book and nothing. it also goes in fastboot and twrp but thats it. i wish i could help you but were in a same boat

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Danm, that sucks. Later I may try using a virtual machine of Linux Mint on my computer and see if it will detect my phone in fastboot. And the sad thing is that this oneplus 2 is my only phone

Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10

fahad999 said:
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
Click to expand...
Click to collapse
I think i need to get in my hands PC with Win7. i also came that conclusion the problem is Windows.
Oneplus drivers (/D) just keep pop-upping asking what todo, when selected nothing happens
EDIT: is it possible install proper softwares via USBstorage?

Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files

Getsuga Tenshou said:
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Click to expand...
Click to collapse
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg

fahad999 said:
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
Click to expand...
Click to collapse
Update! I know why our phones are bricked! when we installed custom roms you wiped the phone right. I was reading that there was a new feature in android in which you wipe the phone with a password, the bootloader gets locked. So I believe that our devices now have a locked bootloader

fahad999 said:
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
Click to expand...
Click to collapse
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)

Guihardrock said:
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Click to expand...
Click to collapse
Sorry to say that this is not working for me and I have no OS installed, I formatted data in twrp and typed yes and still I got no luck. My device is not being recognized by pc in twrp, I installed many drivers (Oneplus Drivers, Google USB Drivers, 15 Sec ADB & Fastboot Drivers, Universal ADB Drivers) Still I got no luck, and nothing shows up in device manager, I tried this in 2 Computers awwell.

i have unlocked bootloader, latest TWRP but no OS. instead zip fils it should be image. adb cant find phone but fast boot does

Bootloop

Hey gents,
Received my unit today which has the dreaded boot loop,
I can get onto a screen with my usb a cable mentioning something about an os.
Windows finds it (xp) i have got some drivers from modaco root zip which is and and fast boot.
Tried both drivers ,
Mad catz is found but can't use any commands get failed when i try following the root procedure.
I tried pressing the buttons to get into recovery as well but I just have a black screen no writing at all and the blue led doesn't load up.
Window cannot find the driver and has usb default but the drivers i used earlier won't work.
Any help ?

Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.

Managed to get cmd to send files to the mojo but my screen doesn't change

K-Project said:
Can you get into TWRP recovery following the guides? You should have no problem once installed. Try this guide here if no OS is installed.
I had bootloop before and managed to recover easily but I used Linux. It looks like a similar method all told though.
Click to expand...
Click to collapse
I have fast boot now but no adb

All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.

K-Project said:
All I can say to my friend is you will have to read thoroughly the guides around here. Have you read this one thoroughly? It says you must remove the USB cable when it says booting OS. This is typically the thing that catches many out. You need to make sure all your files are in place on the SD card once you get to recovery. In all honesty it has been a while since I did this but I used Linux and can flash one of these in seconds. If you're getting the "booting OS" message then the machine is NOT BRICKED and is recoverable.
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
From here in bold:
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
You are using this method to install TWRP recovery, which will then allow you to install your choice of OS. Read, read, read everything you can. I know how it is because I spent a whole long weekend at this over last Easter. It's a drag at first but great once you figure it out.
Click to expand...
Click to collapse
Done exactly what you wrote and i just get this boot loop again

Right currently installing android tv whoop
Followed the Russian site 4pda they have a good write up
Basically i just had two commands
So downloaded openrecovery and then fastbooted to open recovery .

Android TV launcher stayed in boot loop but cm 12.1 is working great

Excellent! Glad you got it going. Yes it's effectively two commands really, but you have to have everything in place.
You're getting a bootloop on Android TV, but my understanding is that will disappear once you flash the SuperSu zip. But if you're good with CM 12.1 I'd stick with that. I never tried Android TV since CM 12.1 did everything I need.
Have you flashed your GApps? I'd go for the nano set.

Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it

sutty86 said:
Yes i flashed gapps but fancied trying android TV again basically you don't flash root when asked i don't think you can root android TV without bricking.
I have a different launcher on it now by chain fire halauncher and kodi running.
I've yet to put emulators on it.
Controller is not the best for android TV to be fair constantly switching modes....
Quick question can the controller pair to a smartphone without the dongle.
As I've tried holding start down for five seconds it goes purple than flashes blue and red but my phone can't find it
Click to expand...
Click to collapse
I'm sure someone round here said you could but it wasn't worth it as performance wasn't so good. The retail one doesn't need a dongle fwiw, and connects to the phone just fine.
Yeah, with CM 12.1 I've managed to minimise mode switching on the pad as it is as you say a bit of a pain. I only switch to mouse mode when using Google Play or shutting down the system. Other than that I occasionally swipe apps away by double tapping the Home button, and that needs mouse mode. Otherwise all emulator, game and KODI use is via the pad mode.

[Recovery]Official TWRP for TicWatch Pro

​Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Catfish
Source Device Tree: Device Tree For Building TWRP

reserved

Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.

What's the command to install this?
Sent from my BLA-L29 using Tapatalk

tfpiaoyang said:
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!BEFGBQKI!uetGnJxWqvG-JRmQNPeBvw
btw any qq grp to communicate?

MicrosoftBug said:
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery ***.img

restore to chinese version cant OTA, will get a big red "!" in recovery...

I have been out of the custom recovery world too long and never tried on a watch before. Trying to flash twrp on my new TW Pro (H) so I can flash janjans rom. Have ADB and drivers (windows 7), have twrp.img ready.
cmd prompt not recognizing adb command. Cant remember how to proceed...how to open fasboot, unlock bootloader.
I know im missing something simple but stuck. Can anyone help jumpstart me?
Update: Got twrp installed after flailing about for awhile. Bottom line, operator error.

This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!

haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
Did you try running fastboot from bootloader? Also maybe try sideload the rom from twrp, that worked for me.

haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/

Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks. I've tried three different chargers (though I'm not sure if the other two that I bought are actually capable of transmitting data) and three different computers. I ordered a new charger that says it is able to transmit data, so hopefully when that arrives it will work. Makes no sense to me that I can get into bootloader and twrp and yet not see the watch in device manager.

Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!

haplohaplo said:
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
Click to expand...
Click to collapse
You deleted the OS? What do you mean by that? Is the watch still working on its own?
Sounds to me like a faulty connector, I would send it back if it is still under warranty.

I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.

haplohaplo said:
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
Click to expand...
Click to collapse
Try 1. Flash boot.img via fastboot
2. Reboot and connect, check via adb if it's detected
3. Install via sideload ROM
(adb sideload file.zip)

This issue was that I couldn't connect with fastboot at all. That being said, it turns out the problem was with the watch itself. Mobvoi, replaced the watch with a brand new one free of charge so it's all good now.

Any chance you have, or know of, a TWRP for the TicWatch E2/S2 ?
Would be much appreciated.

Hey, is it possible to connect a SD card or usb flash drive to the watch via otg when booted into twrp to create a full backup?

Hello, what would I need to do in order to port this to the TicWatch Pro 2020? The hardware is almost identical, except it has more RAM, the codename is catfish_ext. I have an unlocked bootloader and tried to boot this recovery, but I get FAILED (remote: 'dtb not found').
EDIT: Nevermind, I have found that the recovery for the 4G EU verison also works with mine. Here is the link to a working image: https://drive.google.com/file/d/1XNejRoLecLeadEj1CAW_zrTUP5bkUJZ8/view?usp=sharing
And here is the original source: https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013

Hisense 4K ATV4 Rooting

The Hisense 4K ATV4 runs Android 9 Pie. I got into Developer Options and enabled ADB. Unfortunately, the bootoader isn't unlockable, but I think that you might be able to root it using KingoRoot, or even install apps from ADB.
Specs:
Storage: 4 GB
RAM: 1 GB
Processor: ARM Cortex A55

Same problem, my tv is not unlockable. It goes all black when i run "adb reboot bootloader", I can not find OEM
Unlock option under Developer Options!

jerrydevis said:
Same problem, my tv is not unlockable. It goes all black when i run "adb reboot bootloader", I can not find OEM
Unlock option under Developer Options!
Click to expand...
Click to collapse
if you use mtkclient does it unlock?

$cronos_ said:
if you use mtkclient does it unlock?
Click to expand...
Click to collapse
Nope,I can not boot into fastboot mode! It only restarts the TV!

U can unlock it, my Hisense 43A6H is unlocked. After u get a usb male to male type a cable hook it up only 1 port communicates with the tv on my tv. Find out which one it is and it may require a reboot of the tv to get communication via adb initially then adb reboot bootloader then it reboots go to device manager install the bootloader interface driver for the device that shows up. Then run fastboot flashing unlock. That's as far as I have gotten, so do a fastboot reboot.
That's as far as I have gotten, I haven't been able to root it. I have the boot.img and i patched it with a lot of magisk versions and flashed to fastboot flash boot_b boot.img as fastboot flash boot boot.img & fastboot flash boot_a boot.img both basically brick the tv.
Before u continue call up Hisense and get your firmware and to recover rename the file from
usb_9612us_no_tvcertificate_user.pkg
to
usb_9612us_no_tvcertificate.pkg
Place the file only in the root of the fat32 flash drive unplug the tv and plug in the flash drive into ideally the port that communicates with the pc and hold power on the remote and plug in the tv... It will begin to recover the Hisense tv.

chris1892006 said:
U can unlock it, my Hisense 43A6H is unlocked. After u get a usb male to male type a cable hook it up only 1 port communicates with the tv on my tv. Find out which one it is and it may require a reboot of the tv to get communication via adb initially then adb reboot bootloader then it reboots go to device manager install the bootloader interface driver for the device that shows up. Then run fastboot flashing unlock. That's as far as I have gotten, so do a fastboot reboot.
That's as far as I have gotten, I haven't been able to root it. I have the boot.img and i patched it with a lot of magisk versions and flashed to fastboot flash boot_b boot.img as fastboot flash boot boot.img & fastboot flash boot_a boot.img both basically brick the tv.
Before u continue call up Hisense and get your firmware and to recover rename the file from
usb_9612us_no_tvcertificate_user.pkg
to
usb_9612us_no_tvcertificate.pkg
Place the file only in the root of the fat32 flash drive unplug the tv and plug in the flash drive into ideally the port that communicates with the pc and hold power on the remote and plug in the tv... It will begin to recover the Hisense tv.
Click to expand...
Click to collapse
I've tried 7-8 times running "adb reboot bootloader" with different ports, It goes all black and in PC's device manager, there's nothing!
if you want root privileges you can try connecting to shell via UART, I've heard that you'll be directly provided with root privileges on some hisense tv!

@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!

chris1892006 said:
@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!
Click to expand...
Click to collapse
Thnx for amazing guidance & necessary files, I'll try it and let you know very very soon!

chris1892006 said:
@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!
Click to expand...
Click to collapse
Any way to get through this?
Edit: Done Successfully after restarting TV.

Great job buddy so did u unlock it?

Yes, I did

Great job. Hopefully @theydream has time to help us all out. Good luck all! theydream determined I & possibly we have A/B partition scheme i think is the right terminology. So I tried this command but no dice. I patched my boot.img with almost all magisk & even a modded magisk and all no dice.
fastboot flash boot_b boot.img
Click to expand...
Click to collapse

Hisense U8G Bootloader Unlock (and probably others)

Hello. I have managed to unlock the Hisense U8G bootloader in the stupidest of ways. This will likely also work on the U6G, U7G, and U9G (Android TV models ONLY) since they run the same firmware. This will probably also work on every other Hisense Android TV.
So... tl;dr just run "fastboot flashing unlock" and that's it. No need to enable OEM Unlocking in Developer settings or anything since there is no FRP.
You will need:
A computer with adb and fastboot installed
Mediatek drivers if running Windows
udev rules if running Linux (available here: https://github.com/bkerler/mtkclient/tree/main/Setup/Linux)
Step-by-step on a stock TV OS (YOUR DATA WILL BE ERASED):
Enable Developer Settings by clicking on build number 7 times, standard stuff
Enable USB Debugging (this will also enable network debugging, but you will not need it)
That's all you need to do on the TV itself, settings-wise.
On the PC:
adb devices
On the TV:
Allow USB Debugging
On the PC:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
That's it. Your bootloader is now unlocked.
I am currently trying to figure out a way to dump boot.img and vbmeta.img and/or get into BROM mode so I can use mtkclient to dump boot.img and vbmeta.img. Help would be appreciated.

Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".

jerrydevis said:
Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".
Click to expand...
Click to collapse
Thats normal, need a usb type a male to male plugged into 1 of the ports of your tv only 1 port gets detected and other not so ask me for the adb bootloader interface driver for the tv and ill provide, I have a Hisense 43A6H its a MEDIATEK MT9612 SoC which I unlocked the bootloader and cannot root it as I have all the drivers and boot.img and I patched it and typed command and on my tv and likely yours is the same command in slot B but it didn't root the tv...... Anyone know of an alternative method to patch and flash the boot.img? Mtkclient gui might work with python but idk haven't tried yet... Make sure to get the latest firmware from hisense so u can recover if u do something wrong or want to relock the bootloader.
To recover take your .pkg file which for me is update_no_tvcertificate_user.pkg and rename to update_no_tvcertificate.pkg and have only that file on your fat32 flash drive and unplug the tv plug in the flash drive and hold power button on remote pointing at tv and plug in the tv and it'll start recovering and u can let go of the power button.
Code:
fastboot flash boot_b boot.img

Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.

I've been having a hard time rooting the tv. Nothing takes, may someone help?

chris1892006 said:
Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.
Click to expand...
Click to collapse
I would be thrilled if I could just get my Hisense to default to HDMI1 input upon startup, like you can with other SmartTVs.

Have a 65H6510G with a failed eMMC. Service port UART shows CPU trying to setup eMMC to retrieve data, fails and repeats. I can replace eMMC but need to flash in signed boot code. Any ideas?