I am still on 6.14.75 and waiting for positive solutions before I jump.
I have successfully return to ICS 6.14.75
Posted 28 April 2012 - 10:33 AM
I have successfully return to ICS 6.14.75
Posted 28 April 2012 - 10:37 AM
I have successfully return to ICS 6.14.75
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!
Posted 28 April 2012 - 10:38 AM
Don't jumpWhat 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.
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!
Posted 28 April 2012 - 10:40 AM
Posted 28 April 2012 - 10:41 AM
Don't jump
Posted 28 April 2012 - 10:53 AM
Posted 28 April 2012 - 10:56 AM
Posted 28 April 2012 - 10:57 AM
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
Posted 28 April 2012 - 11:11 AM
Posted 28 April 2012 - 11:11 AM
How?I have successfully return to ICS 6.14.75
Posted 28 April 2012 - 11:15 AM
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.
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.
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.
Posted 28 April 2012 - 11:42 AM
Posted 28 April 2012 - 11:45 AM
Yes I was. I'll try matt's util to flash back to 173
Posted 28 April 2012 - 11:50 AM
Posted 28 April 2012 - 11:51 AM
Posted 28 April 2012 - 11:51 AM
Add this guy to the brick list
0 members, 8 guests, 0 anonymous users