Well, i'd wait for Sam's advice then, but i'll betcha the HoB will get you back up and running using ONE of the options.I have never used HOB i just use my custom fxz but the hack i did edited something my fxz wont fix :'(
Well, i'd wait for Sam's advice then, but i'll betcha the HoB will get you back up and running using ONE of the options.I have never used HOB i just use my custom fxz but the hack i did edited something my fxz wont fix :'(
Captain Crypto said:Never mind. I'm not doing it tonight.:icon_eek:
Well, maybe I will do it tonight. :blink:
The only thing I remember about that was some people who had froze or removed stuff had to first get back to stock before going to any leak...which I believe still holds true in order to get OTA.
But when the OTA is released it will be cross checked with the. 246 leak..and afaik that release is the final official OTA...so everyone who is running the leak will be on the path again.
I'm not sure what you were asking/saying so if my response isn't what you mean, ignore it
Sent from my. 246 ICS leaked BIONIC
I'm sorry, you are wrong. Like I said, I am the person who LEAKED .905, I do believe that I know what I am talking about. If someone had different file sizes between the leak and the OTA, they had a corrupt download.In the case of the .905 update, the leak and the OTA had different file sizes, so everyone on the leak had to fxz back to 902 and then take the OTA .905 before they could install any of the ICS leaks. That much I do remember because I spent a lot of time going back to 902, taking the OTA update before moving on to the next leak (before HoB, of course). I had to look back through some older threads to refresh my memory on this.
Dave12308 said:Let's wait to hear what he did (if he feels like sharing, that is).
I have never used HOB i just use my custom fxz but the hack i did edited something my fxz wont fix :'(
Ur not helping -_- the one i bricked was my holy grail of Bionics for OCing the other 2 cant compete
You are absolutely wrong. There WAS no difference, as a matter of fact, the .905 OTA never touched my phone until well AFTER I had installed my first leak (I am the originator of the .905 leak, actually). Most of the people having issues were using Safestrap. A build is a build. By definition, if something in .246 were changed, the entire thing would have to be rebuilt, and it would no longer be .246
Dave12308 said:I'm sorry, you are wrong. Like I said, I am the person who LEAKED .905, I do believe that I know what I am talking about. If someone had different file sizes between the leak and the OTA, they had a corrupt download.
Son of @%@%#%%#&€ $& € €%&% i just bricked my phone an i am on @%@%@%@%@%%@@%@%@% 246 oh my @%@%@%@%@%@%@%@%@% god kill me now
SamuriHL said:What the hell is wrong with you?Your buddy Samuri can help fix it you know.
![]()
sargentmajord said:I created a swap file in the android system to allow better ram access i also recreated my kernels values to run more efficient an then edited my I/0 scheduler for a 15mbs write speed an 25mbs read speed an i entered the wrong @##%#&#&&@%@%@%@ value somewhere
Took u long enough
altspeed said:Sarge! You know better than to play with the swap and heap size!
I tried to tell him that *LMAO*What the hell is wrong with you?Your buddy Samuri can help fix it you know.
![]()