Database Info

Clockwork Latest

Clockwork isn't working properly for me. Can anyone point me in the direction of a download for the latest Glacier recovery image? Thanks.

enculturation said:
Clockwork isn't working properly for me. Can anyone point me in the direction of a download for the latest Glacier recovery image? Thanks.
Click to expand...
Click to collapse
ok, so first, how is it not working for you, what is your clockwork mod number, and recovery image number, when you post a problem, we can not just read your mind, so as much information about your phone you can give, aka, rom, kernel, root method, what you did prior to it messing up, and what you were doing when it messed up, apps installed, ect.... the better we will be able to help you... if you dont give that info then you should click on the link in my signature that says THIS GUY, cause that isnt who you want to be... help us to help you and it will be as fast and easy ass a poop after an all you can eat wings and $1 pitchers at hooter night!!!

I'm just looking for a link to the image LOL, if no one has it that's cool I'll be "that guy."

enculturation said:
I'm just looking for a link to the image LOL, if no one has it that's cool I'll be "that guy."
Click to expand...
Click to collapse
if that is all you need then i would have to say use the search button, i know it has been posted, but i am not sure where, as i havent had a need for it yet, but if you cant find it with the search function, then i will try to look it up for you..

the thread you are looking for is here

enculturation said:
I'm just looking for a link to the image LOL, if no one has it that's cool I'll be "that guy."
Click to expand...
Click to collapse
Here's a direct link to CWM 3.0.2.4 from the official source: http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-glacier.img.

Hey, thanks for the links guys; much appreciated.
I had T-Mobile send out another Glacier for various reasons and I had to get S-ON (quickly) so I could return my 'defective' unit. I was bouncing back and forth between my rooted stock nandroid, and a CM 7 nandroid (which means Clockwork as well) trying to get everything sorted.
I couldn't get the latest Clockwork app to download any of the recoveries, it was giving me that "error encountered while flashing" message. I didn't have any time to deal with it so I figured I'd just manually flash them.
The Clockwork error seemed to be server related. That's what I found when I Googled the error message last night anyway.
Sorry for the long winded response, I just wanted to give you (irrelephant) an explanation as to why I was a little short.

enculturation said:
Hey, thanks for the links guys; much appreciated.
I had T-Mobile send out another Glacier for various reasons and I had to get S-ON (quickly) so I could return my 'defective' unit. I was bouncing back and forth between my rooted stock nandroid, and a CM 7 nandroid (which means Clockwork as well) trying to get everything sorted.
I couldn't get the latest Clockwork app to download any of the recoveries, it was giving me that "error encountered while flashing" message. I didn't have any time to deal with it so I figured I'd just manually flash them.
The Clockwork error seemed to be server related. That's what I found when I Googled the error message last night anyway.
Sorry for the long winded response, I just wanted to give you (irrelephant) an explanation as to why I was a little short.
Click to expand...
Click to collapse
all good bro, glad i could help, and thank you for the explination! and i appologise if i came off rough, but i was in a mood last night it seems, and i am in a great about to get toasted mood tonight, so i am glad we could help ya out!!!

enculturation said:
Hey, thanks for the links guys; much appreciated.
I had T-Mobile send out another Glacier for various reasons and I had to get S-ON (quickly) so I could return my 'defective' unit. I was bouncing back and forth between my rooted stock nandroid, and a CM 7 nandroid (which means Clockwork as well) trying to get everything sorted.
I couldn't get the latest Clockwork app to download any of the recoveries, it was giving me that "error encountered while flashing" message. I didn't have any time to deal with it so I figured I'd just manually flash them.
The Clockwork error seemed to be server related. That's what I found when I Googled the error message last night anyway.
Sorry for the long winded response, I just wanted to give you (irrelephant) an explanation as to why I was a little short.
Click to expand...
Click to collapse
Out of curiosity, how did you go about turning S-ON? (And what rooting method did you use?)

kimbernator said:
Out of curiosity, how did you go about turning S-ON? (And what rooting method did you use?)
Click to expand...
Click to collapse
All I did was restore it to my stock rooted nandroid and run
Code:
./gfree --secu_flag on
(I'm fairly certain this was the command that I used).
Code:
sync
The unroot.sh, & the revert instructions in the (True S-OFF) thread did not work for me.
The gfree command was the only thing that actually worked; there's a related thread out there somewhere I'll see if I can find it.
I rooted via the gfree method.

Here's the thread, I just followed Erik's instructions with the gfree command.
http://forum.xda-developers.com/showthread.php?t=1043740

HELP!! No Android Recovery option

Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers

ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!

djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.

The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?

yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019

Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....

im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.

I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.

solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom

DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?

assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.

okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.

According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?

no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?

autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help

much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _

fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.

the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?

aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.

I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?

[Q] lg g2x install JB.. now frozen on boot

hey everyone!
yesterday, I got really tired of froyo so I said ''f$%? it, lets try to root my phone and install jelly bean, that look really slick!''
. well looks like everyone as to start somwhere..
so my problem right now, I am stuck at the custom LG logo, I cant hard reset and even my recovery boot but the menu wont pop up and simply restart my phone..
basicaly, I feel screwed right now does anybody can help me on this?
it is probably something super stupid and simple but I can'T find any solution so I decided to join this forum for a bit of support..
EDIT: my mistake, it went in the wrong section
thx a bunch!

Usually run this when I cluster f my phone
http://forum.xda-developers.com/showthread.php?t=1590523

thanks for the cue, I will also try this. and keep you posted if it worked or not..
better way to learn is to make mistakes!
http://forum.xda-developers.com/showthread.php?t=1180331

ok, most of the link to download the needed files are dead... I might have to rely on your support guys.
the http://forum.xda-developers.com/showthread.php?t=1180331 thread didnt helped enough..

Did you install the adampk rom?
Sent from my LG-P999 using xda app-developers app

no I haven't...
so far , what I did is
root the pone with the one clicker (wich was a success)
did the recovery with the clockworkmod recovery thing,
restarted and exectued this website's tutorial to jellybean (start with WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed..
this morning, I managed to get back to the recovery boot screen and found that if I press the house icon it show up a menu.. but this menu giving me access to reboot, wipe cache, data or install update.zip (which was supposed to fix my problem) but this menu is blued out and unaccessible..
dunno if it helped..
right now, I am trying to get acces to my phone doing the no battery boot thing but my pc doesnt seem to recognize my phone + I am at work hehe so I am pretty much limited in acces due tu the it protection and firewall stuff
I am gonna try to redo that stuff tonight at home but meanwhile, if any of what I described may give you a clue on how to help me, I really appreciate the effort!
thanks again for the support guys, I know it can be a pain sometimes to help people screwing some beginner stuff like I probably do right now

dubmah said:
WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed
Click to expand...
Click to collapse
I say you needed to use the g2x android development forums on this site to find a suitable jb rom, not this other site. The one click method isn't very stable, so nvflash is most definitely what you need to try to get working. There are very thorough tutorials on how to get that to work. Do you know which clockwork recovery version you have installed? Should be 5.0.2.0. Once you get home, I suggest you read read read. Do as much research you can to make sure you can follow nvflash instructions to the letter. I know I personally spent about a week researching to make sure I had a solid understanding of the procedure.
I recommend getting nvflash going to get clockwork properly installed, then download a rom from xda, nowhere else. I would even say use a gb rom before trying a jb ...the jb roms are hackfest versions, so they have (from my experience) much poorer battery life, and lack hardware acceleration. Netflix and many 3d games won't work. You can use adampk or mazout's roms but they don't have working radio, i.e. no phone/SMS functionality.
Sent from my LG-P999 using xda app-developers app

dubmah said:
no I haven't...
so far , what I did is
root the pone with the one clicker (wich was a success)
did the recovery with the clockworkmod recovery thing,
restarted and exectued this website's tutorial to jellybean (start with WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed..
this morning, I managed to get back to the recovery boot screen and found that if I press the house icon it show up a menu.. but this menu giving me access to reboot, wipe cache, data or install update.zip (which was supposed to fix my problem) but this menu is blued out and unaccessible..
dunno if it helped..
right now, I am trying to get acces to my phone doing the no battery boot thing but my pc doesnt seem to recognize my phone + I am at work hehe so I am pretty much limited in acces due tu the it protection and firewall stuff
I am gonna try to redo that stuff tonight at home but meanwhile, if any of what I described may give you a clue on how to help me, I really appreciate the effort!
thanks again for the support guys, I know it can be a pain sometimes to help people screwing some beginner stuff like I probably do right now
Click to expand...
Click to collapse
Boot into recovery, there should be an option to format or wipe system. Do that then flash the ROM. It won't boot if you flash it over stock.
Also, use the paranoid android rom found in the development section, same cyanogenmod base but works better.
Sent from my Nexus 7 using Tapatalk HD

great ! thx for the advices ! yeah I Will read some more first, making sure I do thing properly, for now, I will try to revert at least to my backup and wait til I know what I'm doing!
thx again, I keep you up about the progress !

progress!! .. I tried to start my phone without the battery.. my pc recognized the phone for about 10sec and then the icon disapeared and until then, nothing I plug I start there is no way I can make my pc to recognize the phone...
does this happened to anyone before?

allright! I have bean reading about the NVFlash! that help A LOT! actually it almost fixed my thing! the phone is now unbriked YAY
I just keep replying to myself incase there is another guy who dont know crap about the obvious, if it can help the thread worth it
I used this tutorial to fix things,
http://forum.xda-developers.com/showthread.php?t=1248644&highlight=nvflash+steps
My main issue was the APX driver wich wasnt installed.. now I know bit more, I still have issue but luckily things goes forward so it gave me the boost to keep working on
but I face a new problem so maybe some of you might be able to help on that new issue
I am from montreal and here in quebec we have videotron instead of t-mobile and since I used a t-mobile boot it looks like my sim card is not recognized anymore..
is there a way to fix that? am I supposed to find a videotron thing?
hope it helps

dubmah said:
I used a t-mobile boot it looks like my sim card is not recognized anymore..
is there a way to fix that? am I supposed to find a videotron thing?
Click to expand...
Click to collapse
What do you mean by "T-Mobile boot" and "videotron thing?"
Sent from my LG-P999
---------- Post added at 10:09 PM ---------- Previous post was at 10:02 PM ----------
Ok, wait I think I understand what you're saying now. If you can, pm the op of that thread you used to unbrick. Ask that person if you need some kind of different file in that .zip file to work on your carrier.
I remember having to use that guide to get back to stock. Glad to see you're making progress. I know it can be frustrating when devices get wacky. Good luck!
Sent from my LG-P999

hehehe sorry, I am not fully used to the right terms so I rather stay in the gray zone by using words like ''thing''
but I can now oficially say I was talking about ROMs
finally, I managed to bring back my phone to the stock mode everything seem to work!
now I can brick it again!
thx for the help!

I began to wonder if it was just a matter of changing APN settings?
Sent from my LG-P999

this, or... putting the simcard in the properly? !!

[Q] Help with Flashing Linkify fix to CleanRom 6? (Solved)

Yes, I'm a noob,to XDA, but I am pretty tech capable otherwise.
Yesterday, I unlocked the bootloader on my OneX, installed TWRP 2.3.x recovery, flashed CleanRom, ended up with a soft bricked the phone (still not sure what happened, but I think it was my stupid ancient work computer), tried to reinstall it, but the zip file was no longer in the SD card, tried to mount in recovery, but it was unsuccessful, tried to reinstall the 2.20 RUU, but it failed (all of these were probably B/C my work computer again). Gave up and came home. Got home to my modern PC, reformatted my SD, transferred Zips again and was finally able to get CleanROM to install correctly. All seems good, I setup the phone last night.
However, I have a problem with hyper-links that Scott has already acknowledged here:
http://forum.xda-developers.com/showpost.php?p=38936130&postcount=9922
I would have just asked this in that thread, but I don't have enough posts to write in Dev forums.
So, does anyone mind directing me to some basic instructions for 'flashing' the Link Fix Zip that Scott mentioned? I am assuming it is not the same method as installing the ROM.zip from TWRP, or is it?
After soft bricking yesterday, I'd really prefer some hand holding on this so that I don't mess up the successful CleanROM install.
Thanks in advance.

flash it in recovery just like the rom

jerrycoffman45 said:
flash it in recovery just like the rom
Click to expand...
Click to collapse
Thanks! That took all of 30 seconds plus reboot. Links working now.
Problem Solved.
Thanks Jerry!

please add solved and give thanks

DvineLord said:
please add solved and give thanks
Click to expand...
Click to collapse
Done, unless there is a tool for marking the thread "solved". I looked but didn't see anything.

NM, I figured out how to change the header.

[Q] Phone stuck on "this build is for development purposes"

Yep so I tried to install CM11
and the last thing was to:
fastboot flash boot boot.img
and that was it. Cannot restore my Nandroid backup - it doesn't boot back up.
Just gets stuck at the HTC page with "This build is for development purposes".
I think I need the stock boot.img but it is no where to be found.
Any help??

Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.

Who did you find to restore your phone?
808phone said:
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Click to expand...
Click to collapse
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?

so basically you paid a guy to google the right RUU???
all you had to do is check your CID (its written on fastboot) and search for that, they really arent that hard to find!!
http://forum.xda-developers.com/showthread.php?t=2140967
also if you're going to keep flashing different roms its also a good idea to keep that RUU on your pc somewhere!!

There was no matching ruu. What no one told me was that you could use a newer ruu than the one you have. Another thing, before you judge, there were no replies to help me so I had no choice. Since then look how many times I have helped others.

chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.

In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app

zubeedubs said:
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.

808phone said:
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
Click to expand...
Click to collapse
dude theres no need to get fassy about anything... unless your one s is knock off means that there is a RUU for your device and that you simply couldnt find one in the small amount of time that you searched for one...
and just to gnaw a little more at your flawed logic and sour attitude RUU means "ROM UPDATE UTILITY" so i guess your right in not being able to use a newer one... :good:
AND BTW.. i dont have a jtag but i do run a business and in my line of work we see folk like you everyday, ever so quick to get pi**ed at someone for THEIR OWN mistakes!!!
and maybe if youre that impatient and wound up for your own calamities it serves you right to have paid for a simple task..
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
have a peek at the RUU thread in the dev section and follow the instructions... it really isnt that difficult!!!

? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.

808phone said:
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
Click to expand...
Click to collapse
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!

808phone said:
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
Click to expand...
Click to collapse
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.

same problem
zubeedubs said:
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
Click to expand...
Click to collapse
Just to say that I

chrons6 said:
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
Click to expand...
Click to collapse
Thankfully I finally figured out how to consistently get my phone to enter into Fastboot; however, no the trouble I'm having is finding the proper RUU. I've tried the 3 T-mobile varients available in the RUU depository found here
http://forum.xda-developers.com/showthread.php?t=2094414
But alas, while I am able to run the RUU program, which enters my phone into a mode where the screen is all black expect for the HTC logo in the middle, I keep on getting error codes. Are there more than 3 RUU varients identified in the depository?
Oh, I should note that I was also able to get into recovery, but my SD was unable to mount so I can't find my Nandroid

Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app

zubeedubs said:
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.

chrons6 said:
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
Click to expand...
Click to collapse
That won't help. You can fix the sdcrad bug by flashing stock recovery via fastbot and preform "factory reset + clear storage"