Related
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Sounds like that upgrade definitely went wrong. Since you were upgrading to Kit Kat I'd say flash the No Wipe file from here http://forum.xda-developers.com/showthread.php?t=2735172
Your phone won't allow for CWM or TWRP recoveries since it's a build past MDK. Also if you want prior to using that Odin file go to play store and get the app " Samsung phone info" and run that app and take a screen shot of the bootloader section. Actually do that before hand anyways. I'll link you to it
Sent from my SCH-I545 using Tapatalk
---------- Post added at 06:39 AM ---------- Previous post was at 06:39 AM ----------
Here
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SCH-I545 using Tapatalk
hopefully people will learn by this NEVER take any update while traveling, too much can and will go wrong.............
Yea I think people have to much faith in Verizon. There not setup to handle anything but a perfect download and install when it comes to their OTAs. They're best done on WiFi at home
Sent from my SCH-I545 using Tapatalk
Reply
BeefJerkyAddict said:
Hello, everyone! I'm in search of a hero who can help me resolve this (frustrating) issue! I'm sure you have heard it before: my phone will not boot fully; it is instead stuck permanently on the white VERIZON logo screen.
Model: SCH-I545
Carrier: VERIZON
Color: BLACK
Size: 16GB
The phone has not been rooted.
It does not have USB debugging enabled.
I have not installed any custom recovery software or mods.
There is no external SD card installed.
First, some back story. My phone asked me to perform a software update roughly a week ago. About a minute into the update, it told me the update failed. I assume this occurred because I was on the train and passed through a tunnel. Afterwards, my phone began acting up, rebooting itself randomly, and applications(such as web browser, text messaging) would randomly crash on me. I assumed another update would come to resolve the issue, but unfortunately yesterday(Sunday), my phone again rebooted itself, only this time it would not make it past the white VERIZON screen.
My goal is simply to recover my files from the device before either returning it or performing a factory reset. I have scoured the internet for hours trying to find a way to achieve this. I can boot my device into the stock recovery console and into ODIN download mode. I have tried clearing my phone's cache in recovery mode, which did not help. I have tried booting into safe mode by repeatedly tapping the menu screen, but it did not help.
I have ADB installed and a USB driver from Samsung and a USB driver from Google. I can get my phone to appear using ADB in sideload mode only while in the recovery console. Unfortunately, this is of limited use because apparently it can only be used to install software packages, and the phone seemingly rejects all attempts to install packages such as CWM and TWRK, which I had hoped would allow me to use the ADB pull command.
I have tried installing these mods using ODIN as well. Again, failure due to security apparently. :crying:
If anyone has any idea how I can retrieve the files from my phone, you'll be my hero forever!
Click to expand...
Click to collapse
Hi BeefJerkyAddict,
I would reccomend to do a total full wipe with Odin, this usually solves all of your problems. All of your stuff should be clear for restoring once you do that. But after you do the full wipe, immediately go to settings and then software update because your phone will be on android 4.3 and not 4.4.2.
Here is the link with the instructions as well:
http://forum.xda-developers.com/showthread.php?t=2578209
You're welcome.
Yea I guess I'm just biased to updating straight to kit kat lol if the op has the chance to stay on mk2 he might as well. And I suggested no wipe first just so not to lose data. Up to the op though
Sent from my SCH-I545 using Tapatalk
Hi guys,
Just posting to say THANK YOU for the help. After a long download, I got ahold of the VRUFNC5 No-Wipe file and successfully installed it using ODIN3 v3.09 without a hitch! All of my pictures, videos, text messages, are all right where they were, and my operating system is upgraded.
Thank you so much for taking the time to point me in the right direction. I had nearly given up!
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
You are using an unofficial build of CM, install an official build of CM12
Fhronk said:
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
Click to expand...
Click to collapse
Is your device boots and works well on stock?
nhmanas said:
Is your device boots and works well on stock?
Click to expand...
Click to collapse
My device couldn't even boot in the end. However I solved the problem by changing battery, so it wasn't a software problem. Thank you anyway!
I flashed LCA43 with adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip and everything wents very well.
Now I am in tests and tomorrow I leave a feed-back of the new version.
Thanks.
I download Bits Watch Face from Play Store and I am testing with the new Android Wear LCA43.
For first impression Bits Watch Face is awsome, I like it, very cool.
What was your flash-process?
Unlocked/locked Bootloader? Stock Firmware?
My adb sideload command always breaks things at 61% with an "Installation Aborted" (Error 7) when it is verifying the Image.
Thanks for your help
My flash process is adb sideload eefea3292b364b67db746dc4131713605b8e8f76.signed-platina-LCA43-from-LDZ22D.eefea329.zip
Previously I am in pure stock with locked bootloader, and I flash the new LCA43 with windows 10.
When I flashed it stops two or three minutes in 61% than I continues to 100% without any breaks.
I think you must wait at 61% until process continues.
Try flashing it with another usb port for example.
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
I have tried, flashing stock and sideloading, no dice, reflashing stock and locking bootloader then sideloading, again no dice, unlocking flashong stock once more relocking and trying ota, nothing flashes when ota tries to flash the lint gets to 15-25% theb flips to the dead Android for around 30-60 seconds before rebooting.
i tried multiple cables, pcs and operating systems (win7-10 linux Ubuntu and debian) and multiple downloads from seperate sources, nothing seems to want to give me this update..
Any help would be appreciated
freshlysqueezed said:
FYI
The old technique of forcing an ota update still works for a stock watch: Make sure you have the latest android wear app.
1. Reset the watch from settings
2. On the phone, erase the data from the android wear app.
3. Connect the watch to the app
After the watch syncs, it will ask if you want to update.
Click to expand...
Click to collapse
Thank you,it works
I have the new Android Wear 1.3 flashed at 28 hours ago and for now i am loving the new faces, and i like the battery optimization, in my case it consumes only 0.89% battery in one hour.
I have the screen off and micro off with an application.
LG G Watch have a new stable upgrade in my opinion.
Hi. What do you mean by micro off ?
Do you also keep fit off ?
Sent from my LG-D852 using XDA Free mobile app
ruben46_ said:
Thank you,it works
Click to expand...
Click to collapse
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Visegrad said:
Tried this twice, stock with bootloader locked and both times it comes up with the dead android and reboots. Not sure what's wrong.
Sent from my Hitchhikers Guide to the Galaxy
Click to expand...
Click to collapse
Did for me right now too. Maybe try to boot into recovery mode and flash it via ADB sideload.
For the user that ask me I mute the mic with an apk "mute wear mic" that I download, I think that is free.
I upgrade my to 1.3 with adb sideload command and it work at the first shoot.
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
steso90 said:
I have also ended up with the dead android and tried both sideloading and the regular installing from watch. Tried with restoring the watch to stock and locked the bootloader but I am still ending up with a dead Android image then reboot..
Click to expand...
Click to collapse
Yeah, it's weird. It's like I've lost recovery. I have flashed back to stock, locked the bootloader and try to go to recovery, dead android. unlocked bootloader, try to go to recovery from bootloader... dead android. I have used the restore tool to push recovery image on, everything says it went fine, try any method to get to recovery...dead android. I was able to flash the Mysterious Magic rom back on via his script with no issues, so not sure where the disconnect is, but for now I will stick with the rom since the battery life is great with that.
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
JanusDC said:
I've tried everything with no luck, LCA43 doesn't want to be installed on my watch.
I got the OTA, but when I press install it start installing until more or less the middle of the progress bar and then I get a dead android. I downloaded the OTA to do a sideload but it gets aborted at 61%. I formatted all the partitions and flashed the official images of LDZ22D, then tried both methods, with the same result.
Does anyone have the link to the official img? Because the OTA doesn't seem to work for me.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
EpicLPer said:
It's not "aborted" at 61% (or does it say Aborted?), only takes a long freaking time till it hits 100% from then on. Just wait 5 minutes or so once you see 61% on your CMD window.
Also I posted the update in a separate thread here, I think under General.
Click to expand...
Click to collapse
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Is there any way to make the ota flashable through twrp?
hugoprh said:
If I boot into recovery, I get the dead android, and ADB can't see my device when this happens, so I can't sideload your update file, so I tried installing TWRP recovery and installing that file from there, but it fails straight away from TWRP.
How did you get ADB to see you device when you have the dead android showing?
Thank you =)
Click to expand...
Click to collapse
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
EpicLPer said:
Boot into bootloader, select recovery there, once the screen turns to the LG logo instantly swipe from left upper to right lower corner as fast and often as you can, after a few seconds you should see a menu on the stock recovery screen. Then select the adb sideload option and send it from your PC via "adb sideload zipnamegoeshere.zip"
Click to expand...
Click to collapse
No luck, tried it, booted into the bootloader, selected recovery and once the screen turned to the LG logo, I swipe from left upper to right lower corner as fast and often as I could, went again into the dead android screen and ADB still unable to see the device.
Isn't the swipe from upper left to lower right, to boot into the bootloader? I can do that, but whilst booting into recovery, from the bootloader, it just goes to the dead android.
Also tried to do a factory reset to the watch, cleared the data of the Android App on the phone, connected the watch and update fails when the progress bar is at about 20%
if any one could get their hands into the full ROM file, that would be awesome.
Any other ideas are welcome =)
And thank you for your help