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.
Related
I just purchased a Motorola Defy in Thailand (there are not many of these here…Moto’s seem to be very rare here) and I have not been able to root this thing no matter what I have tried. None of the one-click solutions seem to work. I have been able to push the required files via adb to the phone, get into the shell and run the exploit.bin. I get back to the original directory but I the phone disconnects and when I run the adb devices command I get no devices attached. If I reboot the phone I can get it to show up on the adb devices list, but when I run the adb shell I only get a $ and not #. I have tried this many, many times with the same result. I have also re-installed the Moto usb drivers many times and does not seem to make a difference. I must be doing something wrong. This is a brand new phone in Thailand, and probably has only been available here very recently.
I really do not have any experience at any of this but I am trying to learn. I also really need this phone rooted because I cannot access any paid apps in the marketplace In Thailand, and getting some of these apps would make my life easier. I am confident I can get them if I could get root access (using MarketAccess). The reason I bought the Defy in Thailand and not another phone is it is compatible with my home country. Maybe I blew it…..
Any help or advice would be very much appreciated.
I am brand new to all of this, and have no idea what I'm talking about.
A search turns up two guides on how to do this. One at a site called dkszone and one here. Simply by searching "root motorola defy". Dkszone credits xda with the guide. Their guide is a little different, though, in that they reference an ADB gui for Windows, which is what I would have to use. Both guides are worth reading. I can't link to them because I have not posted here enough.
One thing that does strike me is that you make a reference to getting back to the original directory and your phone disconnects. Both guides make a reference to having to reconnect. XDA in step 5 and dkszone in step 7.
Someone here knows the answer.
Haven't been to Thailand in a while. Lived on Soi Lang Suan in Bangkok for two years. '95 and '96 maybe. Is Shinawatra still in exile? I'm sure you must know that he essentially brought cellphone service to Thailand. In a big way, that's for sure. This long before he became the PM, or whatever they call it now.
.
more specific info
I will try to get a little more specific…
I’ve used the guide posted on xda forums and I can push via adb the following files like this:
adb push Superuser.apk /sdcard/Superuser.apk
abd push su /sdcard/su
adb push busybox /sdcard/busybox
adb push exploit.bin /data/local/tmp/exploit.bin
Seems to work no problem…..
I then type the following commands
adb shell
cd data/local.tmp
chmod 0755 exploit.bin
./exploit.bin
The system chews on it a bit, shows a bunch of remarks, then $, then forked a bunch of childs (scary) and then displays the starting directory (C:\documents and settings\userblahblah).
At this point things go nowhere. There is a remark about restarting the adb server on the desktop and re-login. I guess I am not exactly sure what that means or how to do it. If it means unplugging the phone and plugging it back in I have done that. If it means rebooting the phone and/or rebooting my pc I have done that as well. If I type adb devices at the command prompt after running the exploit.bin) I get “list of devices attached” with nothing listed below. I can use kill-server and then again enter the adb devices command (adb starts) but the phone is still not recognized. I can check for hardware devices attached through device manager and the ADB interface does not show up (although it was there when I started this procedure) If I type adb shell at this point I get a device not found error. The only way I can get the phone to be recognized again is if I reboot the phone. When I do this the adb interface is listed in system hardware, I can run the adb devices command and the device shows up. When I run the adb shell command now I get a $....so no permissions, right? This has been a long, frustrating experience.
Does anyone have any idea that I am doing wrong or know of any way to fix this?
Any help or other ideas would be very much appreciated…..
BTW,
I’m pretty sure Shinawatra is still in exile…I think he has like 20 passports or something. Who knows where he is...
I really don't know what to tell you. I really don't.
I would not be able to use that program you are talking about. I would have to use a one-click method. I know you said you have tried the one-click methods before.
I don't need this for my phone and it wouldn't work anyway, I suppose, but I put the one-click .apk on mine just for illustration purposes.
This on a phone with ASTRO file manager pro.
Downloaded one-click .apk from here onto my hard drive. That first post reads that the app is available on the Market. I couldn't find it.
Pic 1 - moved file onto my phone then removed phone from laptop
Hit the ASTRO icon on my phone and I get what you see in pic 2.
Hit sdcard and got pic 3.
Scrolled to bottom and hit the .apk and got pic 4.
Hit Open App Manager and got pic 5.
I can't continue from there because it's not made for my phone.
My intent is not to insult you. If you have done this and it doesn't work, then I am just at a loss. If the info is of no use to you, maybe someone will find it useful in the future. I suppose it's possible that this is all in the thread that I linked to. I can't take the time to read 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"
}
Thanks for the input and the concise instructions. I have actually tried running the z4root.apk file from the phone. It installs just fine. When I run the program (for those familiar with it) I choose permanent root (or temporary root, I have done both). There is a notification at the bottom of the program that is telling you what the program is doing at the time. It displays ‘Running exploit in order to gain root access’ (or something similar) and then ‘acquiring root shell’. The z4root program stays on the ‘acquiring root shell’ screen for about 10 seconds or so then the screen reverts back to the all applications screen. No confirmations or error messages…nothing. And the phone is definitely not rooted.
Going to Hong Kong for a day…wish I could use the app store for my wanted apps there….I think I'm going to have the same issue as Thailand (no paid app appstore access).
Still hoping for an answer….and I'm not talking about throwing my phone out the window….yet…
Rooting Motorola Defy
Z4Root does the same thing on my Defy. I also can’t pass through ./exploit.bin either. After executing exploit.bin I get dropped to c:\...\... as expected but then I can’t even go back in adb shell as it gives the error: device offline…I can only get to adb shell after rebooting the phone, however it takes me back $ prompt instead of # prompt. So it seems like this exploit.bin is not capable of giving me # (Root) prompt and so I am unable to mount system partition with read and write access and so unable to execute the rest of the commands on the phone as well. Am I doing it wrong or missing something here? Thanks for the help.
The z4root worked fine till version 2.34.1. From 2.51 version on there is another utility superoneclick. You can find it in the defy section of the forum. Worked for me and a lot of others.
Sent from my MB525 using XDA App
Success!
I do not know why I did not find this tread before but I did get my Thailand Defy rooted using the info and file on this tread:
http://forum.xda-developers.com/showthread.php?t=913709
I need to improve my thread searching skills....
The superonclick version that I had tried previously was different than the one posted on that thread and I did not need to use 'turn on turn off stuff' noted there........one click...done......as advertised.
Thanks for everyone's help.....you have saved a Thailand Defy from a 30 story dive out of the window..... (and saved my sanity).
Success!
Ditto from an apartment on the 13th floor in Ottawa, Canada.
Rooting a Defy
I have one too. While I was on 2.1, I had to use an old version of Super One Click. The update finally came out for my phone, and moved it up to 2.2.2. The update killed my rooting, but the current Super One Click worked like a charm after the update. Mine was from the UAE, and I live in the USA, so some of the pre-installed apps did not apply to me, and were really annoying, trying to localize applications into languages I can't read or speak. Rooting let me kill off some pre-installs. The new version also seems to be a lot more battery gentle, although it really hit the battery hard the first day (I think it was just getting all of the cache and settings caught up using a lot of data connection.)
SO i posted this in another thread, thought I'd start one here.
Im sure a lot of people are facing the same issue as I am. So any assistance would not only help me, but plenty of others as well. Here it goes:
I just joined XDA...if there ever existed a supernoob when it comes to phones, then thats me...i have almost absolutely no idea about flashing, roms and whatnot...i just know they exist
My problem is that I have a galaxy nexus, yakjuux, here in Canada, and as everyone else, thinking of flashing to yakju for the updates.
I have a black macbook, and I was reading on how to flash...and i just couldnt piece together all of the information thats available.
Anyone here generous enough to help me flash to yakju to get the updates?
walk me step by step as to how to flash...like literally step by step, with every bit of detail.
Im not completely dumb with technology, but its just with phones that I fail.
Thanks!!
time for some tough love... You need to start reading and figure it out. These exact threads, nearly word-for-word, have been posted for the last 3 months straight, and have been answered the exact same for 3 months straight. There are guides, stickies, posts, videos, etc. all sitting in these forums. You are seriously going to get yourself into some nasty **** if you just let someone tell you what to do and you have absolutely no idea what's going on while you're doing it. Search. Please.
Good luck.
Thanks martonikaj,
I understand the multitude of information available out there, but there is nothing for mac in terms of videos that helps flash from yakjuux to yakju.
If i missed something, would you be able to post it? I would be grateful.
Its just a matter of getting a guide that's concise and concrete.
mace17 said:
Thanks martonikaj,
I understand the multitude of information available out there, but there is nothing for mac in terms of videos that helps flash from yakjuux to yakju.
If i missed something, would you be able to post it? I would be grateful.
Its just a matter of getting a guide that's concise and concrete.
Click to expand...
Click to collapse
There is nothing different about a Mac guide. In many ways its simpler. The only difference is that you need the Mac version of ADB and Fastboot files instead of Windows ones, and you need a "./" in front of the commands in Terminal (instead of Command Prompt). There are no "1 click" (toolkit) methods for OSX. Do it manually you'll be better for it anyway.
I've attached ADB and Fastboot files.
Got past that, serial number is not showing up though...aghh
is there no video to show how its done?
mace17 said:
Got past that, serial number is not showing up though...aghh
is there no video to show how its done?
Click to expand...
Click to collapse
so you've downloaded and unzipped ADB and pointed Terminal to that folder, connected your phone and enabled USB debugging, and type "./adb devices" and nothing shows up?
umm yeah I did all of that...
i sent you a message!
Sorry for the stress haha, tough love indeed it is...but this is driving me crazy...
mace17 said:
umm yeah I did all of that...
i sent you a message!
Click to expand...
Click to collapse
On computer:
1) unzip Mac_ADB_Fastboot.zip
2) Move files somewhere, like your <user name> folder
3) Open Terminal
4) type "cd " and drag the unzipped Mac_ADB_Fastboot file into the Terminal window (or manually navigate if you know how to do that) and hit enter
On phone:
1) turn on USB debugging in developer options
2) connect phone via USB
There is literally nothing else to do to get the computer to recognize the device.
So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Thanks for sharing this find, I'm sure others will find this to be useful
No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up
Next time I'll be more safe while flashing roms to my phone.
Great find.
wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?
This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that
Yup. In most cases, there's a way around a problem, you just have to dig until you find it
Congratulations
Saludos desde Ecuador
Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!
rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/
Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!
I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"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"
}
I would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).
Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...
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 .