21 replies to this topic

[smith3jk]

I'm pretty familiar with flashing and everything invlovled. I've been flashing roms for a while now. Anyway, I tried flashing the .744 through RSD because I wanted to take on the ICS leak. I'm stuck at "Step 12/18 Flashing: system.img" ....it's been on this step for at least 30 minutes now. I've used RSD before and never had a problem. I have all drivers up to date as well. I think it may be bricked? Anything I can do? Or should I see if big red can send me a new one?

[wyld]

Try Matts Utility 1.51 that will take you to full stock .173 so you can go to the ICS leak. I'll update with link in a minute.

Edit:

Please Login or Register to see this Hidden Content

[Windows]-*new-Thread*

Rooted Droid Razr ICS Leak

[smith3jk]

I tried that and it gets stuck on one of the steps.

[jami2976]

I tried that and it gets stuck on one of the steps.

Do you have moto helper installed? just wondering because i was having trouble with RSD lite as well and after uninstalling it and downloading an older driver it worked great...and dont send that phone into big red....

[smith3jk]

I have to send it back to big red otherwise I'm out of a phone. I think it was able to clear data and cache in the RSD process.

[Thach]

Do you have moto helper installed? just wondering because i was having trouble with RSD lite as well and after uninstalling it and downloading an older driver it worked great...and dont send that phone into big red....

I agree on not sending the phone in. Bricking is a risk you take by rooting and flashing no matter how experienced you are in this.

Sent from my DROID RAZR using Xparent Red Tapatalk 2

[smith3jk]

I understand it's a risk and I understand and take full responsibility for what happened. Unfortunately I'm a full time student and working part time and I don't have the budget to buy a new one like some people on here. I don't plan on messing with this one. I've paid a lot of money to big red over the years just like all of us here.

[superrelaxx]

I understand it's a risk and I understand and take full responsibility for what happened. Unfortunately I'm a full time student and working part time and I don't have the budget to buy a new one like some people on here. I don't plan on messing with this one. I've paid a lot of money to big red over the years just like all of us here.

You're not taking responsibility. You broke it, fix it. It's not that hard to get stock back on your phone.

Sent from my DROID RAZR using Tapatalk 2 Beta-5

[smith3jk]

I don't know why you guys are getting so angry over this. I'm not a noob, I know what I'm doing. The RSD program (which even VERIZON uses) got stuck and damaged the phone. The phone is under warranty. It's not like I didn't read through these forums for a whole day trying to find a way to fix it. I literally tried everything and so I've come to the conclusion that it is just damaged now. I talked to tech support and they agree. I appreciate the help, I really do. But there's nothing left from here.

[_base2]

Makes sense to me. You take full responsibility for rooting and hacking your phone and voiding your warranty. Unless of course you mess it up. In which case you'd have to actually pay for your mistake.

Risk is present regardless of outcome. You took a risk by rooting and voiding your phone's warranty. When that risk turned out adversely, you didnt want to accept the outcome.

That's the great thing about risk. You can't un-accept it.

What's done is done. Consider this a lesson in risk and outcome. Makes you think twice about the value of birth control, doesn't it ... ?

Sent from my DROID RAZR using Tapatalk 2

[Thach]

Makes sense to me. You take full responsibility for rooting and hacking your phone and voiding your warranty. Unless of course you mess it up. In which case you'd have to actually pay for your mistake.

Risk is present regardless of outcome. You took a risk by rooting and voiding your phone's warranty. When that risk turned out adversely, you didnt want to accept the outcome.

That's the great thing about risk. You can't un-accept it.

What's done is done. Consider this a lesson in risk and outcome. Makes you think twice about the value of birth control, doesn't it ... ?

Sent from my DROID RAZR using Tapatalk 2

Wait a dang second!!! What is this birth control that you speak of? It could have helped me out 2 kids ago lmao j/k I love my boys.

[smith3jk]

So here's what's going to happen. Verizon will get the phone back, fix it, and use it as a refurbished phone that they then send out to people. Do you work for Verizon? Am I the only one who has ever done this? No. And is Verizon and Motorola screwing us over when it comes to pricing/cost? Yes. The irony behind this is that it was damaged trying to load a STOCK image. Not flashing a ROM, not rooting it. It's the system, people take advantage of it all the time and that's why we pay out of our ass for new phones now. We can't stop it either. This discussion has gone very off topic and I appreciate the help.

EDIT: And I do take this as a lesson and will not mess with the new one.

[24v]

The discussion has gone off topic because you are committing fraud. You chose to modify your phone, and got it to a point where you do not have the knowledge to fix it. So now because you do not have the patience to fix it correctly you are going to commit insurance fraud because it is convenient to you to do so.
The point of insurance is to cover your ass should you accidentally break or lose your phone. It is not so that you can get in over your head flashing roms, and then take the easy way out.
And, you are very right, others have done it as well. Does that make it right? Other people rob liquor stores and steal from people, should you go give that a shot as well?
If you see nothing wrong with what you are doing then call Asurion or Verizon, whoever is covering the phone, and tell they you were flashing custom roms and got your phone stuck. See if they are then so willing to give you another.

[superrelaxx]

The discussion has gone off topic because you are committing fraud. You chose to modify your phone, and got it to a point where you do not have the knowledge to fix it. So now because you do not have the patience to fix it correctly you are going to commit insurance fraud because it is convenient to you to do so.
The point of insurance is to cover your ass should you accidentally break or lose your phone. It is not so that you can get in over your head flashing roms, and then take the easy way out.
And, you are very right, others have done it as well. Does that make it right? Other people rob liquor stores and steal from people, should you go give that a shot as well?
If you see nothing wrong with what you are doing then call Asurion or Verizon, whoever is covering the phone, and tell they you were flashing custom roms and got your phone stuck. See if they are then so willing to give you another.

+1

[coletrane09]

+1

lol

Sent from stock rooted ICS Razr

[superrelaxx]

lol

Sent from stock rooted ICS Razr

+1

[STiK]

I know this may be slightly irrelevant but why do people continue to fastboot back to .744? I know it works but why not fastboot to .173? Just seems to add unneeded steps to the recovery process.

[Gerland the Oracle]

i know i go back that far because iam unable too locate a good dwnlod for .173, HINT HINT!!!

[wyld]

i know i go back that far because iam unable too locate a good dwnlod for .173, HINT HINT!!!

Matts Utility 1.51 lol

Rooted Droid Razr ICS Leak

[BigDaddyHicks]

I know this may be slightly irrelevant but why do people continue to fastboot back to .744? I know it works but why not fastboot to .173? Just seems to add unneeded steps to the recovery process.

I do it to make sure I haven't done anything that would cause me to be thrown off the update path.

Sent from my DROID RAZR using Tapatalk 2

[coletrane09]

Matts Utility 1.51 lol

Rooted Droid Razr ICS Leak

only way to go....think I'm on the leak for the 3rd time used utility each time

Sent from stock rooted ICS Razr

[PillClinton]

I know this may be slightly irrelevant but why do people continue to fastboot back to .744? I know it works but why not fastboot to .173? Just seems to add unneeded steps to the recovery process.

Personally, the only reason I would restore to .744 is to make sure nothing gets wiped (and because I already have those files downloaded). The .173 fastboot files wipe your internal memory, and most recently when I was caught in a bootloop, I didn't have a way to backup/retrieve any of those files. After restoring to .744 once I backed up my files, I used the .173 files to speed up the upgrade process.

If you don't have anything you care about if it gets lost/wiped, or if you already have your files backed up, just use the .173 fastboot files and save yourself a ton of time!