![]() |
![]() |
Posted 30 April 2012 - 09:13 AM
Posted 30 April 2012 - 09:32 AM
Posted 30 April 2012 - 09:35 AM
Posted 30 April 2012 - 09:43 AM
could this help?
Posted 30 April 2012 - 09:46 AM
Posted 30 April 2012 - 09:51 AM
Whoa!!! What do we have here???
Posted 30 April 2012 - 09:52 AM
a fastboot file for a DEVELOPER edition of the droid razr =)Whoa!!! What do we have here???
Posted 30 April 2012 - 09:53 AM
It's for the dev edition. We may be able to use parts of it if it has the same bootloader version. (The thought being that perhaps the bootloader is the same version, but instead unlocked ... but I do not know this. It is merely a guess)
[ 43V3R IC3'd on .84 ] supposer it is the same but unlocked. Does that pose a possible bootloader unlocl solution =P
Posted 30 April 2012 - 10:04 AM
Posted 30 April 2012 - 10:10 AM
Posted 30 April 2012 - 10:32 AM
Posted 30 April 2012 - 10:35 AM
Posted 30 April 2012 - 10:38 AM
Ok, just got back on here and noticed what is going on. If I'm on .84 and everything is running smoothly with root should I be worried? I have no want or need to go back to GB now that this build is working so nicely for me. Thoughts? Advice?
Posted 30 April 2012 - 10:46 AM
Don't do anything that would cause you to bootloop and i think you will be ok. I'm on .84 from day one with no problems. Just don't hold me to that cause I'm not a dev or anything and really not sure.
If it's not broke try harder.
Posted 30 April 2012 - 10:46 AM
+1 on what cynnar said. Be very careful what you do with root. Other than that don't try to fastboot back to ANYTHING...stay where you are until they (Devs) come up with a solution to get us back on "the path".Ok, just got back on here and noticed what is going on. If I'm on .84 and everything is running smoothly with root should I be worried? I have no want or need to go back to GB now that this build is working so nicely for me. Thoughts? Advice?
Posted 30 April 2012 - 10:51 AM
+1 on what cynnar said. Be very careful what you do with root. Other than that don't try to fastboot back to ANYTHING...stay where you are until they (Devs) come up with a solution to get us back on "the path".
Follow me @xlightwaverx
Posted 30 April 2012 - 10:56 AM
I still say we fb to the developmental build sextape released on XDA. I am trying to get him to mirror it somehow or at least torrent it. I bet this will be fastbootable considering it should have the latest fb system and all the brickers should not get the cdt.bin errors on this flash.
Just an assumption though.
X
Posted 30 April 2012 - 11:05 AM
Posted 30 April 2012 - 11:17 AM
is there any diffirence between this and the old leak? or is it just cause its new people want it. u kno that new new..lol
Posted 30 April 2012 - 11:21 AM
Posted 30 April 2012 - 11:29 AM
Lucky, lucky me. I flashed the 84 build and like a complete retard tried to fb back to 181. As we all know I soft bricked. I got the system back and everything ran great til today. It turned of and would not come back no matter what I tried. So I decided to take it into a Verizon store to and tell them the 181 caused the problem. They said oh yeah that's been happening all week. I will have a new phone in the mail tomorrow. I have learned my lesson on leaks. MSN it's hard bring a crack flasher. At last I'm getting a new phone out of it.
Sent from my Nook Tablet using Tapatalk 2
Posted 30 April 2012 - 11:47 AM
Posted 30 April 2012 - 11:50 AM
Posted 30 April 2012 - 11:56 AM
Posted 30 April 2012 - 11:59 AM
Posted 30 April 2012 - 12:09 PM
Posted 30 April 2012 - 12:15 PM
white on white whatt? I havent seen thatJust my $.02, but I don't think .85 will be the official OTA either. It still has the white on white text bug on the widget picker.
Posted 30 April 2012 - 12:28 PM
Posted 30 April 2012 - 12:31 PM
I am running .84 with no problems at all. Since I'm already stuck should I flash .85 to be up to date or is it a big risk?
0 members, 0 guests, 0 anonymous users