984 replies to this topic

[knghts50]

I have successfully return to ICS 6.14.75

How?

[ssmaynv]

This is what I did. I know you will read it and say to yourself, "well that just sounds dumb", I know this because it's what I thought.

1. Protect root with voodoo
2. Reboot into ICS Bootstrap
3. Factory reset
4. Wipe Dalvik
5. Advanced Restore Nandroid - SYSTEM ONLY
6. Wait for it to fail because I protected Root with voodoo
7. After fail, check log to verify it failed at su-backup
8. Factory Reset
9. Wipe Dalvik
10. Reboot
11. Skip initial setup
12. Verify root, and I'm still rooted (Yay)
13. Verify system settings
14. Create accounts, sync, load apps as normal.

I really hope this works for you too because I'm surprised it worked for me.

[JungleKing76]

This is what I did. I know you will read it and say to yourself, "well that just sounds dumb", I know this because it's what I thought.

1. Protect root with voodoo
2. Reboot into ICS Bootstrap
3. Factory reset
4. Wipe Dalvik
5. Advanced Restore Nandroid - SYSTEM ONLY
6. Wait for it to fail because I protected Root with voodoo
7. After fail, check log to verify it failed at su-backup
8. Factory Reset
9. Wipe Dalvik
10. Reboot
11. Skip initial setup
12. Verify root, and I'm still rooted (Yay)
13. Verify system settings
14. Create accounts, sync, load apps as normal.

I really hope this works for you too because I'm surprised it worked for me.

You may have successfully gone back to 75 but whatever is causing users to fail in rsd likely is still there in your phone and I suspect you will be stuck as well.

Sent from my DROID RAZR using Xparent Purple Tapatalk

[DirtyDroidX]

Ok, here is my take on this whole situation. I'm a regular dude. Not a nerd, but not dumb. I mess with electronics because I find it fun. I've flashed firmware on mad stuff with no problems at all, from 360 to psp's, the list is endless. So like I said, nothing special, but not retarded. I take full responsibility for flashing this, that being said. I lost such a huge amount of faith in this site, I don't even know what to think. Allow me to explain in a non disrespectful objective manner. I am new here. I don't interact much because I am a loner in real life and that translates to the internet oddly enough. I have flashed every single rom on this site and have donated to the three devs that produced something I would actually purchase in real life. So I am not a leech and I support hard work. Being a contributing member to the community I would like to think that there is that unspoken understanding. Everyone makes mistakes, heck I do all the time. However, I fully read the warning. Though I am bringing my phone back to verizon anyway, these guys are really slow here so, sorry? Point being is there was nothing, and still nothing listed about this error. I even laughed when I read this was an isolated incident on certain phones? It seems to me this is a huge widespread problem, though I won't argue symantecs. I tried to fastboot back well before people started posting and now my phone is, even with that "fix". At the point where a bunch of people as in almost everybody started complaining there should have been some huge warning posted. Was this planned? I just don't see why there is nothing extra being posted about this HUGE problem. I would feel more comfortable knowing that some of the devs I gave money too are working to rectify this, rather then reading an all caps rant about feeling tortured over a bunch of kids not appreciating something you didn't do. Say what you want but this is all fact. I have to assume this was planned if there is no warning posted about this still. I feel very betrayed, I feel worse for the people that can't do anything because their local verizon workers are too smart. From here on out I will be strictly leeching from this site until I am either assured that there was someone working damn hard to fix this, or some BIG warning gets posted against this. You lost the trust of a solid guy, just had to say it.

Wow the internet police are here. Your threatening words makes everyone, want to work hard just to make sure your demands are met.

[AsosaYoung]

This is what I did. I know you will read it and say to yourself, "well that just sounds dumb", I know this because it's what I thought.

1. Protect root with voodoo
2. Reboot into ICS Bootstrap
3. Factory reset
4. Wipe Dalvik
5. Advanced Restore Nandroid - SYSTEM ONLY
6. Wait for it to fail because I protected Root with voodoo
7. After fail, check log to verify it failed at su-backup
8. Factory Reset
9. Wipe Dalvik
10. Reboot
11. Skip initial setup
12. Verify root, and I'm still rooted (Yay)
13. Verify system settings
14. Create accounts, sync, load apps as normal.

I really hope this works for you too because I'm surprised it worked for me.

Were you on .84???

Sent from my DROID RAZR using Tapatalk 2

[ssmaynv]

Yes I was. I'll try matt's util to flash back to 173

[BigDaddyGriz]

Yes I was. I'll try matt's util to flash back to 173

You are a brave man.

[STiK]

Add this guy to the brick list

[ssmaynv]

Well, Matt's applications have always been rock solid for me. I will ask this before I try it though, is there some sort of indicator that it might fail? such as a file or partition structure?

I mean from what's been learned so far.

[_base2]

Add this guy to the brick list

^^ this lol

[ 43V3R IC3 ]

[trekie4ever]

I hope you didn't already try. The system flashed back to. 75 bt the boot loader which is probably the problem won't and you will be stuck with a brick like everyone else...


WHY ARE PEOPLE FASTBOOTING IF THE LEAK LOADED JUST FINE FOR THEM?!?

Sent from my DROID RAZR using Tapatalk 2 Beta-6

[_base2]

Well, Matt's applications have always been rock solid for me. I will ask this before I try it though, is there some sort of indicator that it might fail? such as a file or partition structure?

I don't think anyone knows yet... hence the risk

[ 43V3R IC3 ]

[fbm111]

I wouldn't try matts back to 173. I did and I am bricked. If any reputable dev that is trying to fix this wants me phone pm me. I will send you my phone to tinker with. Nothing I can do with it now.

No I won't send back to Verizon wasn't there fault was mine.



Sent from my ADR6300 using Tapatalk 2

[ssmaynv]

If it brick's then it brick's. It's no big deal to replace a phone.

edit: I see the post about it being the bootloader...I understood this to be a different problem, more with the "system" partition.

So a moment of pause is given..

[fbm111]

Nothing bad towards Matt or anyone. I love you guys and appriciate all your work

Sent from my ADR6300 using Tapatalk 2

[KMANN04]

I'm on the brick list myself. I loaded the new ICS leak and lost root so I decided to start over and I used Matt's utility to do it.
Long story short, Is there anyway to get my phone to boot up on anything? I don't care what it is I just need a working phone.

[ssmaynv]

My bootloader version is 0a74, can anyone see if that's the same on .85? I never checked before restoring my nandroid.

The system version, build number and build date are as they should be with .74.

[TwoBuells]

Life goes on. add me to the Brick list.
I flashed this on my own.
I eff'd up on my own, no one to blame but me.
Just got home with a new Razr MAXX. Best Buy $237 OTD

Hey does any of the Dev's want a computer screen shoot of the failed files while using Matt's Utility?
I did try RSD also but failed on step 6.
Phone boots with moto logo, then black screen. It does do that vibrate thing after about a min.

[_base2]

WHY ARE PEOPLE FASTBOOTING IF THE LEAK LOADED JUST FINE FOR THEM?!?

Sent from my DROID RAZR using Tapatalk 2 Beta-6

The question of the day...

I'm completely satisfied with 84. Runs great for me. In fact, today has been quite therapeutic for me. In not allowing me to fastboot back, I actually have to learn to be satisfied with what I've already got. And thankfully, I found that very easy. lol

[ 43V3R IC3'd on .84 ]

[jpcalhoun]

Well, Matt's applications have always been rock solid for me. I will ask this before I try it though, is there some sort of indicator that it might fail? such as a file or partition structure?

I mean from what's been learned so far.

Yeah, Matt bricked his phone using the utility...does that count?

[STiK]

Fastboot fails at flashing cdt.bin. Restoring the .75 system nandroid is not going to prevent fastboot failure. When you use RSDlite to fastboot, it will fail and stop at cdt.bin therefore you can restore the previously flashed files. Using the utility, it will fail at cdt.bin and continue on flashing other $#!+. Some may fail and some may succed but you will have all sorts of whack things flashed on your device. If you are on .84 or .85 you should under no circumstances fastboot back. With that said, have fun flashing that $#!+

[ssmaynv]

Yeah, Matt bricked his phone using the utility...does that count?

LOL, I saw that in chat earlier. I was just hoping that something significant had changed when I restored my nandroid.

[KMANN04]

I'm not blaming anyone but myself. Matt has done nothing but make things easier for people. I was just letting the devs know what I did to brick and hopping they might have a solution.

I appreciate everything all the devs do for us..Sh*t happens and I'm sure they will figure out a fix.

[benefit14snake]

By the way, leak is preeetttyy sweet once debloated and frozen. I am enjoying it very much!

Sent from my Axiom MAXX!!

[_base2]

Yeah, Matt bricked his phone using the utility...does that count?

I'd say that's what we call a STRONG indicator.

I'm down with 84 and all but all this locked bootloader bull$#!+ is getting old. Not really bc I'm worried about getting back on the path TODAY (because I'm confident that it'll happen soon) but bc this shouldn't even be an issue to begin with.

We need open source to ACTUALLY BE OPEN. Motorola is the devil. At least their security sucks so I still has rootz!

[ 43V3R IC3'd on .84 ]

[jpcalhoun]

LOL, I saw that in chat earlier. I was just hoping that something significant had changed when I restored my nandroid.

Don't get me wrong...I'm not blaming anyone for the situation we are in on .84. Those Devs work hard to give us the ROMs/themes and fixes. Matt's Utility has been one of the greatest tools for inexperienced users...EVER. Someone made a mistake (and it wasn't Matt by the way), so forgive and forget. Lets hope that the fastboot files for ICS get released or leaked soon and we can all go on with our lives.

[TwoBuells]

The question of the day...

I'm completely satisfied with 84. Runs great for me. In fact, today has been quite therapeutic for me. In not allowing me to fastboot back, I actually have to learn to be satisfied with what I've already got. And thankfully, I found that very easy. lol

[ 43V3R IC3'd on .84 ]

everything was running fine with the 84 leak, but my Webtop app was going nuts.
I first tried a nandroid backup of the old leak w/DT's modifier but I bootlooped, tried Matt's Util and RSD and it all went south.........

[_base2]

everything was running fine with the 84 leak, but my Webtop app was going nuts.
I first tried a nandroid backup of the old leak w/DT's modifier but I bootlooped, tried Matt's Util and RSD and it all went south.........

Damn... I've never used webtop so j wouldn't know. What exactly happened? Did you not try a data wipe first to get out of the bootloop?

[ 43V3R IC3'd on .84 ]

[jpcalhoun]

everything was running fine with the 84 leak, but my Webtop app was going nuts.
I first tried a nandroid backup of the old leak w/DT's modifier but I bootlooped, tried Matt's Util and RSD and it all went south.........

I guess it's a little to late to tell you to not use RSD or the Utility to get back to some other build...sorry to hear you're bricked.

[ddfuji]

How would you know it's a crap because if you flash it you can't flash back to gingerbread??? Just asking.

Sent from my DROID RAZR using Tapatalk 2

i did with the first leak. if its not true for the second leak then nevermind