Database Develop

[Q] Droid 3 SBF file question

Does the phone have to be completely bricked to use the SBF file for droid 3? Mine isn't working properly..i did a factory reset on my phone after i froze some of the bloatware...and now it doesn't work right

We have an official, working SBF for the D3? Where?

Yea wheres the sbf lol
Ru talking about the fastboot partitions?

haha its not official..it's the leaked version...i guess it's the fastboot partition..i dont exactly know the difference between the two

http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)

rdypatel said:
haha its not official..it's the leaked version...i guess it's the fastboot partition..i dont exactly know the difference between the two
Click to expand...
Click to collapse
Yeah, I am sort of confused about this too. I thought that ROMS would be possible once we had CWRecovery working, and we've had the leaked current and OTA versions for a while. So how is a flashable recovery different from the SBF?s we have now, and why isn't the CWR that just released adequate?
I apologize if these are really newbish questions.

I'm having the same problems. Since my OTA update my phone has trouble finding WIFI.

the leak is the same as the official, and im pretty sure you dont have to be bricked to flash hope this helps

No you don't have to be bricked.. my phone wouldn't download the 890 so I flashed it to hopefully fix w/e issue was going on w/ system updates on it and hoping it may have fixed the speaker failing.. but it didn't. Got my replacement tho and rooted + debloated. Runs a lotttt better.
Sent from my DROID3 using XDA App

[Q] How to start over?

I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.

atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv

Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.

Redownload?

Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?

I would redownload everything and try agian

littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?

atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?

I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App

http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium

wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.

Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.

i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721

I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!

i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.

How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).

i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop

Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.

re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283

jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?

I didn't think safestrap was working with the D4?

jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom

Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk

jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.

I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.

mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok

Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App

greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.

Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App

Send me your email addy in a message and ill send you a pic of it

Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?

Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.

Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.

Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.

Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.

Yes there is quite a few. Ill let you know as soon as i can

Update from zip aborted

In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?

i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)

icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.

strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.

strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX

icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.

\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol

I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.

well i just bricked my self on the update lol

Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.

jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?

Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.

strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.

mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app

If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2

azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215

podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol

azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)

Upgrading to JB Issue

I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!

jradicle11 said:
I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!
Click to expand...
Click to collapse
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).

I believe you must be on .246 to update to JB. No frozen, deleted, or altered system files either. I took the update and am very happy with it.

mikemikemikexxx said:
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).
Click to expand...
Click to collapse
Even with it being an official upgrade?

Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app

flyfisher7 said:
Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
That's exactly what I ended up doing. I flashed to 246 and OTA'd to JB. It ended up working quite well. I want to put on CM10.1, hopefully I don't have to flash back to 246.

A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD

SamuriHL said:
A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
So if you've taken the OTA JB update then you're screwed? No possible way to go back to ICS?
My phone worked great on ICS but since the forced OTA JB update it has become a complete piece of crap. I lose Verizon signal constantly and have to reboot my phone to get it back. This happens probably 6-7 times a day. Text messages hang and don't send, I get strange UI FC's, etc.
Has anyone else run into these issues? Any suggestions on how to fix?
Thanks,
Michael

Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.

SamuriHL said:
Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Click to expand...
Click to collapse
Honestly I am not surprised. I am the idiot who clicked OK without researching what the update was first. If I had, I wouldn't have taken it.
SamuriHL said:
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.
Click to expand...
Click to collapse
I thought about doing that, but I was hoping not to have to do so.
Since I was also dumb enough to not have OTA root keeper installed of course I lost root too. I see there is another post about rooting stock JB using Linux, etc. Has anyone developed another method yet? I have searched but haven't found anything. I used the motofail method to get root on ICS, but no posts as to whether that works on JB or not.
Thanks,
Michael

No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.

SamuriHL said:
No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.
Click to expand...
Click to collapse
Ok so be it. I saw that post on the Easy Root using a virtualbox image.
I also saw this post: http://forum.xda-developers.com/showpost.php?p=40430047&postcount=73
Since I previously had root on ICS, will this work for me?
Thanks for patiently answering my questions, I appreciate it.
Michael

It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.

SamuriHL said:
It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.
Click to expand...
Click to collapse
Ok I will give it a try and go from there..
Hopefully with root restored and FDR my phone will return to what it was and I will be happy with it once again.
Thanks again,
Michael