• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

am i rooted??

no...i was leary about doing cause i didn't want to erase all my stuff, so i tried entering in some of the root commands to see if anything was missed. when this didn't work i went for the ruu. it looked the zipped rom file in the ruu was messed up. is that link safe on our forum?
 
I understand, but this is what I'm telling you...Try downloading it again as sometimes you just get a bad download. No real explanation.

Otherwise, if you are still able to boot into recovery somehow, you could try restoring a nandroid backup (pending you made one of course). In the root guide here, there are instructions for how to boot into recovery without command prompt.
 
Again, have you tried re-downloading it and trying again? And yes I mean from the same place. If that doesn't work, you could try the 1.29 version instead. Furthermore, i don't think you read what I put above stating that you can get into recovery without cmd prompt. It is in the guide.

ccapasso said:
17.How do I boot into Recover Mode from Power Off?
a.

1) Pull Battery (If necessary and stuck in a loop)
2) Press and hold the "Home" button
3) Continue holding "Home" while pressing and releasing the "Power" button

You didn't receive an error code or anything correct? have you even tried pulling the battery?
 
yes, i've pulled the battery, it keeps taking me to ruu, and now that site won't let me download anymore................seriously, this effen sucks. no error code nothing, it just said some files are missing from the stock rom download.
 
Did you try the above and pull the battery, press home, etc?

have you tried the older RUU version as suggested?
 
Please take your time and read thoroughly. There are 2 different RUU's there:

RUU_Hero_C_Sprint_1.29.651.1

RUU_Hero_C_Sprint_1.56.651.2

Furthermore, if you will kindly take a deep breath and read all that is being suggested to you, try the different things and then respond, it would be appreciated. You are jumping around, and I understand you are in panic mood. If your phone is bricked, you have several options. One is to do what I suggested above and read that link. People having problems with RUU have done it and been successful. Other than that, if you have insurance with Sprint, you could take it to them and see what happens. Or you might have to buy a new one.
 
OK...sorry, its just that i saved up a lot to get this phone. i was/am freaking out because i don't want to ruin it. i don't have the ability to replace it. ok, so the 'brick workaround' did work. which is good, cause i can use my phone...and i'm going to be doing a lot of driving today so ICE it is a necessity. next thing is, i received error 110 (see the read me file of the download) that files are missing or corrupt both times i downloaded the RUU. i downloaded it AGAIN to try it later, and i'm downloading the earlier version. i don't know if my phone is in fact, BRICKED, because the read me knew of this error. but, i definitely can't fix it unless i get a solid version of the RUU. is there any reason why this is so unstable? in your opinion, do you think my phone is officially bricked, or just messed up from an incomplete RUU install. if so - do we have a more reliable one, or do i keep having to chance it on this one?

i apologize for freaking out on these forums. but this is really stressful to me.

thanks in advance.
 
i also wanted to add, after googling my error, it appears a few people have had this same problem in the last few weeks from that same site. there may be something wrong with that download. in which case, i'm really bummed now, and it should be taken down immediately as to prevent anyone else trying to go back to RUU from screwing up their phones.
 
The work 110 error fix worked? Good news :0

From what I've been reading, it has been suggested that you hold off doing anything more for now once it is working, as there is a chance, and I say it lightly, that when sprint Releases the new 2.1 software that there will be a radio update that may, and again this is only a maybe, fix the issue.
 
no, the 110 error didn't work...the fastboot did. so i can use my phone, but i can't turn it off unless there's a computer around. that link should be removed. the RUU is corrupted. i'm working on finding a solution now, on another forum. if i do i will post it and maybe it can get a sticky, cause this is an issue...having something that is corrupted on a help forum. just saying...it may have worked at one point, but it sure isn't working now.
 
While I understand your frustration, the link will not be removed yet from what I have posted as the guide. Not because I want people to mess their phones up or because I don't I don't care.

I have seen few and far between with issues. Some have problems, others do not. If it is removed from the source, then I will look more into it. For now, I don't see the need to remove something that could help others.

As always, each and every person is responsible for what they do to their phones.
 
nah, that's now what i'm saying...your guide is great, its the RUU thing that is messed. is there no way to remove just that link? i'm just trying to save anyone from what i've gone through today - even with your help...thank you
 
I don't know if the RUU itself is corrupted, unless it's changed since it was first put up. I've used the 1.56 multiple times, and it worked just fine. I haven't tried it since doing the radio updates in the past month, but I'm sure it'd still work just fine.

What I wonder is if the people using the auto-rooter from the kitchen are the ones having the problems. Perhaps the way the kitchen roots the phone is causing the RUU to not work with their phones? Just a thought (that's probably wrong).
 
There is nothing wrong with ruu, I have used it. There is nothing wrong with the auto root on kitchen, I used it 4 times on Saturday on 4 different phones successfully. I flashed all 4 to fresh 2.0d. Not to be a DI#K but sounds like user error.
 
Geeez! you still having issues? lol

alright what's going on? fill me in..I don't want to read everything...
 
Geeez! you still having issues? lol

alright what's going on? fill me in..I don't want to read everything...


Lol..There isn't much to read, and it is better then him or anyone repeating it all over again.

Long story short, he still couldn't get the apps to remove. I walked him through doing it manually, still no luck. No luck with either kitchen version. He decided to RUU and re-root manually. RUU failed and now his phone is semi-bricked. I have sent him several links on limited work arounds...
 
I used the auto rooter today, had my phone rooted and flashed in about 5 minutes. Never had any probs at all. I cooked a rom and it is flawless. Now I'm downloading fresh 2.0d, any thing special to do or just wipe and flash?
 
There is nothing wrong with ruu, I have used it. There is nothing wrong with the auto root on kitchen, I used it 4 times on Saturday on 4 different phones successfully. I flashed all 4 to fresh 2.0d. Not to be a DI#K but sounds like user error.

look, i don't know what i'm doing sure...but i followed everything right doing the RUU...and it bricked my phone. error 110. look it up, there's a lot of people having trouble with it. when did you last download RUU and use it?
 
Back
Top Bottom