New Ics Build 6.14.84.xt912
#741
Posted 30 April 2012 - 09:59 AM
Sent from my Nook Tablet using Tapatalk 2
#742
Posted 30 April 2012 - 10:07 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
You'd better hope that VZ doesn't put your phone into fastboot and realize you have a different bootloader version. Your next bill will be about $700 more than usual if they find out.
That's what insurance is for. To cover things not covered under warranty.
[ 43V3R IC3'd on .84 ]
#743
Posted 30 April 2012 - 10:25 AM
#744
Posted 30 April 2012 - 10:28 AM
#745
Posted 30 April 2012 - 10:34 AM
Sent from my Nook Tablet using Tapatalk 2
#746
Posted 30 April 2012 - 10:37 AM
#747
Posted 30 April 2012 - 10:47 AM
#748
Posted 30 April 2012 - 10:53 AM
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.
#749
Posted 30 April 2012 - 11:06 AM
#750
Posted 30 April 2012 - 11:09 AM
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?
don't try it. Besides i think ypi would have to update from 181 and that means an rsd and that will brick the phone
If it's not broke try harder.
#751
Posted 30 April 2012 - 11:12 AM
Everyone done it for different reasons. Some wanted new. I wanted to start deodexing. Some just couldn't help themselves.
I haven't noticed much of a difference between the two. Some have noticed changes though.
It's not worth the risk IMO.
If it's not broke try harder.
Im a flash addict myself does motocast works or flash for chrome users
#752
Posted 30 April 2012 - 11:21 AM
Im a flash addict myself does motocast works or flash for chrome users
I don't know of they do I don't use those, but i think crackle is working on 84
If it's not broke try harder.
#753
Posted 30 April 2012 - 11:23 AM
white on white whatt? I havent seen that
Are you talking about apex launcher? Bc that's definitely apex launcher and not Moto's ICS. The only big I've noticed is scrolling cache being a little bit weird on tapatalk bug haven't been able to replicate it on any other app so it may just be app-specific.
[ 43V3R IC3'd on .84 ]
#754
Posted 30 April 2012 - 11:23 AM
#755
Posted 30 April 2012 - 11:24 AM
Im a flash addict myself does motocast works or flash for chrome users
I have had no flash issues on chrome beta.
[ 43V3R IC3'd on .84 ]
#756
Posted 30 April 2012 - 11:27 AM
#757
Posted 30 April 2012 - 11:29 AM
IDK...but I would say it is a big risk if something doesn't go right. I'd stay right were you are for now.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?
#758
Posted 30 April 2012 - 11:30 AM
I dont understand something and i am now slightly confused. If i go into fastboot mode it says 0A.66 and i'm on 6.14.84. I just came across which says 6.11.744 and .748 are 0A.66 and 6.12.173 and .181 have a 0A.6C. Does that seem right??? If that were True, i should be able to bounce back to .744 or .748, no?
I don't think i would chance it.
If it's not broke try harder.
#759
Posted 30 April 2012 - 11:30 AM
I dont understand something and i am now slightly confused. If i go into fastboot mode it says 0A.66 and i'm on 6.14.84. I just came across which says 6.11.744 and .748 are 0A.66 and 6.12.173 and .181 have a 0A.6C. Does that seem right??? If that were True, i should be able to bounce back to .744 or .748, no?
I can verify my 181 is 0A.6C. However, I wouldn't trust that them changing two codes to look alike on a leaked file means they are actually the same. It is possible that the compiler they use defaults to OA66 simply because it was the first value entered, and then they could have forgotten to enter a value when compiling the leak. If enough other people verify having something besides OA66 though, then maybe for some devices it is going to 66 and other some new non-compatible build. That would explain why some people are fine and others are stuck.
#760
Posted 30 April 2012 - 11:31 AM
I dont understand something and i am now slightly confused. If i go into fastboot mode it says 0A.66 and i'm on 6.14.84. I just came across which says 6.11.744 and .748 are 0A.66 and 6.12.173 and .181 have a 0A.6C. Does that seem right??? If that were True, i should be able to bounce back to .744 or .748, no?
Mine says 0A.74
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users