Related
Ok, before someone goes on a tangent about how there are threads about this, let me start by saying i know, i've read over them, and i'm still stuck.
I went through this thread http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=695243 and tried the steps.
I also tried following these steps: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ The update.zip flashed like it was supposed to. After rebooting the phone, still no Go.
It looks as if it's going to work, after typing reboot in connectbot, phone boots back up without it working.
When trying to use fastboot, it gets hung at "waiting for devices". Device manager in Win7 does not show anything for the phone (the phone also does not show up on three other computer, 1 Win7, 1 Xp, and 1 Vista).
I've also followed these steps (except where noted)
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
(Could not do these due to computers not seeing device)Make sure in device manager the driver is installed(Win 7 x64 downloaded them automatically)
Open command prompt like you would to use ADB and type
fastboot oem boot
It will give you a log, look for the line that says INFOCID is SPCS_001, if it says something different, then use the generator below to create one(or hex edit the one I posted)
Download the mtd0.img attached or use this CID generator made by stevebrush over @ Modaco to create a custom one
Download the flash_image attached
Unzip both zips and copy both files to the SD card
Open a terminal emulator(I used ConnectBot) and type
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
reboot
I'm downloading a stock rooted rom now to try. During this time, it started with Fresh's previous Rom, after i used the update to go to his current rom. Since then, i've tried EvoNonsense, Damage Control, and another that i've now forgotten.
Downloading Caulkin's 1.47 rooted now and flashing.
I'm sorry if this seems like something i should have found in a search, but i really didn't find anything that looked like it'd work for me.
And yes, it is plugged into the computer, not the wall.
I had this issue a couple of times and what I had to was add to it...." or chmod u+x /data/flash_image"
This is found in a later post of the same thread. I was about ready to pull my hair out. I hope this works for you.
In ConnectBot make sure you pick local, the first time I forgot (total blonde!)
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image or chmod u+x /data/flash_image
/data/flash_image misc /data/mtd0.img
reboot
one2sas said:
I had this issue a couple of times and what I had to was add to it...." or chmod u+x /data/flash_image"
Click to expand...
Click to collapse
Ah, i read the "or" as in "type this, or that".
I'll try that. Thanks!
I receive "unable to chmod or: No such file or directory".
This is after putting Caulkin's 1.47 rooted stock rom on.
If i leave out everything past "or", it works fine, reboots, but still no usb functionality.
Try it again, but unplugged from the computer.
one2sas said:
Try it again, but unplugged from the computer.
Click to expand...
Click to collapse
Same thing:
{
"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"
}
What is mtdp0?
Worse comes to worse...re-root your phone...since it can see it via usb charging.
one2sas said:
What is mtdp0?
Worse comes to worse...re-root your phone...since it can see it via usb charging.
Click to expand...
Click to collapse
That was a typo. The next line was the correct line.
Yea, short of charging, the usb port won't do anything else.
I'm about to flash a stock rom on to it. After that, I'm at a loss.
Looks like flashing back to a factory rom didn't do anything for me either.
How can i get the amon recovery off of here so i can bring it to Sprint and have it looked at/serviced?
I had this same issue with my usb connection and no one seemed to be able to fix it. I went back to the stock rom, brought it to a sprint store and they replaced it right away.
Edit:
So how do you root without breaking usb? That's what's holding me off from rooting my new phone now.
Bump, still no usb functionality.
magnu5 said:
Bump, still no usb functionality.
Click to expand...
Click to collapse
Why did you make two threads about the same issue? I can help you, but answer the question first. One that's going to be justifiable.
pseudoremora said:
Why did you make two threads about the same issue? I can help you, but answer the question first. One that's going to be justifiable.
Click to expand...
Click to collapse
I don't believe i did.
The other thread was about having the AmonRa recovery replaced by the stock Evo recovery.
magnu5 said:
I don't believe i did.
The other thread was about having the AmonRa recovery replaced by the stock Evo recovery.
Click to expand...
Click to collapse
From the other thread:
"I still cannot use any usb functionality other than charging, and i'm running unrooted OTA1.47 now."
So, I'll repeat my question.
pseudoremora said:
From the other thread:
"I still cannot use any usb functionality other than charging, and i'm running unrooted OTA1.47 now."
So, I'll repeat my question.
Click to expand...
Click to collapse
Let me grab the title of that thread for you since you've obviously missed it in your fit of "let me smack some noobs":
"Need to go from AmonRa to Stock Recovery"
Here's another part of it you might have missed:
"I'm at the point where i'm needing to get the AmonRa recovery off and the factory recovery back in place, but i can't find out how to do it."
And the final part of that thread:
"I see a few posts that say to run the ruu, but that involves running the exe while the phone is connected to a windows workstation through usb. With no USB functionality, i'm kind of at a loss on how to proceed."
So, as you SHOULD be able to tell, that was a thread created to hopefull find out how to return the phone to %100 stock in case i end up having to return to Sprint for repair, not about hacking the phone to fix the USB port.
So, this thread = Fixing USB port
Other thread = Returning phone to %100 stock, including recovery.
Now, if you could please conclude your normal habit of bashing people, it'd be nice to have help instead of someone bickering and complaining.
magnu5 said:
Now, if you could please conclude your normal habit of bashing people, it'd be nice to have help instead of someone bickering and complaining.
Click to expand...
Click to collapse
I have yet to bash anyone, let alone you... though I really should consider it.
The premise of this thread and the other relate to each other; in that you need USB functionality to 1) Return back to stock and 2) Gain USB functionality altogether so you can gain other options besides just "charging". Obviously you're overall problem is USB connectivity.
Why you decided to go and make a different thread when you could have combined two problems into one and just updated your OP in this thread is beyond me, that's what I'm getting at.
pseudoremora said:
I have yet to bash anyone, let alone you... though I really should consider it.
The premise of this thread and the other relate to each other; in that you need USB functionality to 1) Return back to stock and 2) Gain USB functionality altogether so you can gain other options besides just "charging". Why you decided to go and make a different thread when you could have combined two problems into one and just updated your OP in this thread is beyond me, that's what I'm getting at.
Click to expand...
Click to collapse
I know this is hard to belive, but some people actually base their entire opening and reading of a thread over the title alone.
In addition to that, i'm sorry you can't wrap your head around it, but there ARE two different objectives here.
Also, lets say someone down the road needs to return to stock as described in the second thread, and does a search for it. Do you think they'd click on a thread titled "Lost USB" when that has nothing to do with their issue?
Now, if you can't contribute, i'd rather you do what you think is right, such as reporting the threads to a mod, or just not replying because you have some sense of anger at a forum you don't own or operate being cluttered.
If you can contribute, instead of arguing, i would indeed appreciate it.
magnu5 said:
Now, if you can't contribute, i'd rather you do what you think is right, such as reporting the threads to a mod, or just not replying because you have some sense of anger at a forum you don't own or operate being cluttered.
If you can contribute, instead of arguing, i would indeed appreciate it.
Click to expand...
Click to collapse
You speak as if threatening to report my post is going to change my opinion?
Report me, do it.
By the way, the answer can be searched. You just obviously haven't searched well enough. I'll contribute by saying that I've had the exact problem you have and fixed it with a very easy solution, the only difference was that I properly searched and received my answer.
With that said, I'll help you. Go here.
I'd be hard pressed to find that a MOD wouldn't give you the same suggestion I'm giving you, since XDA is based largely on the idea that searching should always be the first thing you do, which will 99% of the time return your answer... and believe me, your answer to this question is part of that 99%.
pseudoremora said:
You speak as if threatening to report my post is going to change my opinion?
Report me, do it.
By the way, the answer can be searched. You just obviously haven't searched well enough. I'll contribute by saying that I've had the exact problem you have and fixed it with a very easy solution, the only difference was that I properly searched and received my answer.
With that said, I'll help you. Go here.
I'd be hard pressed to find that a MOD wouldn't give you the same suggestion I'm giving you, since XDA is based largely on the idea that searching should always be the first thing you do, which will 99% of the time return your answer... and believe me, your answer to this question is part of that 99%.
Click to expand...
Click to collapse
you can stop replying now, since you aren't doing anything but arguing.
I've searched, and through my ignorance, i've failed to find what i need. Sue me and move on.
In case you also missed it, in the original post, i posted threads i'd found using search. Unfortunately, they didn't help me, and i failed to locate others that would. Not saying they aren't out there, i just didn't find them.
Now, what is the point of your posting, if not to help? Since you will probably claim "directing", i've already indicated i have searched, and couldn't find what i needed. Which you've either missed, meaning you need instructions on how to read posts, or you decided it wasn't up to your standards, which places you back into the "bashing noobs" category.
Again, since you aren't truly trying to help, and are instead telling me to search, when i stated i already have and failed to locate what i needed, you can stop replying now since you're only arguing.
If you decide to offer genuine help, besides things that have already been attempted and were stated to have been attempted before you ever made your first post in this thread, it will be appreciate.
Why do I want this?
Some apps do not work properly without an IMEI. The example app that I ran into is the XDA free application. Without an IMEI, the XDA app crashes when logging in. I believe it may also affect Terminal Emulator, causing it to force close on launch. The Kindle Fire, at least when running CM7 (not sure about stock), does not have an IMEI built in. Test yours by typing "*#06#" in the dialer.
Prereq's
Ensure the Kindle Fire ADB drivers are installed. The Kindle Fire Utility installed them for me.
Step 1
Download DizzyDen's IMEI generator.
Edit .ini to modify build.prop to stock Kindle Fire device identification (optional step)
(Use if you have issues with the Market or Amazon Appstore allowing you to download apps)
Settings:
Device_Manufacturer = TI
Manufacturer_Device = blaze
Device_Model = Full Android on Blaze or SDP
{
"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"
}
Step 2
Run the program! For the first option, asking about dev's rom, select "no."
Choose "yes" for in-place upgrade.
It will pop up saying "Failed to read MAC address."
Ensure that your serial number was found and the IMEI is a correct 00-#### (series of numbers) format.
If all is correct, push to device:
You must run it again on every ROM update!
FAQ
Q: Anything else this program can do?
A: Look in the !IMEIme.ini file, there are options for spoofing the device manufacturer, etc.
The following is the relationship from the ini to the build.prop settings:
Device_Manufacturer edits the ro.product.manufacturer
Manufacturer_Device edits the ro.product.device
Device_Model edits the ro.product.model
Q: Does this program support ICS?
A: DizzyDen says that it should.
Q: I've heard messing with IMEIs is illegal.
A: DizzyDen's program generates an IMEI with a 00- in front, indicating that it is a test IMEI. No illegal spoofing of a real phone is going on.
Q: Is there any way to add an IMEI to a ROM before flashing?
A: Yup, just choose "Yes" to "Are you planning to update a dev's ROM zip file?" and choose your ROM.
Q: Ran it, and under system > About Tablet > IMEI it shows as Unknown.
A: Normal, test with *#06# in dialer.
Please consider clicking a "Thanks" to me and to DizzyDen!
The XDA app works fine with stock rooted 6.2.1. CM7 might clear the IMEI.
I'll give a look to see if the I have an IMEI.
I'm in CM7 with no imei but I use the premium version
Sent from my Kindle Fire using xda premium
Thanks for the feedback guys.
I've tried the free version on CM7.. FC QUITE A BIT!!! Will try this when I get off of work. Great work btw
Sent from my SGH-I897 using XDA App
CrimsonSentinel13 said:
The XDA app works fine with stock rooted 6.2.1. CM7 might clear the IMEI.
I'll give a look to see if the I have an IMEI.
Click to expand...
Click to collapse
That's weird... Doesn't for me.... I'm going to try this fix when I get home.
Sent from my myTouch_4G_Slide using XDA App
Nice work, when I was on CM7 (now am back on stock kindle rooted) I was unable to use the XDA Free app at all because it kept force closing, though like others mentioned, the premium app worked fine.
The regular app checks for an IMEI, the premium does not.
Sent from my Galaxy Nexus using xda premium
Good find. Decent guide. xda free app is working well now.
That explains a lot! Thanks! I have had issues nwith the XDA Premium app on the Fiya.
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?
ibleo02 said:
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?
Click to expand...
Click to collapse
No... it won't cause apps to show up that don't show up... BUT
With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.
You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.
You could try the default KF info and if that don't work... make it mimic your Evo
And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.
One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.
Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?
Thanks,
td
Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.
I'm doing these steps:
1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.
I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
There may be a way to spoof this. I think the nook color does this
Sent from my Galaxy Nexus using XDA App
tduermeier said:
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.
Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?
Thanks,
td
Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.
I'm doing these steps:
1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.
I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
Click to expand...
Click to collapse
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?
A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?
MaxRabbit said:
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?
A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?
Click to expand...
Click to collapse
So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.
When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?
Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?
Regards,
td
Edit:
Tried a couple new things, still to no avail.
1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.
After this attempt I got an error reading:
This will circumvent the intent of this program by using a GENERIC IMEI. This program will not allow this. Program will exit now.
Click to expand...
Click to collapse
I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.
Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.
It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.
DizzyDen said:
No... it won't cause apps to show up that don't show up... BUT
With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.
You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.
You could try the default KF info and if that don't work... make it mimic your Evo
And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.
One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
Click to expand...
Click to collapse
Thank you sir, i will try that.
I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.
tduermeier said:
So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.
When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?
Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?
Regards,
td
Edit:
Tried a couple new things, still to no avail.
1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.
After this attempt I got an error reading:
I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.
Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.
It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.
Click to expand...
Click to collapse
The error regarding circumventing may be due to the method of rooting used causing your device to report one of the "generic" serial numbers (11223344.... or 12345.... etc) several recovery applications use this and without me taking that into account there could be MANY devices obtaining the same IMEI (which defeats the purpose)... a method you could use is
1. edit !IMEI.ini and set Use_ADB = 0
2. select yes to update developer's ROM
4. manually input your device serial number
5. flash the ROM (the one with -IMEI.zip to the device)
Alternatively you could pull your framework.jar from you /system/framework folder and select no to dev's ROM, and no to inplace... it will then let you browse for your framework file to patch.
tillum said:
I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.
Click to expand...
Click to collapse
the "Failed to mount ROM to read device information" shouldn't effect the use on a KF... since the program was originally intended for use on a NookColor... I have it written to mount the ROM partition to read the device specific files... but I also added the use of the "adb getserialno" to obtain device serial number from other devices.
I'm confused then, as it doesn't appear to be working... I will check the other error messages I'm getting and post back... basically, the program seems to be quitting with something along the lines of "Unable to generate generic IMEI... quitting" etc. Cheers.
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
{
"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"
}
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Well Done!
ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.
irisgenx said:
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.
Click to expand...
Click to collapse
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted
ananjaser1211 said:
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted
Click to expand...
Click to collapse
Okay Thanks brother. I don't have access to the tablet as of now. When I get it back , I will try this and bug you again if there's any issue.
Thanks for the WiFi tip too. I'll see if that connection is maybe damaged.
ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi
xinixi said:
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi
Click to expand...
Click to collapse
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet
ananjaser1211 said:
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet
Click to expand...
Click to collapse
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:
xinixi said:
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:
Click to expand...
Click to collapse
I just checked the UAE site. and yeah apperantly they removed the device . pretty bad, but i think if you contacted the support they may give you the link to the download site ( it is in Chinese so i don,t really think you will find it in ease)
I had the files before but the HDD the contains them died.
Welcome to the HTC One M8 S-Off GUIDE FOR NEWBIES!
Disclaimer:I am not responsible for any damage to your phone, in part, or in whole; including bad SD cards, broken reception, bad wifi, Windows 8 being installed, or anything else that could go wrong: Bricking, Bootloops, blips, beeps, boops, or sweeps. You chose to follow these instructions on your own accord and if you do so, agree that I am not liable in anyway, shape or form.
What Models/Carries Should this Work for?
USA: ATT, TMobile
European: Tmobile, VodaFone
I'm unsure if all of this works for Verizon/Sprint versions. You'll have to check the Toolkit's thread and the Firewater thread or official site for confirmation. The above models are just what I've read on the forums)
Credits:
Hansoon2000 for the HTC One Toolkit
Shrimp208 for Minimal ADB and Fastoot
Beups and Fuses for Firewater.
Ok, so, you want to achieve Root/S-Off and its many benefits. I'm going to walk you through what I did to make this process fairly simple.
Requirements:
HTC One M8
Windows 7, 8, 8.1
No Lockscreen on your phone.
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Let's Root!Use the All-In-One toolkit here:
http://forum.xda-developers.com/showthread.php?t=2699065
Process:
When you open the ToolKit, you'll notice lots of little boxes with text inside. We're going to focus on the box at the very top left that says "To root the phone, follow in order." Fairly simple, right?
First, Download and install HTC Sync Manager and make sure it sees your One M8. Do not use the Install Drivers option from the toolkit, they're outdated/don't work for most people. HTC Sync will install the latest driver for the M8. You can then uninstall the HTC Sync Manager program itself. Link: http://www.htc.com/www/software/htc-sync-manager/
Register at HTCDev. This is needed for this process to gain permaroot at the time I write this. If it doesn't allow you to register, either use a different email address, or ask a friend to do this.
Once logged in, go to "Unlock Bootloader" and Select HTC One (M8) from the drop down list. Follow the steps/prompts and directions on the site.
Get Token ID. Plug your phone in to a USB 2.0 port on your PC (not a hub, not USB3.0, USB 2.0). You should be notified that the HTC One M8 has been plugged in. If so, Proceed. If not, you'll have to figure out the issues you're having with the drivers first.
Two windows will Pop Up. Hit close on the First Window.
The second window should pop up with text. Your token ID is a long series of alpha-numeric text. This is an example of everything you should copy:
{
"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"
}
Note: Copy ALL off that text. From the <<<<Identifier Token Start down to Identifier Token End>>>>
Now, Take that copied text and submit it at HTCDev where it asks you to. If it's successful and you've copied what you need to, an Unlock_Code file will be emailed to you. Download and Place this file in the HTC One Toolkit's Data folder.
Unlcok Bootloader: Again, two windows will pop up, close the first. Your Phone should reboot and the token ID Applied. Your phone will ask you if you want to proceed. Hit Volume Up for "Yes" and Power Button to confirm. This might take a minute, don't freak out.
Flash a Recovery. Once your phone is booted back to the Home screen, go to the far right top window and Select TWRP as the recovery. Select Flash Recovery. Your phone will again pop up with two windows, close the first, and let it do it's thing. Reboot back into the Recovery after this is all done.
Flash Supersu. Go into "Install" in TWRP and select "SuperSu" from the list, swype to begin process.
Congratulations, you should now be rooted!
Time to S-Off!
WARNING: Not all devices are supported by Firewater. There's really no way to tell until you start running the process to S-Off. If Firewater tells you that your device is not compatible, then it's not compatible. You'll have to wait until Firewater does support your device and is updated.
REQUIRMENTS:
ROOTED HTC ONE M8
ADB and HTC Drivers (htc drivers should be installed from Rooting)
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Don't have ADB and don't know where to start? Then download and install MINIMAL ADB AND FASTBOOT:
http://forum.xda-developers.com/showthread.php?t=2317790
Once Downloaded and installed, go to your Start window on the PC and search "ADB". Minimal ADB and Fastboot (here on referred to as ADB) will show up, click on it to bring up a Command Prompt. Using Admin Rights isn't a bad idea either when using ADB.
Go to http://firewater-soff.com/instructions/ And make sure you Follow the Prerequisits to the letter! Read the Instructions for "Rooted, Normal Device Method"
Now that you have the Firewater file, go to Start and Search for ADB, RIGHT CLICK and choose SHOW FILE LOCATION. Drop your Firewater file here. Now we can begin!
Process:
Connect your phone to a USB 2.0 Port if you already haven't and make sure your phone is on the Home screen with NO LOCKSCREEN OF ANY SORT
In the Command Terminal, Type:
adb device (this should show you that your phone is connected. If it says that the phone is inactive/offline, then unplug your phone and replug it. Try again. It should now show up).
Type:
adb Reboot (this will reboot your phone)
After your device has rebooted, there's a 99.9999% chance that it will ":go offline" and not connect to adb (we can confirm this with "adb device" command. Unplug, Replug your phone and ensure it's online and ADB can see it).
Type:
adb wait-for-device push firewater /data/local/tmp
Type:
adb shell
Type:
su
Type:
chmod 755 /data/local/tmp/firewater
Type:
/data/local/tmp/firewater
If you're successful up to this point, Firewater will ask you if you're sure. Type:
Yes
At this point, the Command Prompt will start Chugging bottles of Firewater. Some Command Prompts only Chug One, others, 5,6, up to 12. If you reach 13 Bottles, Abort and try the steps again. This may take a while and several resteps, just be patient. The command prompt, when successful, will notify you that you are now S-Off!
To check this, boot in to Bootloader to confirm (it will say S-Off, not S-On).
The Why:
I believe the reason you need an internet connection is that the Firewater file connects to a server and the voodoo is all done by the server. Why would they do this? Probably to ensure that HTC doesn't screw us out of S-Offing our device like they're known to do by downloading and decompiling files used to S-Off or reverse engineering steps taken to S-Off If anything, this slows them down (and possibly makes it impossible for them to stop us from doing so.)
Special Thanks:
Beups, Fuses, Hasoon2000, and all Developers that are supporting our device with lots of goodies. Don't forget to donate to them to encourage them to spend time on our device, or, just buy them a beverage for all of the hard work and time they spend doing this for us.
If I have forgotten anything or forgot to give credit to someone, please let me know and I'll be sure to add it.
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
stuart0001 said:
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ah, yes, you're correct. Thank you!
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Yes adb shell
Sent from my HTC One_M8 using xda app-developers app
Learoy1 said:
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Click to expand...
Click to collapse
Did you get it all worked out?
Also, I updated the OP to use "adb shell," I apologize, I should have remembered that adb need to be there. As well, I've updated the OP to point to the latest HTC Sync with drivers.
Sorry for the question but it's my first HTC device and I'm studying in deep all the aspects of bootloader, s-off and so on.
What about I need to come back the M8 for warranty?
If I am right I can restore stock rom and recovery and relock the bootloader through s-off. At this point, what about s-off? Is there a way to revert it to stock s-on?
This Rooting method works for the International variant as well right?
Just can't seem to get my device online. I've tried just about everything, restarted phone, laptop, server, different port, different cable, etc. I see a notification that says "Media Device [MTP] connected", and I have an inkling that it could be causing issues, but I can't seem to find a way to disable it. Is anyone else having this issue?
(T-Mobile M8, perma-rooted)
*edit* After several attempts, I seem to have gotten the timing right, using the version of ADB that came with the all in one tool. Somehow it just started to work, but only with that version. Other versions of ADB still saw the device offline. Just one of those annoying things. Either way, I'm now S-OFF. That was the last piece I was missing. Thank you.
Not working!
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
patstar5 said:
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
Click to expand...
Click to collapse
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
BerndM14 said:
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
Click to expand...
Click to collapse
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
patstar5 said:
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
Click to expand...
Click to collapse
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
BerndM14 said:
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
Click to expand...
Click to collapse
Titanium backup won't let me backup to sd card, I guess I could backup to internal storage and put it on pc like nandroid or move it to sd card afterwards? I could just download custom rom to my phone, goto twrp and flash it without pc? Is there any dual boot method of roms? I know for m7 there was something that let you switch from sense to stock android with press of button.
Lost & Puzzled Newbie
Hi Guys,
I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!
So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.
I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:
http://forum.xda-developers.com/showthread.php?t=2799796
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.
What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.
I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!
Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop
However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?
EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!
EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier
ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted Now I could just do with some help deciding what ROM to install & help on how to go about it.....please
EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!!
I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!!
If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it
p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!!
delete
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 .