Hello,
after a failed attempt at rooting my Ticwatch I am now stuck in a bootloop. Is there any way to get into recovery or the bootloader without using adb?
(I tried pushing the button after the vibration, holding it down for ~30 secs. and swiping basically in any direction possible) I cant use adb or fastboot because my computer wont detect the device and im only getting to the Ticwatch logo in the boot sequence. Can I have any hope for fixing this or do I have permanently bricked this thing?
Any help is appreciated!
Nilsit said:
Hello,
after a failed attempt at rooting my Ticwatch I am now stuck in a bootloop. Is there any way to get into recovery or the bootloader without using adb?
(I tried pushing the button after the vibration, holding it down for ~30 secs. and swiping basically in any direction possible) I cant use adb or fastboot because my computer wont detect the device and im only getting to the Ticwatch logo in the boot sequence. Can I have any hope for fixing this or do I have permanently bricked this thing?
Any help is appreciated!
Click to expand...
Click to collapse
I didn't attempt rooting yet, I only unlocked the bootloader.
I noticed that while booting, I was able to execute adb commands (using the charging cable for connection), including rebooting commands.
Aren't you able of doing that?
What recovery did you use, by the way?
EDIT: ew, I just noticed you mentioned your PC not detecting the smartwatch. Maybe try changing PC, since it's strange actually.
Nilsit said:
Hello,
after a failed attempt at rooting my Ticwatch I am now stuck in a bootloop. Is there any way to get into recovery or the bootloader without using adb?
(I tried pushing the button after the vibration, holding it down for ~30 secs. and swiping basically in any direction possible) I cant use adb or fastboot because my computer wont detect the device and im only getting to the Ticwatch logo in the boot sequence. Can I have any hope for fixing this or do I have permanently bricked this thing?
Any help is appreciated!
Click to expand...
Click to collapse
Is this still relevant? Or did you manage to revive it already? Because I may be able to help here but you'll have to give me a few hours to get some dumps off of the watch which you can flash back via the MediaTek Flash Tool.
EpicLPer said:
Is this still relevant? Or did you manage to revive it already? Because I may be able to help here but you'll have to give me a few hours to get some dumps off of the watch which you can flash back via the MediaTek Flash Tool.
Click to expand...
Click to collapse
No, its not relevant anymore. After not getting any answers for half a month I tried my luck with the Mobvoi support. They somehow approved my warranty request and I sent the watch back to them. Now I´m waiting for my replacement. But thanks for your help anyways, if I ever try it again and also mess up again I will contact you
Nilsit said:
No, its not relevant anymore. After not getting any answers for half a month I tried my luck with the Mobvoi support. They somehow approved my warranty request and I sent the watch back to them. Now I´m waiting for my replacement. But thanks for your help anyways, if I ever try it again and also mess up again I will contact you
Click to expand...
Click to collapse
Oh boy you'll have a fun time waiting then... Mobvoi support is one of the ****tiest so far sadly, according to stories on Facebook people sent in their watches for repair a few months ago and haven't heard anything back yet.
But yeah, flashing back the partitions via the flash tool would've been tricky too anyways since we don't have the things Mobvoi used when making the watch
EpicLPer said:
Oh boy you'll have a fun time waiting then... Mobvoi support is one of the ****tiest so far sadly, according to stories on Facebook people sent in their watches for repair a few months ago and haven't heard anything back yet.
But yeah, flashing back the partitions via the flash tool would've been tricky too anyways since we don't have the things Mobvoi used when making the watch
Click to expand...
Click to collapse
Funny Story: First I requested a repair wich was declined. I sent them a video of the bootloop and they still asked for more information and seemed to have no idea what a bootloop is. Then I sent them a warranty request with exactly the information provided in the other request and it got approved instantly. :laugh:
I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?
For clarity, you were running a OP6 rom on the 6T?
Krunk_Kracker said:
For clarity, you were running a OP6 rom on the 6T?
Click to expand...
Click to collapse
XxX made a 6/6T rom.
The rom was made for the 6 and 6T. It flashed and booted with no problems. Multiple reboots no issues. Wasn't until the software update installed itself I had issues
Does a computer recognize it at all, even with any weird key combinations?
skinzy98 said:
Does a computer recognize it at all, even with any weird key combinations?
Click to expand...
Click to collapse
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
I had pretty much the exact same issue Saturday, and I was t even rooted or unlocked bootloader so I know how you feel
There's an option to turn off automatic updates, for future reference.
blue5055 said:
I was able to root my 6T with no problem. Was even able to run the XXX No Limits OnePlus 6 rom with no issues. However overnight the pending software update installed itself. When I tried to reboot the phone got the screen that says "your device is corrupt". Went and tried to flash the official stock OOS rom and now its hard bricked. Phone won't even power on. Is there anyway to fix it, or am I just F'ed in the A?
Click to expand...
Click to collapse
Have you tried to flash the fastboot Rom in the xda thread?
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
blue5055 said:
After messing with it some more was finally able to get it to boot. Had to hold down power+volume up for like 3 minutes. Now that I am able to get in fastboot going to try this: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Using the tool above I was able to unbrick and return to stock. For anyone else bricked, that tool will help you
Everything I've been reading says that the OP7T Pro Mclaren and The OP7T Pro share the exact same software from OP, but when you flash the Mclaren phone it knows to unlock the Mclaren features/themes. This means you can flash the Mclaren edition phones with the software already available from OP.
The question is can you flash the Mclaren 5G from T-Mobile with this same Global version and get the same results. I know this was true for the OP7 Pro on T-Mobile, but this is a different version of the Mclaren than the International one.
I would assume the main issue would be the 5G radio and maybe all the radios for that matter, but is anyone out there with a Sim Unlocked (do not need to be bootloader unlocked) T-Mobile OP7T Pro Mclaren 5G willing to try flashing the Global software?
As I've mentioned before, there's no way to recover this phone from a bad flash or hard brick. Even just flashing the system partition would be insanely risky and probably lead to a loss of 5G, at least in the GUI.
LLStarks said:
As I've mentioned before, there's no way to recover this phone from a bad flash or hard brick. Even just flashing the system partition would be insanely risky and probably lead to a loss of 5G, at least in the GUI.
Click to expand...
Click to collapse
I completely understand that there is no T-mobile software to fall back on in case of disaster. What i'm wondering about is the OnePlus side of things. Are they going to have to release a separate Mclaren 5G stock/global system or will we be able to use the 7T Pro global version? If we need to wait for a stand-alone Mclaren 5G OnePlus stock system we might be waiting a long time.
Assuming there's a way to flash back I'd test it out. I don't use 5g at all I have it disabled right now so losing that functionality is not a big issue for me.
I've flashed my T-Mobile 6t and OnePlus 7 Pro before so now I impatiently await a solution for .y McLaren edition.
Can't wait for this to be tried out. I don't need or use 5g so I'd be willing to give it up to ditch the tmobile software.
Wondering the same. I don't mind losing 5G, would love to get updates straight from OP instead of waiting months for Tmobile to get their act together.
Yep, T-Mobile is slower than molasses ???
You guys will break your device. It will not boot, and there will be things broken that can't be fixed as of right now. No amount of fastboot restoring will do the trick. I mean you can fastboot restore and it will boot but things will remain broken even after a restore.
DanDroidOS said:
You guys will break your device. It will not boot, and there will be things broken that can't be fixed as of right now. No amount of fastboot restoring will do the trick. I mean you can fastboot restore and it will boot but things will remain broken even after a restore.
Click to expand...
Click to collapse
The ota done did it for me today for hours on end. Qualcomm ****. Only had work laptop Fastboot not working because i guess i turned off file transfer a few days ago. Then all a sudden it did. Had to download that flash.zip package thats floating around here somewhere. Did that. Didnt work. Recovery>erase all
Didnt work
Over and over. Manually in folder: flash boot boot_b boot_b.img
As well as a
Didnt work
Reversed it
Didnt work
A to a and b and vice versa
Didnt work
Did it the first way again and all a sudden im back on.
Fashcat said:
The ota done did it for me today for hours on end. Qualcomm ****. Only had work laptop Fastboot not working because i guess i turned off file transfer a few days ago. Then all a sudden it did. Had to download that flash.zip package thats floating around here somewhere. Did that. Didnt work. Recovery>erase all
Didnt work
Over and over. Manually in folder: flash boot boot_b boot_b.img
As well as a
Didnt work
Reversed it
Didnt work
A to a and b and vice versa
Didnt work
Did it the first way again and all a sudden im back on.
Click to expand...
Click to collapse
Well, I'm gonna give it another shot then
DanDroidOS said:
Well, I'm gonna give it another shot then
Click to expand...
Click to collapse
Im getting this in my update. Still not sure what happened. Backed up everything and followed directions to the T on dealing with magisk
But this is what i was seeing earlier and at one point i think it downloaded but didnt install but i reboot to check if it would after the fact but crash dump instead. Oof
Hala bir gelişme varmı bu konuda
Bu konuda bir gelişme var mı?
Any progress on this?
oneplus 7t pro 5g mclaren T-mobile automatically answer incoming calls plz help me.
It all started when I decided to de-google my phone and use Lineage OS. I jumped down the rabbit hole and managed to unlock my bootloader by submitting request to OnePlus and waiting for the email with the unlock_code.bin file, then using that to unlock. I am working on Linux Mint with adb and fastboot installed. I can get to bootloader screen on the phone and I can send commands to it but I'm not sure what to do next. I attempted to boot the latest TWRP.img and it appears to work but then I get a QUALCOMM Dump Mode error.
This is a great phone and I hope I've not ruined it so I will wait patiently to see if anyone can bail me out. Meanwhile I'm using this crappy LG K7 to get me by for now. Thanks for your time if you read this post.
I think you need to start by converting it to an international 6t. Been a long time since I did mine but this should be the right place to start
T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)
In the previous thread, we discussed a method to convert T-Mobile 6T's to the international variant, sort of, but it required an unlocked bootloader, which itself requires a SIM unlock which T-Mobile gives people a hard time about. However, it...
forum.xda-developers.com
ce_lloyd said:
It all started when I decided to de-google my phone and use Lineage OS. I jumped down the rabbit hole and managed to unlock my bootloader by submitting request to OnePlus and waiting for the email with the unlock_code.bin file, then using that to unlock. I am working on Linux Mint with adb and fastboot installed. I can get to bootloader screen on the phone and I can send commands to it but I'm not sure what to do next. I attempted to boot the latest TWRP.img and it appears to work but then I get a QUALCOMM Dump Mode error.
This is a great phone and I hope I've not ruined it so I will wait patiently to see if anyone can bail me out. Meanwhile I'm using this crappy LG K7 to get me by for now. Thanks for your time if you read this post.
Click to expand...
Click to collapse
Almost all twrp versions will crash dump while trying to boot on Android 11. Use this one it will boot for you
Cats_PJs said:
I think you need to start by converting it to an international 6t. Been a long time since I did mine but this should be the right place to start
T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)
In the previous thread, we discussed a method to convert T-Mobile 6T's to the international variant, sort of, but it required an unlocked bootloader, which itself requires a SIM unlock which T-Mobile gives people a hard time about. However, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. I will give that a try. I am currently unable to get the phone to show up in device manager for some reason. I'm using a windows 10 laptop. Unable to get the laptop and phone to interface.
Brettroth said:
Almost all twrp versions will crash dump while trying to boot on Android 11. Use this one it will boot for you
Click to expand...
Click to collapse
I cannot get my laptop and my phone to talk. Won't even show up under "Other Devices" ?? I can get into FastBoot Mode on my phone but not sure what to try now.
Did you open the MSM tool? Connect your phone after the tool is open with it powered off. Then hold down all the buttons. Might take a couple tries to get it right. It doesn't need to be in fastboot to connect. I believe the screen stays black. Good luck
Cats_PJs said:
Did you open the MSM tool? Connect your phone after the tool is open with it powered off. Then hold down all the buttons. Might take a couple tries to get it right. It doesn't need to be in fastboot to connect. I believe the screen stays black. Good luck
Click to expand...
Click to collapse
I finally got it to work! I'm on OS 9.0.13 and need to get to Android version 11 for the lineage OS. I dL'd and attempted to install Android 11 and it failed. Am I not able to jump versions like that?
You
ce_lloyd said:
I finally got it to work! I'm on OS 9.0.13 and need to get to Android version 11 for the lineage OS. I dL'd and attempted to install Android 11 and it failed. Am I not able to jump versions like that?
Click to expand...
Click to collapse
You need to update to 10 then 11. Install the Oxygen Updater app. It will choose the correct version to install.
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
xtcislove said:
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
Click to expand...
Click to collapse
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
nkhater said:
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
Click to expand...
Click to collapse
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
daviddosa said:
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
Click to expand...
Click to collapse
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
xtcislove said:
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
Click to expand...
Click to collapse
Yes fail-safe a/b partition, and Yes I have tried several cables
nkhater said:
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
Yes fail-safe a/b partition, and Yes I have tried several cables
Click to expand...
Click to collapse
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
daviddosa said:
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
Click to expand...
Click to collapse
did that too, leaving it overnight did not work either.
I hope this will be an eye-opener for other flashaholics, things are different in A12
my phone has the same problem, have you fixed it, i need help
[email protected] said:
my phone has the same problem, have you fixed it, i need help
Click to expand...
Click to collapse
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
nkhater said:
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
Click to expand...
Click to collapse
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
ProtoDeVNan0 said:
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Mar 3rd I posted for the 1st time about it.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
djcrystals said:
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Click to expand...
Click to collapse
That's so fed'ed up man, I am in the same boat as you, total loss, I am done with OnePlus, they can enjoy Oppo and ColorOS, A12 sucks and it's not for me.
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Andre Cancian said:
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Click to expand...
Click to collapse
how much did you pay for the motherboard?
nkhater said:
how much did you pay for the motherboard?
Click to expand...
Click to collapse
I paid something like 250 USD for a working 8 Pro with a broken screen. Motherboards on their own were available for a similar price on sites like aliexpress, but the wait was too much.
nkhater said:
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Click to expand...
Click to collapse
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do
you need to replace the motherboard, the phone is completely dead, it's gone