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
Related
Hello, boy do I have a mishap. Well, anyway to begin I will say that I decided I wanted to root my phone to debloat it. So what I did, is downloaded the EE4 update and did the VooDoo V4 Kernel that flashes CWM and EXT4 and other junk. Well that all went great. I got it rooted and such but then just tinkering around I went into Rom Manager and told it to back up. WELL, when I did this the phone got locked on the SAMSUNG boot screen for hours and continued to refuse to boot. SO, I attempted to fix it by installing altered beast just to get the os running again and went into clockwork and backed it up. Then I went to the rooted ed1 to bring it back up to EE4 rooted and with the voodoo kernel and such but it refuses to open clockwork! The voodoo kernel changes filesystems and roots it and such but clockwork wont load. When I try to flash it in rom manager it says its succesful and then i go to reboot in recovery. It takes me to the Samsung Recovery 3e, I try to the update.zip, (yes i took the cwm recovery-update.zip and renamed it and through it in the sd card root) but all that happens is that a progress bar shows up for a split second then the android guy with the triangle and ! shows up and it does nothing. Help? I really need to back it up, preferably in the rooted ed1 but in ee4 will work to. Any ideas would be appreciated. I used odin v1.3 by the way. Im willing to try anything to get clockwork to boot so i can back it up. What do I do?
EDIT: Also, now when I go into 3e recovery, it complains saying " cant mount /dev/block/mmcblk0p3 " or something like that.
Did you read anything on this forum beforehand? Or just go link by link downloading files and deciding what to try on your phone?
Just saying..
Yeah, I did. Ive searched everywhere. I cant find anything about my problem. Ive looked at things that are close, hoping a solution can be found but nothing and no I wasnt just downloading files and spoon feeding them to my phone.. I just wanted to be able to debloat it.
Go search about Rom Manager and let us know what you find out...
I dont see how thats going to get me one step closer to solving my problem. Ive done the searching, now im asking.
Start w/ this one. http://forum.xda-developers.com/showthread.php?t=1100384
I can't tell where you are currently on your phone from reading that as it's to much text in one paragraph and it isn't put together in a logical sense and seems to jump around. I would look at the instructions for going to rooted EE4 in the Dev forum as that should get you to where you want to be with voodoo/cwm/rom
Instead of being a Forum Snob. If you know the answer, why don't you just help him out?
There's an abundance of confusing information on here and everyone uses acronyms. I too searched for hours on how to solve a similar problem and ended up having it taken care of for me. People join communities like this one for help. Not to get flamed for asking a question. It may be elementary to YOU but not everyone.
Thanks, for the care. Sorry about that if its jumbled, im frustrated with this because ive flashed the rooted ed1 about a billion times now, trying everything to get it functioning. Id be glad to try to explain again if that could help? Ah, yes. Well, I returned to the forum about installing the voodoo kernel. I followed the process word for word. But it just doesnt seem to want to work. Right now I just flashed it again back to the rooted ed1. Would I be able to put CWM on there at that point?
Jessman123 said:
Thanks, for the care. Sorry about that if its jumbled, im frustrated with this because ive flashed the rooted ed1 about a billion times now, trying everything to get it functioning. Id be glad to try to explain again if that could help? Ah, yes. Well, I returned to the forum about installing the voodoo kernel. I followed the process word for word. But it just doesnt seem to want to work. Right now I just flashed it again back to the rooted ed1. Would I be able to put CWM on there at that point?
Click to expand...
Click to collapse
Yes. But don't use rom manager. Use imnuts cwm recovery.
Sent from my SCH-I510 using Tapatalk
Alright, thanks. Ill try and use imnuts's cwm recovery. But if someone may answer a question, is the samsung bootloader unlocked?? My brother said thats something to know.
Jessman123 said:
Alright, thanks. Ill try and use imnuts's cwm recovery. But if someone may answer a question, is the samsung bootloader unlocked?? My brother said thats something to know.
Click to expand...
Click to collapse
Yes
Sent from my SCH-I510 using Tapatalk
so it is unlocked?? What does the exclamation triangle mean, when i try to do the update.zip from the samsung bootloader?
Oh and sorry if Im not getting this. Are you saying use a application that imnuts made? If so, could you be so nice to link it? Or a method he used? I looked for stuff but I didnt find anything other then what looks like a stock rom/kernel ed1 from him
I know how it is to be frustrated, but like they all said all of your questions have already been answered.
Here's my attempt to help:
Your problem lies in trying to flash CWR through ROM Manager, it currently doesn't play well with our phones. Word is that Koush (the creator) needs to update something for it to work with our phones. The bootloader is unlocked.
To flash imnuts' version of CWR, you'll need to use Samsung's leaked software called Odin - it's PC only. The alternative is Heimdall which is supposed to be cross-platform compatible, but the latest version is command-line only.
You have to find out if you've converted your system to EXT4 or if it's still RFS. That depends on if you have the Voodoo lagfix enabled or not. Check out the dev section and look for the titles that say [RECOVERY], [ODIN], [ROM], and/or something like "Get yourself to EE4 successfully".
A few links:
[HOW-TO] Get a rooted version of EE4
[RECOVERY][6-11-11]Clockwork Mod Recovery
[KERNEL][06-02-11] PeanutButta Jelly Time
Well, currently right now its rfs. Its the stock file system. What I was going to do, or did before, was to put it in download mode and flash the VoodooV4 Kernel. It roots the phone, and all that good stuff and is suppose to put the Voodoo recovery/cwm on there.
EDIT: Heres the proccess I followed before.
http://www.theandroidsoul.com/how-t...and-clockworkmod-recovery-installation-guide/
Jessman123 said:
Well, currently right now its rfs. Its the stock file system. What I was going to do, or did before, was to put it in download mode and flash the VoodooV4 Kernel. It roots the phone, and all that good stuff and is suppose to put the Voodoo recovery/cwm on there.
EDIT: Heres the proccess I followed before.
http://www.theandroidsoul.com/how-t...and-clockworkmod-recovery-installation-guide/
Click to expand...
Click to collapse
The recovery is a separate flash, both in odin. First the kernel, then Recovery.
Just follow here from the beginning, it should work for you:
http://forum.xda-developers.com/showthread.php?t=1122657
Well I have good news. I would like to announce that I have successfully installed CWM. I guess my phone just didnt like the other one or something. But following this link,
http://forum.xda-developers.com/showthread.php?t=1122657
I was able to get it installed. Now my only question is, I want this kernel http://forum.xda-developers.com/showthread.php?t=1092114 for my phone. But its not in a zip. Am I out of luck? Or do I not have to use CWM to install the kernel? Can I use odin and still be okay?
Jessman123 said:
Well I have good news. I would like to announce that I have successfully installed CWM. I guess my phone just didnt like the other one or something. But following this link,
http://forum.xda-developers.com/showthread.php?t=1122657
I was able to get it installed. Now my only question is, I want this kernel http://forum.xda-developers.com/showthread.php?t=1092114 for my phone. But its not in a zip. Am I out of luck? Or do I not have to use CWM to install the kernel? Can I use odin and still be okay?
Click to expand...
Click to collapse
You do need Odin to load that, but i'm wondering why you want to? Did you install the PBJ kernel following the instructions from the other link?
If you want to go down this route, be sure to apply the SD Card fix as well - you'll find posts about it.
Hey,
I'm trying to install the [ROM] Team Tiamat Xoom Rom 2.2.2 - Moray [9/10/11].
I've got CWM installed (version recovery-Tiamat-R4c-100611-1150-cwm.img but also tried latest version from ROM Manager).
Each time i try to install the .zip it get's to opening package and then just exits to the CWM menu?
It's probably a common thing, but couldn't find anything from a search? Anyone got any ideas?
This has been covered many times so take the time to do a search.
Muffycheeks said:
This has been covered many times so take the time to do a search.
Click to expand...
Click to collapse
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
kar200 said:
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
Click to expand...
Click to collapse
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
okantomi said:
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
Click to expand...
Click to collapse
I just ralised tnat my sd card was screwed (very old 1gb i found lying around). The files on the pc were fine.
I used a different card and now typing from a custom rom! All good.
K.
Sent from my Xoom using xda premium
Good day everyone.
I've run into a rather frustrating issue I haven't seen anyone solve, especially for this specific phone.
I'm running CM9-alpha5 right now, and I'm trying to flash one of the newer versions but I keep getting this "(status 7) installation aborted" no matter what ROM I attempt to flash now, even when I try to flash alpha-4 in which I was previously running.
I've made sure the permissions are set to read and write for everyone from within my computer(running pangolin ubuntu right now) and alas, the status remains 7.
Luckily I'm able to still re-flash alpha 5 and use my phone but... what gives?
Any help would be appreciated, thanks!
I feel I should clarify that I've been downloading these from get.cm like I have been, and transferring them directly to my sd card.
It feels like an odd permission screw-up, but I'm wondering if either that's not it or if there is any easier route to take than backing up and completely formatting my sd..
You didn't mention what recovery you're on, but I'd suggest trying a different one. There have been issues with some of the ROM Manager versions. We've had good success with:
http://forum.xda-developers.com/showpost.php?p=24085665&postcount=1
cschmitt said:
You didn't mention what recovery you're on, but I'd suggest trying a different one. There have been issues with some of the ROM Manager versions. We've had good success with:
http://forum.xda-developers.com/showpost.php?p=24085665&postcount=1
Click to expand...
Click to collapse
Thanks for the reply! I'm running CWM non-touch v.5.0.2.7 right now. The strangest thing is I came home, downloaded the 6-20 Nightly, and flashed it with success! so I guess the previous point is kind of null now, but I still feel I should update my CWM. Do you have any suggestions as to how I should go about updating from my old non-touch to the new touch? Thanks again for the reply!
barbrastreisand said:
Thanks for the reply! I'm running CWM non-touch v.5.0.2.7 right now. The strangest thing is I came home, downloaded the 6-20 Nightly, and flashed it with success! so I guess the previous point is kind of null now, but I still feel I should update my CWM. Do you have any suggestions as to how I should go about updating from my old non-touch to the new touch? Thanks again for the reply!
Click to expand...
Click to collapse
Sure, there are instructions in the post that I linked describing how to flash a recovery tar via ODIN.
cschmitt said:
Sure, there are instructions in the post that I linked describing how to flash a recovery tar via ODIN.
Click to expand...
Click to collapse
Installing on linux... not so fun. I said forget it and came to use my parents windows machine to just easily use ODIN real quick. I wasn't sure if I had to do any specific backups or anything before flashing but, nope, it was simple enough. Thanks again for your help!
Hi Guys,
My friend bricked his phone some how (he's using the htc one s on tmobile) and I myself am using the evo lte, thought i could be of some assistance, but I'm stuck as well...wonder if you guys could help me help him lol.
so I performed the tasks on post #8 from on how to "fix soft-brick" in the sticky, but being able to only access bootloader, and twrp recovery Im at a stall. While in recovery, i go the the options to mount, it won't mount my usb so that i can bring over a rom to flash in recovery. So my problem is that the phone won't mount to my computer so i can bring over a rom i downloaded on my computer to the phone.
if i reboot system it sticks at the htc develop splash page.
Im pretty stuck and hope u guys can me help my boy.
P.S. i told him next time when you flash, always make a backup....cuz he was trying to flash a jelly bean wip (i don't even think it was a rom for his phone).
Thanks in advance guys!
bump, anyone kind to help me out with this?
Thanks again, hope to help him out, but Im at my wits end because i keep on getting running into the same problem.
jdizzle316 said:
bump, anyone kind to help me out with this?
Thanks again, hope to help him out, but Im at my wits end because i keep on getting running into the same problem.
Click to expand...
Click to collapse
You're going to either need to push a rom to his phone using ADB, or perhaps flash an RUU using Fastboot. Are you familiar with either process? There may be other options, but I'm familiar with both of these scenarios and can at least point you in a direction. Lemme know!
Yeah ADB push is your best option right now. IIRC USB mount in recovery does not work due to kernel limitation. (I could be wrong but remember reading about it)
Look here
http://forum.xda-developers.com/showthread.php?t=1667929
baseballfanz said:
Yeah ADB push is your best option right now. IIRC USB mount in recovery does not work due to kernel limitation. (I could be wrong but remember reading about it)
Look here
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
I agree with him, I kinda had the same problem your friend had and adb pushing a Rom is probably your best option right now...
Sent from HTC one s
Thank you very much guys, I am not too familiar with pushing thru adb but have been reading up on it through the development section and am ready to dive in.
I very much appreciate the input fellas, will keep you updated with the status of this so that others in this situation can benefit from this as well.
Thanks again!
jdizzle316 said:
Thank you very much guys, I am not too familiar with pushing thru adb but have been reading up on it through the development section and am ready to dive in.
I very much appreciate the input fellas, will keep you updated with the status of this so that others in this situation can benefit from this as well.
Thanks again!
Click to expand...
Click to collapse
If you need help along the way, just ask we are all here to help each other to get ones problem solved and learn from it
Sent from HTC one s
Ok guys, heres the update as promised. Mission to restore was success!
First, I tried to push thru adb, but it would never stick, would always get hung up. Given, being my first time pushing thru adb i probably did it incorrectly. In fact, I managed to push the rom over to the sd card once, but was unable to flash it from recovery (CWM).
Here is how i fixed the problem of being bricked. I relocked the bootloader, using the "all in one kit" and then i downloaded the TMOUS RUU, booted the phone into bootloader and then ran the ruu's exe. Within 10 minutes it was back to bone stock.
I hope this helps fix others with the same problems, if you guys need any help, feel free to hit me up.
Thanks guys for the suggestions and pointing me in the right direction...I couldn't have done it without your help!
jdizzle316 said:
Ok guys, heres the update as promised. Mission to restore was success!
First, I tried to push thru adb, but it would never stick, would always get hung up. Given, being my first time pushing thru adb i probably did it incorrectly. In fact, I managed to push the rom over to the sd card once, but was unable to flash it from recovery (CWM).
Here is how i fixed the problem of being bricked. I relocked the bootloader, using the "all in one kit" and then i downloaded the TMOUS RUU, booted the phone into bootloader and then ran the ruu's exe. Within 10 minutes it was back to bone stock.
I hope this helps fix others with the same problems, if you guys need any help, feel free to hit me up.
Thanks guys for the suggestions and pointing me in the right direction...I couldn't have done it without your help!
Click to expand...
Click to collapse
Congrats on getting it restored hopefully you do a backup of it so this won't happen again
Sent from HTC one s
Thanks! I'll definitely advise my friend to do so, or I may for him lol.
Again, couldn't have done it without everyones help
Sent from my EVO using xda app-developers app
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"