Related
Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.
Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...
Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.
I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.
Hi,
Something strange happened with my phone yesterday and I think it is worth sharing.
The Problem: I have an old USB JIG I made by myself about one year ago for using it with the Samsung Galaxy S (GT-I9000), it works like a charm for entering into download mode. But when I bought the SGS2 (GT-I9100) I noticed it didn't work, so I searched the forum and read that the new bootloader prevents it from working and erasing flash count or removing the infamous yellow triangle.
I know this have been addressed by other means. But yesterday my phone started acting weird and it turned out to be a problem in the phone's USB port making some sort of short circuit (Explanation in this thread, I'm not the only one: http://forum.xda-developers.com/showthread.php?t=1216163).
The funny part is that, when the phone was not working well, I had to remove the battery because it was unusable. And when I put the battery back, withouth touching any button, the phone started on download mode with a legend saying that the flash count has been erased, I rebooted the phone and the yellow triangle was gone also!
The point of my post is that something in the USB port made the phone think it had some kind of JIG connected which told it to erase the flash count and start the download mode. So I've come to think that there has to be another version of the USB JIG that works with out phone in the latest bootloader version!
I'm not very good with electronics, so I cannot investigate any further, but I leave my doubt in the community just in case someone wants to do some more research.
Hint: When this happened, the phone kept showing the car home icon in the status bar as if it was connected to some kind of dock
I hope this helps!
What rom were you and and did you flash the old bootloader at any time since you were using your phone?
yeah the old jig only took my phone to down mode thts it,but yes defo the fun i had is sparking the pins like wires + an _....lolyes i think ur right ,thers gota b an otha verson
bpivk said:
What rom were you and and did you flash the old bootloader at any time since you were using your phone?
Click to expand...
Click to collapse
I9100UHK1 - Latest 2.3.4 unbranded for my country, the old JIG we all know doesn't work and no, I've never flashed the old bootloader, I was staring to become friends with the yellow triangle until it faded away
Flash the old bootloader, use the jig, flash the new bootloader again if you need to. Simple.
However, I recall seeing posts on here in November/December about a new USB jig that worked with the new bootloader. Don't know how that ended up or whether anyone had gotten hold of one of these (if they exist).
Edit to add - I've just sent the person I was discussing this 'new jig' with a couple of months ago a message to see if these things exist or not. I'll post here when I know either way.
MistahBungle said:
Flash the old bootloader, use the jig, flash the new bootloader again if you need to. Simple.
However, I recall seeing posts on here in November/December about a new USB jig that worked with the new bootloader. Don't know how that ended up or whether anyone had gotten hold of one of these (if they exist).
Edit to add - I've just sent the person I was discussing this 'new jig' with a couple of months ago a message to see if these things exist or not. I'll post here when I know either way.
Click to expand...
Click to collapse
I know that flashing the old bootloader works, but the point of the thread is precisely that there must be another version of the JIG because the phone reseted the flash counter by itself because of the USB port problem, even though it has the new bootloader
using same firmware some time ago when i bought my phone, i try to use usb jig with the new bootloader, but never happened what you said to me, i have to flash the oldbootloader, but if you're not the only one, that,s strange
I think noone understands. He managed to see the factory mode screen and erase the counter while having the new bootloaders (without a JIG, maybe shortcircuit). Can we suppose that a different JIG can activate this with the new bootloaders?
Edit: Sorry, MistahBungle seems to get it
tsinc said:
I think noone understands. He managed to see the factory mode screen and erase the counter while having the new bootloaders (without a JIG, maybe shortcircuit). Can we suppose that a different JIG can activate this with the new bootloaders?
Edit: Sorry, MistahBungle seems to get it
Click to expand...
Click to collapse
Exactly! maybe I didn't manage to give a good explanation.
By the way, I've seen that screen three different times while the problem on the phone existed, so It's not just a concidence, there HAS to be a new JIG version, we just need to figure out. I'm guessing that we need to short circuit some cable with resistors like the original JIG, maybe a different resistance is needed?
New JIG
I remember over-reading a conversation between Odia ( I think) and someone regarding a resistance-switching JIG that can erase it, but I never caught what exactly was required.
If we can find out I'd like to make one, I might have a play with some rheostats later and see if I can figure it out.
May also have something to do with the order things are done as well. The OP inserted the battery at the time the reset occurred. Maybe switching off alone is not enough but a new jig needs installing with the battery out, then the battery replaced.
Sent from my GT-I9100 using Tapatalk
alias_neo said:
I remember over-reading a conversation between Odia ( I think) and someone regarding a resistance-switching JIG that can erase it, but I never caught what exactly was required.
If we can find out I'd like to make one, I might have a play with some rheostats later and see if I can figure it out.
Click to expand...
Click to collapse
That conversation will help you.
pulser_g2 said:
That conversation will help you.
Click to expand...
Click to collapse
Basically this is what I remember when a firmware is being flashed the USB cable should have the same resistance on the same pin as the jig now.
Sent from my GT-I9100
OK. Allegedly (and I can't emphasise this enough), this works with the 'new' bootloader on the SGS2. Yes, I realise the description/title says I9000, I'm just relaying what I was told by someone else (who hasn't bought/tried one of these BTW).
I guess it's a case of who in this thread can't be arsed flashing the old bootloader or using Triangle Away & wants to fork out 2.5 quid to test it out.
pulser_g2 said:
That conversation will help you.
Click to expand...
Click to collapse
It was Chainfire and Odia in CF's TriangleAway thread, but neither of them actually mentioned what it was, just at hint at it.
Anyone care to share?
MistahBungle said:
OK. Allegedly (and I can't emphasise this enough), this works with the 'new' bootloader on the SGS2. Yes, I realise the description/title says I9000, I'm just relaying what I was told by someone else (who hasn't bought/tried one of these BTW).
I guess it's a case of who in this thread can't be arsed flashing the old bootloader or using Triangle Away & wants to fork out 2.5 quid to test it out.
Click to expand...
Click to collapse
I have one of those cables and can confirm, it does NOT work on the new boot loader.
Thanks That rules that bit of kit out then.
mrm1 said:
I have one of those cables and can confirm, it does NOT work on the new boot loader.
Click to expand...
Click to collapse
I suppose by using mobile odin to flash we'll never need a jig again?
Sent from my GT-I9100 using xda premium
rwc3b said:
I suppose by using mobile odin to flash we'll never need a jig again?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I guess with chainfires hot fix you would not need mobile odin or jig ... if sammy keeps as they are in there future releases of ICS
Just to clear things up
The original JIG does not work on the latest bootloader. My state is that there may be a new version of the JIG which may work based on what I've found.
I know there are many methods like flashing the old bootloader, using Triangle Away, or flashing by mobile odin, I just opened this thread in order to share something I have found by mistake on my phone and maybe useful for others.
When I first made the JIG for the original SGS was because the device had download mode disabled and the only way to access it was by calling 'adb reboot download'. But then a flashing procedure failed and all that could save the brick was the JIG. I know this is not the case with the SGS2 but I thought it may be interesting to share and investigate
Hi Everyone, noob here.
I cant remember the exact procedure that i took, but i rooted my phone, and used x-restore to load floyo onto my x8, i did not really like it and wanted to try a newer version of cyanogenmod -7.1 and i had to flash custom Kernel on.. anyway - i tried flash tool and it said restart your phone and under app settings check the box for allow unrecognized or unsupported files or something like that - sorry i don't recall what it was exactly.. this is my first time doing this. it failed again, so disconnected my phone and just restored floyo and decided i was going to be happy with it.. i had tried to use the plugin to unlock the bootloader after testing it to make sure it could be done.. as the forum said.. and all looked good. but i forgot to close flashtools when i was done trying.. i restored floyo and and then made the mistake of plugging the phone in while flashtool was still on and looking for the phone.. the next thing i see a message pop up saying bootloader unlocked successfully or something similar.. restarting phone.. then my phone restarted and it did something else.. i waited for it to Finnish and then my phone went off..
Now it wont come on at all, no LED, nothing.. The phone is one week old.. i fully charged the battery last night so its not the batter i have Hard Bricked it.. and im freaking out..
I am a computer tech that has never failed to fix any computer problem and have repaired thousands.. i have experience in electrical work and have built tonnes of gadgets like small amps etc... but when it comes to this.. i am a complete Noob and i accept that.. ive screwed up and all i can do is ask for help..
i read through tonnes of forums but none seem to match my case so i thought it ok to ask for help.
What can i do, other than own a $300 paper weight.
Just restore with SEUS or PC companion and install something good like Semc Debrand Engine
I'm sorry to tell u that
u have to go to SEMC to repair it
unless u unbricked it by PCC or SESU
as if u want to fix it u'll pay 100$ or above to fix it
Hey man,
im sorry for what happened to your phone.
http://forum.xda-developers.com/showthread.php?p=12442257#post12442257
have you tried to use that guide? i also bricked my X8, the guide helped me very good and now my x8 runs on Android 2.3.7
Chris95X8 said:
Just restore with SEUS or PC companion and install something good like Semc Debrand Engine
Click to expand...
Click to collapse
Thanks, but how do i do that when it is not even coming on ??
shallondb said:
Now it wont come on at all, no LED, nothing.. The phone is one week old.. i fully charged the battery last night so its not the batter i have Hard Bricked it.. and im freaking out.. I saved months to get that thing here in Zimbabwe.. i paid $300 for it here which is sadly the going price..
Click to expand...
Click to collapse
The symptom you describe there is a HARD BRICK. No LED, no display, no vibration, no nothing means it's DEAD - HARD BRICKED.
There's nothing you can do yourself other than to send it to Sony Ericsson for repair.
Since you said "Zimbabwe" I doubt you have repair shops with the required equipment and technicians to try a JTAG restore.
So I'd say your only option left is to send it off to SE - and once you get it back you better don't mess around with it if the $300 you mentioned means US Dollar (insane price).
EDIT: And the mistake you made ... you somehow made Flashtool to unlock your boot loader on a device that's most likely past a manufacturing date of 11W29. This kills the phone and you simply can't repair it yourself anymore ... see the Hard brick warning - read before boot loader unlock sticky in the X8 General board. There are several posts clearly telling you that everyone who managed to hard brick the phone sent it off to SE as there's simply no "fix it yourself" method available.
Hey guys, i cant do any of those suggestions because my phone is not coming on at all ... is there anything else i can do ? anyone ?
shallondb said:
Hey guys, i cant do any of those suggestions because my phone is not coming on at all ... is there anything else i can do ? anyone ?
Click to expand...
Click to collapse
B.Jay said:
There's nothing you can do yourself other than to send it to Sony Ericsson for repair.
Click to expand...
Click to collapse
Feel free not to believe me, but the is NO other way left anymore.
B.Jay said:
Feel free not to believe me, but the is NO other way left anymore.
Click to expand...
Click to collapse
Thanks B.Jay
Sorry my last post was delayed, i was still sending it when you reply came through. I do believe you. i am going to attempt taking it back to the small shop that sold it to me and see what they recommend..
Hello xdadevelopers.. I recently tried unlocking the bootloader on second X8 phone.. I successfully managed to unlock it.. but I've accidentally removed the battery after it boot up.. I'm not getting any sign of life or such.. I tried powering up normally, no results, tried booting up the flashmode, green LED doesn't appear, tried to connect it on my USB cable, no response, tried charging it with normal cable (No USB cable).. no results.. :/
Is there any way to unbrick it without sending it to SE service? Please help..
P.S. It's date is 11W44 (I managed to unlock my bootloader below 11W44 I think, will check my phone for release date)
No. Not really. You need to send it to sony. There are a lot of warnings here regarding unlocking bootloaders of devices 11w29 and up.
So that means the hardware is damaged after unlocking the loader? And I'm not sure if SE service still has options to repair X8 since it's old phone and it's production has stopped.. :/
NCC-34051-E said:
So that means the hardware is damaged after unlocking the loader? And I'm not sure if SE service still has options to repair X8 since it's old phone and it's production has stopped.. :/
Click to expand...
Click to collapse
Not 100% sure, but i don't think it's the hardware in as much as it's not really "damaged." based on what i've read from members that had sony reppair their devices, it seems that the motherboard is replaced. But those who know claim that jtag can fix it.
Edit: try to search around for people who are knowledgeable on jtag and maybe they can fix it.
Yeah.. I've read about jtag and riff box moments ago.. It seems the flash memory is corrupted.. unable to reflash it again.. Since it was my friend's phone (I borrowed him my so I can try to update his phone to cyanogen mod), I've successfully lost my phone, oh well.. I might buy better one in the future I hope.. Thanks for the help!
NCC-34051-E said:
Yeah.. I've read about jtag and riff box moments ago.. It seems the flash memory is corrupted.. unable to reflash it again.. Since it was my friend's phone (I borrowed him my so I can try to update his phone to cyanogen mod), I've successfully lost my phone, oh well.. I might buy better one in the future I hope.. Thanks for the help!
Click to expand...
Click to collapse
Good luck. Hope it gets fixed.
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: