Jump to content


Photo

New Ics Build 6.14.84.xt912


  • Please log in to reply
984 replies to this topic

#381 kbuck13

kbuck13

    Member

  • Members
  • PipPip
  • 105 posts

Posted 28 April 2012 - 10:33 AM

What steps have you taken? both the up and down grade?

I am still on 6.14.75 and waiting for positive solutions before I jump.

I have successfully return to ICS 6.14.75



#382 tucstwo

tucstwo

    www.drdevs.com

  • Administrator
  • 14,435 posts
  • Twitter:tucstwo
  • Google+:tucstwo@gmail.com
  • LocationNJ
  • Current Device(s):LG G3 VS985, Nexus 7 (flo)

Posted 28 April 2012 - 10:37 AM

I have successfully return to ICS 6.14.75


How?

Visit DRDevs.com hosting site for all official Droidrzr.com ROMs, Apps, GApps and other mods/files!!
Please PM me if you need help!
I will be hosting AOSP-Based ROM GApps packages!
Download the most Up-to-Date GApps Packages for AOSP ROMs from me here!


#383 tucstwo

tucstwo

    www.drdevs.com

  • Administrator
  • 14,435 posts
  • Twitter:tucstwo
  • Google+:tucstwo@gmail.com
  • LocationNJ
  • Current Device(s):LG G3 VS985, Nexus 7 (flo)

Posted 28 April 2012 - 10:38 AM

What steps have you taken? both the up and down grade?

I am still on 6.14.75 and waiting for positive solutions before I jump.

Don't jump

Visit DRDevs.com hosting site for all official Droidrzr.com ROMs, Apps, GApps and other mods/files!!
Please PM me if you need help!
I will be hosting AOSP-Based ROM GApps packages!
Download the most Up-to-Date GApps Packages for AOSP ROMs from me here!


#384 robthefive0

robthefive0

    Sarge

  • Members
  • PipPipPip
  • 315 posts
  • LocationN.J.

Posted 28 April 2012 - 10:40 AM

Well, I finally had the balls to do this yesterday before all the hoopla started. Luckily, everything is working awesome. Guess I am stuck with it until either

A: A fix is found. Which I am sure will happen, it's only been 1 day.

B: I break my phone and get an insurance replacement

C: Upgrade date arrives.

Such is life. But, I am loving this leak so far. If I am stuck, I am stuck.
Posted Image

#385 kbuck13

kbuck13

    Member

  • Members
  • PipPip
  • 105 posts

Posted 28 April 2012 - 10:41 AM

Don't jump


generally wait a few days and read everything I can before I do anything as it saves me a lot of head aches.
  • SnoDrtRider likes this

#386 insomniasleepzzz

insomniasleepzzz

    n00b

  • Members
  • Pip
  • 7 posts

Posted 28 April 2012 - 10:53 AM

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.
  • JNagy and tucstwo like this

#387 DonDraper

DonDraper

    Member

  • Members
  • PipPip
  • 156 posts
  • LocationLexington, SC

Posted 28 April 2012 - 10:56 AM

(sings) The FAIL boat.... SOON we'll be mak-ing another thread!!!!!

-50 points to those that supposedly tested. And please top talking about how wrong it is to release leaks. That's the WHOLE F'ING REASON forums like this exist. IF you feel that way then go buy an iPhone and get on with your boring ways.
  • DarkOverDroid and tucstwo like this

#388 insomniasleepzzz

insomniasleepzzz

    n00b

  • Members
  • Pip
  • 7 posts

Posted 28 April 2012 - 10:57 AM

And before a butthurt being emerges saying they pulled the files and blah blah blah, no honey. I mean something BIG to warn people from going anywhere else to obtain it. A whole seperate thread. So if you're gonna be the immature type that just wants to prove a point, don't, I simply expressed my personal feelings in a forum. This needs to be treated as the problem it is.

#389 b419kid

b419kid

    Member

  • Members
  • PipPip
  • 103 posts

Posted 28 April 2012 - 11:02 AM

If you are asking this... you shouldn't flash this leak. People are bricking because odds are you CANT fast boot back if something goes wrong. I personally haven't tried and won't be flashing anymore mods themes or anything until... well who knows lol. Although I will say DTs script works great and so does the deblur debloat mod. But again... if you forget to wipe you may end up sh**img bricks

Sent from my DROID RAZR using Tapatalk 2 Beta-6


Well, I have restored previously through Matt's utility. It comes with flashboot files packaged in. I just was wondering how to obtain them manually for RSD Lite~~ because the guide warns against using Matt's utility. But you are probably right, I need to learn more about it before attempting.

#390 weedahoe

weedahoe

    n00b

  • Members
  • Pip
  • 6 posts

Posted 28 April 2012 - 11:11 AM

Works fine on my device and I have root afterwards.

Am I concerned I cant/wont be able to change later? NO. Not at all because Ive never seen a leak that didnt eventually get a work around to downgrade and then go back forward to a higher revised version.

So I think to all the guys saying DONT do it because you will be screwed later is inaccurate and over exaggerated
  • robthefive0 likes this

#391 knghts50

knghts50

    Member

  • Dedicated Supporter
  • PipPip
  • 199 posts
  • Google+:kevin.page3
  • LocationCopperas Cove, TX (Fort Hood)

Posted 28 April 2012 - 11:11 AM

I have successfully return to ICS 6.14.75

How?
Posted Image

#392 ssmaynv

ssmaynv

    Member

  • Members
  • PipPip
  • 243 posts
  • LocationLas Vegas

Posted 28 April 2012 - 11:15 AM

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.

#393 JungleKing76

JungleKing76

    Droid Master

  • Members
  • PipPipPip
  • 446 posts

Posted 28 April 2012 - 11:20 AM

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

#394 Guest_DirtyDroidX_*

Guest_DirtyDroidX_*
  • Guests

Posted 28 April 2012 - 11:27 AM

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.

#395 AsosaYoung

AsosaYoung

    Member

  • Members
  • PipPip
  • 146 posts
  • Twitter:OGissimO
  • LocationLong Beach, Ca

Posted 28 April 2012 - 11:34 AM

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

#396 ssmaynv

ssmaynv

    Member

  • Members
  • PipPip
  • 243 posts
  • LocationLas Vegas

Posted 28 April 2012 - 11:42 AM

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

#397 BigDaddyGriz

BigDaddyGriz

    Member

  • Members
  • PipPip
  • 26 posts
  • LocationNorth Western Arkansas
  • Current Device(s):Droid Maxx(rooted) / Nexus 7(12) Stock / Droid Razr M (rooted/unlocked)

Posted 28 April 2012 - 11:45 AM

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


You are a brave man.

#398 STiK

STiK

    STiK in the Mud

  • Members
  • PipPipPip
  • 304 posts
  • LocationEverett, WA
  • Current Device(s):LG Nexus 4

Posted 28 April 2012 - 11:50 AM

Add this guy to the brick list
  • tucstwo likes this

#399 ssmaynv

ssmaynv

    Member

  • Members
  • PipPip
  • 243 posts
  • LocationLas Vegas

Posted 28 April 2012 - 11:51 AM

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.

#400 _base2

_base2

    Droid Master

  • Members
  • PipPipPip
  • 810 posts

Posted 28 April 2012 - 11:51 AM

Add this guy to the brick list


^^ this lol

[ 43V3R IC3 ]
  • Baby Duck likes this
[ sent from _base2 ]




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users