master0fursinz
Member
freebird_78 said:
Try wiping cache again.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
NEW ICS leak .238
- Thread starter landon418
- Start date
Try wiping cache again.
ayosick said:
Did it do this on gingerbread? Try fxz'ing back to. 905 using rsd lite and see if it still does the black screen. If that fixes it, than it was something to do with the leak you flashed. I have not had bsod on 232 once however. So, it could very well be your phone. You are going to want to return it to stock 905 anyway before you return it. It's worth a try to go back and run for a while and see if that fixes it.
vipergts450
New Member
I just had to warranty replace my bionic because the screen simply died, same symptoms as you describe. On my new one right now. I was running stock .905 when it happened a week ago. I wonder if this is a series of hardware failures that we'll be seeing more of.
Sent from my DROID BIONIC using Tapatalk 2
I use the stock browser, and it syncs fine for me I am on the 238 leak rooted.
I'm not quite sure what there is to elaborate. The latest OTA release is 5.9.905. EVERY update until the next official OTA requires you to be on 5.9.905 as updates are not installs, they are patches to the existing system. You asked if you could go from 235 to 238 in recovery. The answer is no. If you could, why would I have bothered to write the HoB in the first place? 
What worries me, and this isn't meant to be offensive, is if you don't understand that simple concept, do you get why 235 and 238 aren't for you? I really truly hope you're not on either of those releases. If you are, then you didn't understand the risk before jumping into something that quite frankly should be left to more advanced users. 235 and above contain a new security version. This means you can't flash back to 905. And as I said, you MUST be on 905 in order to flash an update. You see the dilemma I hope. If you're on 235 and 238 requires you to be on 905 yet 235 and above don't allow you to downgrade to 905....see the issue? The "solution" to this problem is at the heart of the HoB. By flashing the boot.img of the version you're trying to go to, and flashing the system and preinstall images from 905, you can get the next update to apply. That's how we go from 235 to 238. We flash the 238 boot.img, 905 system, preinstall, and webtop, and then boot into recovery to apply the 238 update. Don't think for a moment, however, that this process is without risk. And it's certainly not going directly from 235 to 238 without flashing parts of 905. Doing so soft bricks your phone until the update is applied successfully in recovery. Not a process most users should be comfortable with. This is why I've repeatedly warned people to stick to 232 unless you FULLY understand the risk. This is also why I get impatient with people who say "oh, I don't care about downgrading, I don't like GB anyway." Well, you may not like it, but, you sure as hell need it to move forward. Therein lies the issue.
What worries me, and this isn't meant to be offensive, is if you don't understand that simple concept, do you get why 235 and 238 aren't for you? I really truly hope you're not on either of those releases. If you are, then you didn't understand the risk before jumping into something that quite frankly should be left to more advanced users. 235 and above contain a new security version. This means you can't flash back to 905. And as I said, you MUST be on 905 in order to flash an update. You see the dilemma I hope. If you're on 235 and 238 requires you to be on 905 yet 235 and above don't allow you to downgrade to 905....see the issue? The "solution" to this problem is at the heart of the HoB. By flashing the boot.img of the version you're trying to go to, and flashing the system and preinstall images from 905, you can get the next update to apply. That's how we go from 235 to 238. We flash the 238 boot.img, 905 system, preinstall, and webtop, and then boot into recovery to apply the 238 update. Don't think for a moment, however, that this process is without risk. And it's certainly not going directly from 235 to 238 without flashing parts of 905. Doing so soft bricks your phone until the update is applied successfully in recovery. Not a process most users should be comfortable with. This is why I've repeatedly warned people to stick to 232 unless you FULLY understand the risk. This is also why I get impatient with people who say "oh, I don't care about downgrading, I don't like GB anyway." Well, you may not like it, but, you sure as hell need it to move forward. Therein lies the issue.Hey man, I'm not offended at all. I appreciate all the time you put in to help everyone. I'm on 235 because I I accidentally loaded. 235on the sd card instead of 232 and figuring out where to go from here. I have hob ready to go but I'm double checking before I do anything. Thanks again for your help,
Yet another reason for the house to exist... I specifically name the update files in a way to make it impossible to flash the wrong one. That truly sucks that you're in the position you're in due to a simple mistake. Fortunately the house should do its job to move you to 238 fairly painlessly. Now you're stuck without the safety net of an fxz should something go wrong, however, so be extra cautious. Good luck.
Sent from my Xoom using Tapatalk 2
To add a bit to that, if you downloaded every leak they would all be Blur_Version.5.9.905.XT875.Verizon.en.US.zip. You could play Russian Roulette with your Bionic by installing one of the leaks (assuming you're on .905) and then looking to see which one you got.
That's also why some people are worried about being on the OTA path. Motorola/Verizon assumes that you have 5.9.905 and when they ping your phone to send the OTA, your phone will send back the version that it currently has. If it isn't 5.9.905 they move on.
Last edited: