Firestick Gen 2 Stuck In Update Boot Loop - Fire TV Q&A, Help & Troubleshooting

Hey, I have an Amazon Firestick, I believe that it is generation 2 because of the model number on the back of the device. I have an issue with my device. When I plug it in it says that it is installing the latest software then it will proceed to say that it was unsuccessful and reboot. Into the most annoying loop ever. If you guys have any ideas PLZ let me know I have been looking to fixing it for a while now and I would love for my kids to stop bugging me!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jlopezisthebest said:
any ideas PLZ let me know I have been looking to fixing it for a while now
Click to expand...
Click to collapse
The unbrick for the second generation stick is here.

I'll give it a try and let you know. Thanks for the response!!

Sus_i said:
The unbrick for the second generation stick is here.
Click to expand...
Click to collapse
Hey, I know its been a couple of days, I just wanted to let you know that the process/ exploit did not work. I'm not quite sure what I did wrong.
I updated everything in ubuntu
I downloaded the zip
Extracted using WinRAR
Opened the file in Ubuntu
Ran the ./bootrom-setup.sh in ubuntu
Shorted the stick using a piece of conductive wire
Then waited for the terminal to do its thing, but nothing happened.
Please let me know if I did anything wrong or anything that can help my situation.
EDIT: Couldn't find lsusb btw that might have been the issue, not sure where to find that or run it
Juan

Jlopezisthebest said:
Hey, I know its been a couple of days, I just wanted to let you know that the process/ exploit did not work. I'm not quite sure what I did wrong.
I updated everything in ubuntu
I downloaded the zip
Extracted using WinRAR
Opened the file in Ubuntu
Ran the ./bootrom-setup.sh in ubuntu
Shorted the stick using a piece of conductive wire
Then waited for the terminal to do its thing, but nothing happened.
Please let me know if I did anything wrong or anything that can help my situation.
EDIT: Couldn't find lsusb btw that might have been the issue, not sure where to find that or run it
Juan
Click to expand...
Click to collapse
Idk if you did something wrong, except the winrar thing.
Ubuntu is fine, but you need to run all commands from the unlock/unbrick OP up to the disable modemmanager thing.
Download and unzip the amonet.zip (to the desktop) with ubuntu (don't use windows for this, all file permissions get lost).
Browse in the extracted folder and open a terminal in there.
Then run this
Code:
sudo su
./bootrom-step.sh
Now you need to short the CLK resistor to ground.
Don't use sharp steel tools, best is a fine soft flexible copper wire...
Keep the short (steady and proper, until the script tells you to remove the short), then connect the usb cable...
It should take up to 10 seconds to find the stick and do the handshake.
If nothing happens within 15 seconds, the short wasn't that proper, in this case unplug the stick and retry again.
But it's possible too, that you've got one of the newer patched sticks!?
How old is your stick?
You can take a look into lsusb,
the first boot stage is the bootrom, it prints something about 'phone' (this should pop up in lsusb while shorted),
next stage is the preloader (if you see this, the short wasn't steady/proper).
Good luck^^
Edit: PS, to run lsusb command, you need to open a second terminal window...

Sus_i said:
Idk if you did something wrong, except the winrar thing.
Ubuntu is fine, but you need to run all commands from the unlock/unbrick OP up to the disable modemmanager thing.
Download and unzip the amonet.zip (to the desktop) with ubuntu (don't use windows for this, all file permissions get lost).
Browse in the extracted folder and open a terminal in there.
Then run this
Code:
sudo su
./bootrom-step.sh
Now you need to short the CLK resistor to ground.
Don't use sharp steel tools, best is a fine soft flexible copper wire...
Keep the short (steady and proper, until the script tells you to remove the short), then connect the usb cable...
It should take up to 10 seconds to find the stick and do the handshake.
If nothing happens within 15 seconds, the short wasn't that proper, in this case unplug the stick and retry again.
But it's possible too, that you've got one of the newer patched sticks!?
How old is your stick?
You can take a look into lsusb,
the first boot stage is the bootrom, it prints something about 'phone' (this should pop up in lsusb while shorted),
next stage is the preloader (if you see this, the short wasn't steady/proper).
Good luck^^
Edit: PS, to run lsusb command, you need to open a second terminal window...
Click to expand...
Click to collapse
I gave up and just bought a lite on amazon, its ONLY $18, can't beat it. Thanks for all of the assistance. If I ever get around to it ill give it another shot. Yet again thank for the help!!
Juan

Related

spv m2000 (no gsm)

hi i had another thread about this
http://forum.xda-developers.com/showthread.php?t=600587
basicly ive upgraded this unit and now have no gsm ive downloaded the software that i was advised but nothing works says files are corrupt or damaged , sometimes the link doesnt work . i need the factory rom for the orange spv m2000 i think can anybody help me pls
thanks.
since it seems to be the old problem, there was no need to open a new thread, you could have bumped the old one.
also, the answer is still the same. you can find shipped roms at http://xplode.tk
the fact that the wm2003 rom, offered in my tut thread, is corrupt, is aready known. i will fix that some time.
Chef_Tony said:
since it seems to be the old problem, there was no need to open a new thread, you could have bumped the old one.
Click to expand...
Click to collapse
i had on the 15/7/2010
i have downloaded the roms from this site for orange uk and get corrupt message i will take screen shot and show you. asap
thx for getting back to me
andy
this is the rom from http://xplode.tk for orange spv m2000 tried the mirror site and get the same message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you cannot just download and double click it, i thought that was self explanatory. you need to right click the exe and extract it, in it you will find the ruu and the roms, then you take a custom ruu, like the Chef_Tony RUU from my signature and use that to flash.
also, since you are using windows 7 to flash the device, you need to install another driver and deactivate usb connections in wmdc. use d-two's tutorial on windows 7 flashing here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
or simply use a windows xp computer and follow the tutorial in my signature.
ts ts, just doubleclicking the exe, if it was that easy, there would be no need for a 30 step tutorial
i had extracted the files to a folder .. anyways ive got more picks to show this error . after doing what was said .
Chef_Tony said:
also, since you are using windows 7 to flash the device, you need to install another driver and deactivate usb connections in wmdc. use d-two's tutorial on windows 7 flashing here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
Click to expand...
Click to collapse
done everything the pdf asked with success yet i still cant extract my orange rom as pictures above show.
you didn't do everything from the instructions, you are still using BAupgradeut.exe.
you were supposed to use MAupgradeut_noID.exe.
also, i don't see the TEST MODE watermark on your desktop, which can mean several things:
1. you use windows 7 32 bit and everything went fine
2. you use windows 7 64 bit and removed the watermark already, also fine
3. something went wrong during the installation or you skipped a step.
you should straighten these 2 things out before attempting to continue.
also you should put the device into bootloader mode before flashing, charge the battery to 100% and remove both the sim and sd card, just a general advice, i don't know, if you already did that.
the problem, the ruu gives you, however, is not solvable with any of the tips given above. the extrom from the rom you downloaded, seems to be corrupt. the extrom is the file called ms_.nbf and contains carrier-related cab files like a custom wallpaper, dialer skin and other useless stuff. here are some ways to get rid of that problem:
1. resize the partitions using mtty and flash without the extrom:
1.1 with a full battery and without sim and sd card, put the device into bootloader mode
1.2 disable usb connections in the wmdc
1.3 start mtty (look it up in the wiki or through google)
1.4 select wceusb or usb, 115200-8-1-N-N-N, press ok
1.5 hit enter, so it shows USB>
1.6 type task 28aa
now, the partitions are back to factory defaults, close mtty and disconnect the device, still in bootloader mode
1.7 delete the ms_.nbf or move it to another folder
1.8 in bootloader mode, start the ruu and flash the rom and the radio rom.
method 2 is easier:
2. crc errors appear during corrupt downloads, maybe your connection speed fluctuated, maybe you use a wi-fi connection which swallowed a bit or two, or the file was actually corrupt to begin with, try another mirror, or maybe even another rom, there are many different english wm2003 roms at xplode's archive, your carrier is not important.
2.1 flash it using maupgrade, bootloader mode, without cards...
followed you last instruction to the letter and all is GOOD
thank very much

Latest Root Tutorial

I have a HTC Desire Z.
Android Version 2.2.
Can someone please link me to the "best" (simplest/easiest) way to root my phone? I know basically nothing about this apart from what I've read on here, which at times gets confusing. I am after a tutorial for everything...ie, to install a new ROM etc. Would be appreciated.
Thanks
Follow this guide carefully step by step and you will be ok:
http://forum.xda-developers.com/showthread.php?t=905261
I'm a beginner with Desire Z too (used to own a Galaxy S) and found this guide is easy enough.
I believe the guide in the Wiki is the most reliable. At least that's what I've heard from most.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
slapshot30 said:
I believe the guide in the Wiki is the most reliable. At least that's what I've heard from most.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Click to expand...
Click to collapse
i will follow this tutorial. do i download everything on my pc, or on my phone?
which java development kit should i download?
oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
i am using windows 7 32 bit
Read up on everything Will help you understand things in the future.
I'm trying to work through the tutorials but i've downloaded and installed a JDK but i can't install the android sdk because it says it can't find the jdk.
NthZ said:
I'm trying to work through the tutorials but i've downloaded and installed a JDK but i can't install the android sdk because it says it can't find the jdk.
Click to expand...
Click to collapse
Did you install the JDK? If yes then this is a bug with the installer, just press back and then next again, it will pass this message and install the SDK.
kennytung said:
Did you install the JDK? If yes then this is a bug with the installer, just press back and then next again, it will pass this message and install the SDK.
Click to expand...
Click to collapse
yeh i found that out after a search a while ago. i installed the SDK etc and went to the first step of that tutorial above i said i was doing where it says to enter the code to check the INFOCID. i have no idea where to input that code. Looks like a lot more reading is in order
I was hoping to get this done today, but still don't seem to be getting anywhere.
I cant install the windows usb drivers, and i've downloaded so many things because each tutorial links to a different tutorial, that i have lost track of what i have and what i dont have, or where i am in the tutorial.
NthZ said:
I was hoping to get this done today, but still don't seem to be getting anywhere.
I cant install the windows usb drivers, and i've downloaded so many things because each tutorial links to a different tutorial, that i have lost track of what i have and what i dont have, or where i am in the tutorial.
Click to expand...
Click to collapse
Just follow the Wiki guide in order. Go to the HTC website and click support and find your device. Download the program called HTC Sync. When you download that program, it will download the drivers needed also.
You must enter in all the code from the command prompt. Click start on your computer, then type in "cmd" in the search bar, and click on it. It should pop up with a black prompt. It should have some words already up there, mine says "C:\Users\Sam", that means that folder is my current directory and I would have to move all the files I just downloaded to that folder. So lets say I want to change that current directory, then I would type in "cd " followed by the path of the folder. For example, I would say "cd C:\Users\Sam\Documents\HTCDesireZ\RandomFolder". Then the folder "RandomFolder" is my new path and I put all my downloaded files in there.
I have enabled USB Debugging, but when i type adb devices, no devices show up. I have done the other steps correctly. I think it may have something to do with another tutorial i did which made me turn off automatically installing hardware/updates (i think). Not sure how i turned it off though lol. Anyone know what im talking about and how i turn it back on?
argh changed it back and still not working. although when my computer tried updating the driver, it said it failed
also when i open HTC Sync, it doesn't detect my phone
So it's almost 5am. Been struggling with what seems like an intermittent problem with HTC Sync for hours now. It just doesn't want to detect my phone.
I've tried practically all of the methods in this thread:
http://androidforums.com/desire-support-troubleshooting/64808-htc-sync-cant-find-my-phone-3.html
If anyone has any suggestions, I'm open to them.
Cheers
NthZ said:
I was hoping to get this done today, but still don't seem to be getting anywhere.
I cant install the windows usb drivers, and i've downloaded so many things because each tutorial links to a different tutorial, that i have lost track of what i have and what i dont have, or where i am in the tutorial.
Click to expand...
Click to collapse
Just follow closely the tutorial that in my post above, it should include everything you need. For the driver, you can google HTC Sync and install it, after that you will have the drivers you need for you phone.
EDIT: just saw your post, do you have another computer to try on it again?
kennytung said:
Just follow closely the tutorial that in my post above, it should include everything you need. For the driver, you can google HTC Sync and install it, after that you will have the drivers you need for you phone.
EDIT: just saw your post, do you have another computer to try on it again?
Click to expand...
Click to collapse
i do have access to another computer, however it is not convenient for me to do this on another computer. It seems this is a known problem. I am using Windows 7 32bit.
Anyone got any advice for the HTC Sync problem?
this is my device manager. im guessing it shouldn't have the exclamation mark?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry to bring this up with no new info, but i still haven't been able to get my laptop to recognize adb devices.
Ok, so i have S-OFF. now what? lol

[TOOL] Incredible 2 Custom Recovery Installer

Incredible 2 Custom Recovery Installer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download removed until bugs fixed.
Requirements
Operating System: Windows XP with .NET 2.0, Windows Vista, Windows 7
MUST RUN AS ADMIN TO INSTALL DRIVERS!
Changelog
v12.02.23.2
1. Fixed deadlock when app starts without ADB server already running, added start-up status window.
2. Automatically scan for devices after installing drivers.
v12.02.23
Initial Release
Summary
This tool allows you to try out different recoveries very easily. I was frustrated with the different methods for downloading and installing different recoveries and didn't like that there wasn't really a central place to find them so I wrote this tool to use ADB and Fastboot to very quickly switch between them. This tool is very far from done and more features and probably a complete overhaul are at some point in the near future.
Bugs
1. Cannot select between different devices although it appears to allow you to do so. It might flash to a different phone if you have more than one hooked up in fastboot mode.
2. Doesn't actually check to see if the phone is an Inc 2.
3. Sometimes the recoveries get unlocked even though the phone isn't in fastboot mode, if you click one of them fastboot.exe will wait on the phone forever and freeze the program.
Upcoming Improvements
1. Much improved download size.
2. Ability to try recoveries before flashing them.
3. Threaded device state monitoring - gets rid of prompts and keeps the app from freezing.
4. Ability to select between multiple devices.
5. Eventually a better GUI.
6. More consistency throughout the program.
Reserved for future use.
im gonna try this now, thanks
EDIT: not working on Win7 x64. the program wont run. It just goes not responding as soon as i start it both as admin and normal
werdna87 said:
im gonna try this now, thanks]
EDIT: not working on Win7 x64. the program wont run. It just goes not responding as soon as i start it both as admin and normal
Click to expand...
Click to collapse
I had the same result on Win7 x64.
Update v12.02.23.2
Changelog in first post.
Fixed.
Thanks for pointing out the bug. It was the middle of the night and I was tired, didn't think to try to start the app without ADB already running. Should be fixed now in the first post.
still not working for me same problem
OP,
Are we supposed to manually install the drivers? If so, the x64 drivers will not install, even when run as administrator.
I am also getting the same result with the new files. I even tried killing and starting adb to no avail.
werdna87 said:
still not working for me same problem
Click to expand...
Click to collapse
Start ADB before running the program and let me know if that works. I did find the problem you were having and solved it on my end. Do you see a window that says "Starting ADB . . ." when you run the program? If not, make sure you're running the current version.
FC127 said:
OP,
Are we supposed to manually install the drivers? If so, the x64 drivers will not install, even when run as administrator.
I am also getting the same result with the new files. I even tried killing and starting adb to no avail.
Click to expand...
Click to collapse
Make sure your phone is plugged in before installing the drivers. You might need to uninstall other drivers first or you might not need to install the drivers at all. Does it find your phone if you just skip the driver installation?
Still no go on two different computers both Win7 x64... If I try to install the drivers separately it says that the drivers cannot be installed.
Edit: Upon further investigation, I tried to manually install again by directing the device manager to the EXACT file and this is what I get.
[/URL][/IMG]
You shouldn't have to install the drivers just to get the program to open. Can you describe exactly what's happening?
Grouper said:
You shouldn't have to install the drivers just to get the program to open. Can you describe exactly what's happening?
Click to expand...
Click to collapse
Yeah, I know... When I try to open your exe file it immediately says the program is not responding. I have tried to execute as administrator and run in compatibility mode.
[/URL][/IMG]
FC127 said:
Yeah, I know... When I try to open your exe file it immediately says the program is not responding. I have tried to execute as administrator and run in compatibility mode.
[/URL][/IMG]
Click to expand...
Click to collapse
I have the same issue stated here
Sent from my ADR6425LVW using XDA App
Alright, removed the download link. Guess I'll have to setup a VM to figure this out. It works for me with the included drivers OR the "My HTC" drivers and I'm not having any issues with the app freezing so it must be something about this setup.

[Q] help! kindle fire bricked

ok here is how it went.... i had installed cm 10 android 4.1 rom and also flashed change_to_nexus.zip. While flashing, i chose the wrong rom to flash which was my backup for stock software for kindle fire. i then installed my back up cm 10 rom. i later found out that i had deleted twrp and fff when i had flashed my stock software then cm 10... after a week of trying to find out how to get trwp.. no results.. i got frustrated and started deleting random files and one was the systems file. (dont ask why) thi forced close everything, making me reboot. from there it boots up in regular kindle fire logo, quicky flashes a whit light, then goes to a backlit screen. i drained the battery and stuff like that but no help. i try to reinstall twrp with kfu but it doesnt reconize my kindle fire. i go to devmanager and it shows up as a disk drive, amazon file-cd gadget usb device. i got to devices and printers it shows up as android. nothing reconizes my kindle fire. im only 13... dont want my parents to know cause theyll get mad. any help would be well appriciated.
thanks,
gboy
pics
i attached some pictures
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
hmmm
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
well i im 13 so i cant get the factory cable without my parents knowing... and i have tried to open the back... its super hard.. can u tell me how to open the back without scratching it.
walkthrough
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
could u give me a walkthrough how i would use command prompt and adb shell to unbrick.... please make so i can understand. thanks. i'm pretty sure i have everything downloaded that i need. also is there any chance i could fix the driver to one that kfu would reconize?
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
?
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
sorry for my stupidity.. still dont understand what im supposed to be reading from the link you gave me.
Sorry, I keep forgetting Tapatalk is a little different from the webpage.
http://forum.xda-developers.com/showthread.php?t=1869297&page=9
83
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
when u say 83 and on.. u mean 83-1 or 83 up?
Why would you read from #83 going backwards?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
soupmagnet said:
Why would you read from #83 going backwards?
Click to expand...
Click to collapse
ok ill do the back cover way.. can u give me info or post how to open the back besides using something sharp... bcause it scratching my kindle
Plastic tools are by far the best even a really stiff guitar pick will work just don't go all the way with it rather take several careful passes around the device...of course you are just removing the back cover http://m.youtube.com/#/watch?v=MGLn1TVAITQ&desktop_uri=/watch?v=MGLn1TVAITQ
firekit
ok so i guess i gotta download it to fix it if im gonna do it the back cover way. instructions on taking the backcover... without scratching...?
yay
yay got it opened... now wht???
try
when i try to download the ubuntu.. it gets corrupted at the end. i also dont know wht to do now with the back cover pryed open.
http://forum.xda-developers.com/showthread.php?t=1869297&page=9
Start at post #83 and read on.
ubuntu keeps getting corrupted on 32 and 64...
There isn't much we can do about that. That's a problem with your computer or your flash drive.
lol.. didnt have enough space on my flash drive... lets try agian...
If your not going this route you should be its all set up
Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/ use universal usb installer
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565

Zenwatch (WI500Q) firmware needed...

Hey all.
It seems like this section of the forum hasn't seen any visitors for some time, not surprising given the age of the original Zenwatch. However, I am posting this on the slim chance that someone with one of these watches might see it and help a brother out.
My Zenwatch was bricked years ago following a corrupted OTA update, and hasn't seen the light of day since. Recently though I found the watch, charged it up, and gave it another go. The stock firmware was still crashing constantly leaving the watch unusable, but I managed to install the Asteroid OS on the watch and now it works, albeit in a very limited fashion compared to the official software.
Now that I know that the watch itself is OK, and it just needs the stock firmware to be installed, I turn to you. Asus were unable to help me, as they no longer have access to the original firmware (or more likely, they're unwilling to share them with an end user), I am hoping that someone on this forum still possesses one of these watches and can create and share a backup of the OS, as it now appears that this is pretty much my last chance of getting my watch working properly again.
So, any retro watch owners left in this corner of the t'interweb?
Hi! I have this watch with stock firmware. Tell how to do the backup or send manual and I'll do it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
helloworld1337 you might be about to make a lot of people very happy!
I'm not sure how to extract the firmware from the watch, I'll have to do a little research in to that, but I don't think it's a particularly complicated procedure. Give me a little time and I'll get back to you as soon as I can.
Thanks again!
OK, I think I understand how to do this now, but as with any image copying / rooting process, only proceed if you are happy to do so, there is always the slim chance that rooting a watch can have undesired effects, but mine rooted without any issues. So, here we go...
Files that you will need...
KingRoot - https://kingroot-pc.en.uptodown.com/windows/download
ADB & Fastboot - https://developer.android.com/studio/releases/platform-tools
ADB Explorer - Can be found in the Microsoft Store. It only gets a 1* rating but we only need it to look for files and delete created images once we're done with them.
Next, connect your watch to your PC via the charging dock and a suitable USB cable. Now comes the technical stuff which I hope I have understood correctly...
1) Enable developer mode on your Zen watch. You do this by going to settings/about and tapping on the version number 7 times. This should enable the developer options, one of which should be to enable USB debugging (I can't tell exactly where this option is as my watch is running Asteroid OS, but it should be in there somewhere).
2) Extract the ADB tools to a known folder. Open a command prompt in that folder. Type the command "Fastboot oem unlock". This should unlock the bootloader on your watch.
3) Install and run KingRoot, this will root your watch granting you access to all the files on it. Again, this step is done at your own risk, I did it with mine and it worked perfectly, but it would be remiss of me to not give a warning at least. It takes a little while to complete so be patient.
4) Open ADB Explorer and hopefully your watch will be listed in the left-hand panel in the devices list. If it is, click on it and then click the browse button, this should display all of the accessible directories. In my case I see "Internal storage" and "Root", open "Root".
5) At this point we are looking for a folder that contains all of the partitions listed by name. On my watch it is in /dev/disk/by-partlabel, but again, I'm running Asteroid OS. Another possibility is /dev/block/platform/dw_mmc/by-name, but have a browse around the dev folder and subfolders, somewhere in there should be folder with lots of files, some named "boot" "recovery" and "system". Make a note of the path to these files.
6) In the command prompt type "ADB shell", the cursor should change to a # symbol (the first time you do this, type "mkdir images", this will create an images folder on your watch that'll just make things a little easier to navigate in the next steps, you only have to run this command once).
7) Type "dd if=/dev/disk/by-partlabel/boot of=/images/boot.img" but change the "/dev/disk/by-partlabel/boot" to match the path that you found on your watch earlier. If successful this will create a "boot.img" file in the /images/ directory. This can take a while depending on the size of the partition, just give it some time and it will eventually go back to the # prompt (boot and recovery are about 16mb, system is about 500mb so takes longer).
8) Type "Exit" which should return you to a normal command prompt. Now type "ADB pull /images/boot.img", this will copy the boot.img file to your PC (into the same folder as the ADB command file).
9) Use the ADB Explorer program to go to the /images/ folder on your watch and delete the boot.img file, it'll just free up space for more images.
10) Repeat steps 6-9 for the "recovery" and "system" partitions, naming the created image files recovery.img and system.img respectively. Don't forget to delete them off your watch after you have copied them to your PC as the system one takes up quite a bit of space.
11) Take the three image files (boot.img, recovery.img and system.img) and upload them to a sharing site of your choice, then let me know the links to them.
I have tested the above steps with my Zenwatch and have successfully extracted and then re-flashed the images. With luck, and the images you produce, this will allow me to re-flash my watch back to factory standard, then I'll see if there's somewhere where I can host them permanently for anyone else that may need them, as I suspect that I am not the only one looking for them.
Fingers crossed!
Hi!
I got problems with ROOTing.
Tried Kingroot, kingoroot - failed at exploiting. Also looked for TWRP, but all links dead.
ED: Failed means that process went to the end without results.
Yeah I've not been able to find TWRP anywhere either. It's gone midnight now and I'm turning in but I'll see what I can find tomorrow. Bear with me, we're almost there.
Just to check, have you done these steps?
On your watch, head to Menu->Settings->About and tap on Build number for 7-8 times until it says you are a developer. When it does, the developer menu should be unlocked on your watch.
Head to Menu->Settings->Developer options and enable ADB debugging. Without this, your computer will not be able to communicate with your watch.
Yeah sure. I also went to the fastboot mode by swiping from right top corner to left bottom at boot, or sth like that and enabled bootloader by oem unlock. Kingroot has problem with rooting because device is unsupported. It tries many root strategies but all of them are unsuccessfull. It's Marshmallow 6.0.1 - m1d65s build.
We could try Kingo Root, an ironically close name to the other app, but beggars can't be choosers at the moment.
Kingo Root, the king root android app for free.
Kingo Root is #1 one click root solution so easy to use. Take your android phone by your control! You will love this feeling - the freedom.
www.kingoapp.com
I tried it on my watch and phone but they're already rooted so the process didn't succeed (obviously), but it could be worth a try.
As I mentioned before I tried both with no success.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
As I mentioned before I tried both with no success.
Click to expand...
Click to collapse
Ah, that's my bad, I misread your reply, I didn't realise that you had already tried that one.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
Click to expand...
Click to collapse
Damn man, that is exceedingly generous of you! If you're sure that you're happy to do that then I am more than willing to cover the cost of postage. I'll PM you my details and we can get something arranged, you are an absolute legend sir.
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
helloworld1337 said:
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
Click to expand...
Click to collapse
I absolutely will do that, and thank you again, in these days of doom and gloom you have absolutely rekindled my faith in humanity .
For anyone following this thread, the stock firmware files are now available HERE.
Howdy! Nice to see you done the work
BR
helloworld1337 said:
Howdy! Nice to see you done the work
BR
Click to expand...
Click to collapse
Hi BR.
Yup, I eventually managed to work out a somewhat unconventional way to access the storage on the watch, something which I would not have been able to do without your generous donation. I also apologise for not letting you know that it arrived safely, that was an oversight on my part I think caused in part by the dejection that set in from repeatedly failing to root the damn thing .
However, between us we have succeeded in creating the firmware files, and are now able to offer them up to anyone that needs them. I'd call that a job well done .

Categories

Resources