Develop Bugs

[Q] Help! I think I've bricked my phone.

I think I have bricked my phone. I followed the instructions listed here:
http://forum.xda-developers.com/showthread.php?t=834228
but have when i restart the phone, it is just stuck on the words HTC
doesn't load into anything else.
What should I do?

Well as your phone powers on its not a proper brick, when it powers on and gets to the first boot screen like you say there is usually like a 99% chance it can be recovered.
Edit: stupid thanks button!
How long do you leave it on the htc bit before you power down again? maybe your just not waiting long enough.

left it on for 10 minutes.
all it says is "HTC" in green...

Are you able to get into hboot? Try holding the volume down key while you turn on the phone.

One easy thing to try would be to flash an RUU, make sure you find the correct one for your phone (Z or G2) and make sure its the latest one around.
That will return your phone to stock so you can attempt to root again.

yes, yes i can get into HBOOT.

my phone is a g2. How do I flash a RUU?

yukei said:
my phone is a g2. How do I flash a RUU?
Click to expand...
Click to collapse
my mistake, wasn't aware there appears to be no way to flash a new firmware on a g2 unless its by ota.... sucks
edit: just bare with us we will have an answer for you soon.

What about recovery? There should be a recovery option in the hboot menu.

Thank you so much!!

Have you got a custom recovery?
If so, flash a new rom

I tried recovery. It turns into a blackscreen with a phone in the middle and a read triangle with a ! on top of it.
I dunno if that is telling me to not turn off the phone.

MacaronyMax said:
Have you got a custom recovery?
If so, flash a new rom
Click to expand...
Click to collapse
I do not think I have a custom recovery.
How do I check?

yukei said:
I do not think I have a custom recovery.
How do I check?
Click to expand...
Click to collapse
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.

Lennyuk said:
no, from your description above, you just have stock.
I have an idea that you should be able to fasboot install a new recovery, then from there you will be able to flash a new rom.
Click to expand...
Click to collapse
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?

yukei said:
Oh ok. I think I'm a bit more calm now. So is there anything you need to know? In regards to the blackscreen with the red triangle warning sign in the middle. Can reset my phone?
Click to expand...
Click to collapse
I take it you know how to use adb (based on the root process you were trying to do)?

Lennyuk said:
I take it you know how to use adb (based on the root process you were trying to do)?
Click to expand...
Click to collapse
I know some. But not everything. Only the very basics. I have had a rooted hero before. I have had some experience with it.
I am not able to use adb tho. (As in, can't get it to work currently)
when i type "adb remount"
it says "error: device offline"
I have plugged in the USB cable.

basically all you need to do is find the clockwork mod recovery image file
put it in your adb folder
turn phone on hboot, and select fastboot
then type the following into your pc
"fastboot flash recovery [recovery.img]"
obviously replace [recovery.img] with whatever your recovery is called (and no [])
then you should be able to boot into clockwork mod recovery and from there you can install a new rom.

before I really do anything wrong here, would you be able to direct me to an image file?
http://forum.xda-developers.com/showthread.php?t=834731&highlight=cwm+recovery
i have found this thread. however, there is no option to download the recovery file.

yukei said:
before I really do anything wrong here, would you be able to direct me to an image file?
Click to expand...
Click to collapse
use this one for now, you can update with a newer one after your booted back to a rom
http://forum.xda-developers.com/showthread.php?t=834731

[Request]Acer A100 Recovery.img for ICS LOCKED

Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks

Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.

I just noticed something, you are aware that image you linked to is a A101 image, right?

masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab

rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.

You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.

Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.

citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.

Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:

citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.

masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks

liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.

masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:

masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.

Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.

Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.

liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.

pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.

liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.

No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.

[Q] Stuck in sideload - Hold power button - Nothing happens

Hi, I was flashing a new rom but I accidentally select the sideload option and now I'm stuck there,
I tried to hold power button 30 seconds, even more,(also volume down + power button) but nothing happens.
Any idea?
It says:
"ClockworkMod Recovery v6.0.2.3
Sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>"
Please help I'm n00b -.-

I did that once and I didnt know how to get out of it either. Just pull the battery and restart.

jsgraphicart said:
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
Click to expand...
Click to collapse
Thank you so much man, that worked!

ARMIGUER said:
Thank you so much man, that worked!
Click to expand...
Click to collapse
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.

jsgraphicart said:
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
Click to expand...
Click to collapse
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/

ARMIGUER said:
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
Click to expand...
Click to collapse
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?

but rdleye
jsgraphicart said:
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
Click to expand...
Click to collapse
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:

ARMIGUER said:
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
Click to expand...
Click to collapse
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.

jsgraphicart said:
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
Click to expand...
Click to collapse
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:

ARMIGUER said:
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
Click to expand...
Click to collapse
No problem. I hope you get it working. Or at least to boot up again.

Supposedly sideload in cwm is a bug with no way to back out unless you pull the battery or have usb connected [exit in command prompt?]. I was starting to like the touch recovery option, but recently i've accidentally pressed a couple of things i shouldnt have.

Sorry to hijack, but I'm attempting to sideload the 4.2.2 update from stock, and my sideload command seems to do nothing. I'm sure i'm connected as it displays my device number and "sideload" next to it. Using the sideload command simply displays the "help" list of the adb commands.
Is it a driver issue perhaps? Something else? (i noticed my batter was low just before attempting this).
Now i'm stuck in the waiting for adb sideload file.

hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.

bodh said:
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
Click to expand...
Click to collapse
I do NOT see the sideload option in the help output. I have all the latest updates from the SDK manager. Maybe i need to reinstall the SDK. I will give that a go. Thanks.
Edit: Downloaded the latest SDK/ADB and that worked. From 1.0.29 to 1.0.31

I've messed my phone with SideLoad, please help
I booted my Galaxy Nexus into custom recovery (CWM) for some other task but mistakenly gone into sideload menu!
Got no option to get back to main menu or reboot, i took the battery out and re-inserted. Now, my cell is not turning on since then!
Tried another time, took battery off but no luck..... what to do?
I've custom ROM, MIUI V5 4.2.2. My cell is unlocked and rooted, of course.
Please help.

What if the battery is non-removable?
Had stuck in that *** sideload on my SM-E500H and been waiting for the battery to drained it up all.
Yep, tried hardware button combinations as many times as I could.

if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state

lesmanaz said:
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
Click to expand...
Click to collapse
What if I'm still in sideload and get this error?
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

rooted boot image for moto360 KGW42N

This is a rooted boot image for the moto360. It was made by jcase using a dumped image from my device. It has worked fine to root my device, but nobody is responsible if it breaks your device or anything else. Use it at your own risk!
I'm not completely sure about how it works, but it seems to install the su binary to the system partition, and a few other things, so the root is permanent until you remove it somehow.
I booted this image while my watch was in the KGW42N release, rebooted normally and, after a few hours, I received the update to the latest release normally and maintained root. Your experience may vary.
As far as I know, it will also root the newer releases.
This can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot boot boot.img
** It's not fastboot flash boot boot.img ** it only needs to be booted, not flashed.
When your device has finished rebooting, you can enter an ADB shell session and type "su", it should show "[email protected]" in the prompt.
If you find something interesting about the workings of this method, please share!
Big thank you to jcase and beaups, it wouldn't have been possible without their help! Visit http://theroot.ninja/
Enjoy.
https://drive.google.com/folderview?id=0BxTLcy78OveNeW5tY180cWFhZ3c&usp=sharing
Code:
md5 for boot.img: 5c0c7e885711d94e707dd7713fce0d57
Please, don't ask about the jig/cable in this thread, I'll make some instructions soon.
To encourage more research and developments, use the donate button on the right! thanks!

Only reason that I cannot root my device
connect the USB cable to your computer.
Click to expand...
Click to collapse
so sad :/
thanks for awesome job btw

MD5? Drive doesn't seem to show them, at least not that I have found.

What can we do with root?

dproldan said:
This is a rooted boot image for the moto360. It was made by jcase using a dumped image from my device. It has worked fine to root my device, but nobody is responsible if it breaks your device or anything else. Use it at your own risk!
I'm not completely sure about how it works, but it seems to install the su binary to the system partition, and a few other things, so the root is permanent until you remove it somehow.
I booted this image while my watch was in the KGW42N release, rebooted normally and, after a few hours, I received the update to the latest release normally and maintained root. Your experience may vary.
As far as I know, it will also root the newer releases.
This can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot boot boot.img
** It's not fastboot flash boot boot.img ** it only needs to be booted, not flashed.
When your device has finished rebooting, you can enter an ADB shell session and type "su", it should show "[email protected]" in the prompt.
If you find something interesting about the workings of this method, please share!
Big thank you to jcase and beaups, it wouldn't have been possible without their help! Visit http://theroot.ninja/
Enjoy.
https://drive.google.com/folderview?id=0BxTLcy78OveNeW5tY180cWFhZ3c&usp=sharing
Code:
md5 for boot.img: 5c0c7e885711d94e707dd7713fce0d57
Please, don't ask about the jig/cable in this thread, I'll make some instructions soon.
Click to expand...
Click to collapse
If you like, I can provide hosting so that it doesn't kill your google drive. If that's OK with you, I can put it up on 2 diff hostings with unlimited bw and great speeds.

Please sell me a "jig". Or at least, show me a detailed guide on how to make one and where to buy parts.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
trevorftard said:
Please sell me a "jig". Or at least, show me a detailed guide on how to make one and where to buy parts.
Click to expand...
Click to collapse
I apologize. I literally read what you wrote at the end of your post and I can't delete my previous comment.

DELETE

I've made the USB connector, and got the device unlocked. I'm already on the R release, anyone know if it's safe to use this? thanks in advance

zNiiC said:
What can we do with root?
Click to expand...
Click to collapse
My thoughts exactly.

zNiiC said:
What can we do with root?
Click to expand...
Click to collapse
Dougshell said:
My thoughts exactly.
Click to expand...
Click to collapse
What ever you like. roms can be optimized, build.prop edits for battery and speed, themes if you like.......

Lol, I meant thus far.

Dougshell said:
Lol, I meant thus far.
Click to expand...
Click to collapse
That's exactly what he meant. That's what you can do if you have the knowledge. If you're on this site to get others work, then absolutely nothing can be done.
Anyone done this on the R build yet? I don't want to brick my device lol

beats4x said:
That's exactly what he meant. That's what you can do if you have the knowledge. If you're on this site to get others work, then absolutely nothing can be done.
Anyone done this on the R build yet? I don't want to brick my device lol
Click to expand...
Click to collapse
This is just a boot that boots on the device, not flash. It "should" work with out any issues.
I plan to try it out this weekend when I make time to unlock the boot loader and ect.

wingman_214 said:
This is just a boot that boots on the device, not flash. It "should" work with out any issues.
I plan to try it out this weekend when I make time to unlock the boot loader and ect.
Click to expand...
Click to collapse
Haha, yeah, that "should" is what worries me. And I'm outside of my return window now, so it'd be a real shame to lose the device

I did it yesterday on the R build. Everything went fine and got root access

R build rooted
I successful booted the kernel and have root on the newer R build.

I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?

vincenzo697 said:
I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?
Click to expand...
Click to collapse
The boot image linked in the op must be in your adb folder and renamed to "boot.img".

i know i am using the supertool from rootjunky http://www.rootjunky.com/motorola-moto-360-super-tool/#comment-149

Battery should be full and your display should look like this when connected:
http://m.imgur.com/YvjqY0D
Sent from my GT-N7100 using XDA Free mobile app

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error