yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] Zepius:
id gladly void my warranty for completely unlocked bootloader. id sign all kinds of stuff register my device, anything to get an unlocked bootloader.
[Motorola Droid Bionic] Calla969:
I think smart phones need to be looked at more like computers than phones. I'm glad I don't have to buy my laptop through my ISP and have them decide how I am able to use my computer. It is really annoying when the service provider controls (or tries to control) the hardware, software, and the network. We pay for the hardware, it should be ours to use how we want. They subsidize the price so they can lock us into a contract and guarantee a certain amount of income. They should be able to do what they want with their network, but not the hardware/software. If they determine that someone is tethering or violating their terms of service because they modified their device, that is a different issue. The issue should be the violation of the agreement, not the modification of the hardware.
[Motorola Droid Bionic] phydo:
I'd just buy the phone straight from motorola with no contract for it lol
[Motorola Droid Bionic] phydo:
Flashing radios and people oc'ing like idiots are the only real brick reasons I see. Other than that it doesn't really happen.
[Motorola Droid Bionic] EDNYLaw:
Exactly what I'm saying! Verizon could solve 99.9% of bricks with unlocking the bootloader and letting us flash back to stock or having people who don't know what they're doing bring it back to Verizon and have Verizon flash it for them, 20 minutes and no expense required on Verizon's part.
[Motorola Droid Bionic] dan46n2:
Except for the time they're paying Tech's to fix the mistakes of end users.... But they could get around that by putting a fee on it.

Heck, I remember when they used to charge $10 to transfer your contacts over from one phone to the next, so charging a fee to flash back to stock for someone would fall right in line with their previous practices.
[Motorola Droid Bionic] EDNYLaw:
So I just found something that may be applicable concerning open internet policy:

"We adopt a no blocking rule that guarantees end users' access to the Web and protects against mobile broadband providers' blocking applications that compete with their other primary service offering—voice and video telephony—while ensuring that mobile broadband providers can engage in reasonable network management:

A person engaged in the provision of mobile broadband Internet access service, insofar as such person is so engaged, shall not block consumers from accessing lawful Web sites, subject to reasonable network management; nor shall such person block applications that compete with the provider's voice or video telephony services, subject to reasonable network management."

Interesting, seems like tethering would fall right in there. Of course it always seems to be what is "reasonable."

Edit: Found what I believe is considered reasonable. So as not to waste space, if anyone's interested it's under Part III. D. in the attachment.
[Motorola Droid Bionic] Calla969:
They're just another huge corporation doing whatever they want until someone gets up the courage and motivation to challenge it.
[Motorola Droid Bionic] stevessvt:
Fixed for you. :)
[Motorola Droid Bionic] Calla969:
VERY true. And they will always have plenty of $$$ to fight back.
[Motorola Droid Bionic] Zepius:
I have sent an email to some of the executive team at VZW about the bootloader. i did some google searching and found some email addresses.

daniel.mead@verizonwireless.com,

marni.walden@verizonwireless.com,

john.bianchi@verizonwireless.com,

andres.irlando@verizonwireless.com,

tami.erwin@verizonwireless.com,

kevin.zavaglia@verizonwireless.com

i didnt get any bounced emails so i assume they went through.
[Motorola Droid Bionic] phydo:
Well an fxz may not be able to fix a bad flashed radio. Many times not checking the checksum and flashing partially downloaded files is the third brick reason
[Motorola Droid Bionic] EDNYLaw:
That's why I want to try to find some legal precedent or at least SOMETHING in the case law that indicates what Verizon is doing violates C Block. No one person would have the resources to pursue this against Verizon so I'm hoping to rally more lawyers to look into this for free. I can tell you, just today, casually research I've probably put in enough work to bill a client between $700 - $1,000. It could add up quick which is why I feel like I have some responsibility to do something since I can do it for free :)
[Motorola Droid Bionic] phydo:
I feel you man. Did I ever think I'd find anything with the cheesecake thing? No. I researched, tought, and wrote the app because it was an opportunity for growth. If I had your expertise I'm sure I'd be with you. But I did what I can so far. I'm sure other stuff will pop up.
[Motorola Droid Bionic] EDNYLaw:
That's the exact reason I want to do this kind of stuff, all sorts of people pulling together to get something done that benefits everyone in the community. It's a good effort and I believe that through everyone's participation whether it be through cheesecake, legal recourse or what have you, this bootloader problem will be knocked out eventually
[Motorola Droid Bionic] phydo:
Btw guys on 5.5.893, there is now an update to 5.6.893 (mr1) update.

First glance new LTE radio.
[Motorola Droid Bionic] open1your1eyes0:
What server? Have you done the update and tested root and everything still works?
[Motorola Droid Bionic] phydo:
Either staging1 or the master production server. Got it the second I rebooted after updating from 892-893. Yes I kept root thru it too.
[Motorola Droid Bionic] open1your1eyes0:
Found it on staging1, applying now.

EDIT

: Applied, rebooted, tested root is working, haven't noticed anything obviously new. Seems a little faster. Battery life to be tested.
[Motorola Droid Bionic] phydo:
One thing I still noticed on892 is I use Bluetooth to play music thru my car. It used to skip when on Bluetooth. Hopefully one of the updates fixed it
[Motorola Droid Bionic] Zepius:
I just spoke to a lady from Executive relations (Verizon Wireless Executive Relations <ExecutiveRelations@VerizonWireless.com>) about the whole bootloader.

more or less she basically said "Verizon Wireless will not change its stance on the locked bootloader on the Motorola Bionic. It was part of the agreement we had with motorola to protect our security"
[Motorola Droid Bionic] daveywoodard:
Is this what everyone else is seeing???

5.5.1_84_dbn-62_mr-1
[Motorola Droid Bionic] papi92:
Upload the maintenance release. I'll test it out
[Motorola Droid Bionic] idefiler6:
So people are saying once you install .893 you could be off the chain for official OTAs....well doesn't Cheesecake give you the ability to just force the future OTAs anyway?
[Motorola Droid Bionic] daveywoodard:
I didn't realize it was a newer version so I installed it. (Just got a replacement bionic today) so the file is gone.:( I got it from staging

---------- Post added at 01:35 AM ---------- Previous post was at 01:27 AM ----------

now staging shows.. dbn-62 to dbn-62_mr1
[Motorola Droid Bionic] papi92:
Okay sounds good. Thanks ill find it lol just have to find a way to return to 893 to accept the update. I'm traveling and all I have is me phone
[Motorola Droid Bionic] phydo:
I have the file from earlier this morning. Pm me for it
[Motorola Droid Bionic] daveywoodard:
I downloaded the dbn-62 to dbn-62_mr1 where should I send it?
[Motorola Droid Bionic] papi92:
Pm me it. Upload to mediafire. I'll test to make sure radio and such doesn't cause problems. Yes I have multiple bionics lol
[Motorola Droid Bionic] phydo:
http://db.tt/VrXpcLpc

I already use it. Its safe

Btw version is 5.6.893 disregard filename. I just name them cuz Motorola doesn't.
[Motorola Droid Bionic] papi92:
Now the one you uploaded is the one for the 893 to mr1 or what
[Motorola Droid Bionic] daveywoodard:
dbn-62 to dbn-62_mr1
[Motorola Droid Bionic] mistawolfe:
Welp, gonna have to restore my stock 893 update and install this bad boy :D
[Motorola Droid Bionic] trueagle:
it keeps failing and i cant figure out why?
[Motorola Droid Bionic] bgs_piece:
I downloaded to -mr1 file and it installed fine but now under settings, about phone, the webtop version shows "unavailable" Does this mean that my phone no longer has webtop?
[Motorola Droid Bionic] phydo:
You probably don't have a stock phone. Using any Rome or themes?
[Motorola Droid Bionic] azwildfire:
Have to launch webtop first sometimes - 893 did the same thing to me until I used webtop for the first time.

---------- Post added at 08:54 AM ---------- Previous post was at 08:49 AM ----------

Will http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html allow for the update to install? i know 893 won't install again after this process.

Or will http://www.mydroidworld.com/forums/...nic-cwr-update-zip-system-only-886-893-a.html allow for this to be installed?
[Motorola Droid Bionic] real0325:
mr1 failed

I downloaded the file and it also failed on me . running stock 866 im guessing you have to be on the first 893 file to receive the mr1 file.

any help would be greatly appreciated
[Motorola Droid Bionic] phydo:
Correct
[Motorola Droid Bionic] Alxoom33:
ota 5.6.893 using Cheeskakev2.apk

v

Based on above, I rerooted using forever root method and downloaded the cheescakev2.apk, and then using cheescake I found a new update 5.6.893 rom.

I downloaded and the update loaded automatically with Andy and his file friend with no problems, and I then reloaded v 2.0, which appears to contain the earlier v 5.5.893 system. :D
[Motorola Droid Bionic] Sjflowerhorn:
Stock rooted 5.5.893 keep getting "update failed". Waah waaaah. Ill keep trying things.

One thing i noticed is in cache folder diwnload is named 5.5.893 but ota update message says 5.6.893 any ideas on that one?
[Motorola Droid Bionic] Sjflowerhorn:
Its now saying there is an error with framework even after completing restore to stock 5.5.893 then factory reset. download is good. Something else is going wrong. Is there a way to flash stock framework?
[Motorola Droid Bionic] bgs_piece:
I'm on the latest 5.6.893 and the only issue I am experiencing is when I try to edit the calendar it forcecloses. I can go into the calendar and click on an item but once I try to edit, com.android.calendar forcecloses. Anyone else having this issue?
[Motorola Droid Bionic] Calla969:
Just went through the whole process of returning to stock to update and I am in the process of updating to 5.7.893.en.US. Seems like there's already a new version out! Found it on Staging 1 using Cheesecake.

I only see this update when I search from .886. After updating to .5.893, when I search I only see .6.893, but I did download and copy .7.893. Dropbox link to 5.7.893 http://dl.dropbox.com/u/20562469/Blur_Version.5.5.886.XT875.Verizon.en.US.zip
[Motorola Droid Bionic] lawtalking:
How do you flash the file if you do not download it through cheesecake. I restored to .886 stock because I wanted to update to .6.893 but when I go to staging 1 it says I am up to date.
[Motorola Droid Bionic] ebourlet:
5.7.893 noe headphone whine

Just went to 5.7.893 via cheescake came from stock rom. system version now 5.7.893.XT875

Webtop Version WT-1.3.0-108_DBN-21

Main reason was I just started using headphones today and that whine was driving me crazy with the stock build. It's now gone .

******UPDATE 11/1/11******

Verified Webtop working using my HDMI Dock. I did go right from original base ROM to the latest . From what I'm reading people that did incrementals are still having web top issues. I do have a strange problem though when I run Cheescake it does not let me sellect a server. When I attempt to change update server I get a little popup that says "Should be good" and never get the drop down to select a server.
[Motorola Droid Bionic] demo333:
Some one confirm that the hotspot on 5.7.893 works?
[Motorola Droid Bionic] 0mie:
I've been using it since last night no problems...
[Motorola Droid Bionic] demo333:
About the webtop?
[Motorola Droid Bionic] zachdroid:
What does the 7.893 update? Just webtop?
[Motorola Droid Bionic] Sjflowerhorn:
Webtop still unavailable to me on 7.893
[Motorola Droid Bionic] ebourlet:
Confirmed webtop working with 5.7.893 on my HDMI Dock. I can't select a sever with cheesecake any more though..

I primarily took the plunge to get rid of the headphone whine.
[Motorola Droid Bionic] RoboJoe:
Webtop with just an hdmi cable, or with an attachment?

Swyped from my Droid Bionic, unless I was in landscape, in which case I Swiftkeyed the hell out of it.
[Motorola Droid Bionic] papi92:
Cheesecake works for me
[Motorola Droid Bionic] phydo:
Anyone have a 6.893->7.893 update?
[Motorola Droid Bionic] cellzealot:
http://db.tt/0K4oFHqW
[Motorola Droid Bionic] johnlgalt:
Great app, Phylo. Wondering, really just musing out loud, but....

Is there any way to pre-chceck which servers are up (like a batch ping) so that the app will then list only servers that are up instead of all of them?

I'm currently trying to maintain a list of servers that are up versus those that are down, but it seems that even if I cannot ping a server it may still be up, so that sort of check may in fact not be accurate at all....
[Motorola Droid Bionic] phydo:
Thanks man. I somehow didn't get that one.
[Motorola Droid Bionic] wanderfowl:
Phydo, Thanks for all the hard work you're doing on this project, and for your dedication. Nothing else to add, I just wanted to take a second to thank you for it.
[Motorola Droid Bionic] phydo:
Thanks :) at least we get some stuff from looking. You guys have helped me too
[Motorola Droid Bionic] mistawolfe:
I'm on 5.7.893 stock and I've been searching all day. Going from 5.6 to 5.7 reintroduces the infamous data drop. Hoping to find something new today - so far, nothing...
[Motorola Droid Bionic] open1your1eyes0:
Hey Phydo, just a little recommendation, for others you should probably try to update the 2nd post of this thread a bit with the three new updates we discovered since then. Perhaps provide download links as well?
[Motorola Droid Bionic] phydo:
Yes I've been meaning to. Ill get around to it soon. Thanks for the gentle nudge :)
[Motorola Droid Bionic] open1your1eyes0:
Thanks Phydo! Much appreciation for starting this great thread. Really loving getting all these updates so early. :)

P.S

: I'm assuming still no bootloader related discoveries made?
[Motorola Droid Bionic] yutzyscott:
Can someone post a copy of the 5.6.893
[Motorola Droid Bionic] ebourlet:
was forced to go back to 5.5.893 (because I aparently don't reed before leaping) from 5.7.893 found that the audio effects that worked in 5.7.893 just add white noise in 5.5.893. Sure wish I could get a copy of the 5.7.893 system . The Cheesecake servers are saying that I'm up to date with the 5.7.893 radio but system version 5.5.893.
[Motorola Droid Bionic] Calla969:
I'm on 5.6 and I still have the data drop. I've noticed problems with wifi too. Seems to have issues with all types of data. Maybe not as frequent as before, but I have trouble switching from 3g to 4g, and sometimes all data drops. Wifi, 3g, 4g, everything. I usually show the data icon highlighted in blue, but I can't access the internet until I reboot. Sometimes that doesn't even fix it. I really hope they can figure this out.
[Motorola Droid Bionic] unchoney:
Wow that is strange ...i had installed the partial update to get the 02 radio then later rolled back with DTS and DHS restore and forever root. Then tried cheesecake and was able to install full 7.893 update( which has the webtop) and maintained root.
[Motorola Droid Bionic] jbreaz:
Which server did you find the update on? I tried that earlier and it didn't work for me either
[Motorola Droid Bionic] azwildfire:
All my data issues went away going to 5.7.893 - moving apps to the media area no longer makes them disappear, and i have much better reception and data speeds at my house.

Guess I got lucky since everyone else seems to think their phone is broken :/
[Motorola Droid Bionic] bigeddthemonk:
Im in the same boat 7.893 fixed mine all up
[Motorola Droid Bionic] runandhide05:
Haven't seen a need for this, but can we go back to the stock factory version after updating?
[Motorola Droid Bionic] phydo:
Probably not
[Motorola Droid Bionic] cellzealot:
The system can be reverted and changed via many methods but the boot image and radio can only be updated via official update zips and only in the order that they are intended to update and can never revert to a previous version.
[Motorola Droid Bionic] luke1333:
Everything is better on 5.7.893 but is the motorola server down now? I can't check for updates or use social networking widgets cause it says setup motorola account but won't connect even on 4g or wifi so I don't have social widgets any fix for this or anybody else have these problems?
[Motorola Droid Bionic] bigeddthemonk:
Must be because yesterday when i was still on 5.893 it was doing that i was so mad so i connected to my home wifi, still no luck.
[Motorola Droid Bionic] papi92:
894 on QA blocks forever root.
[Motorola Droid Bionic] bigeddthemonk:
That was fast, already beat us :(
[Motorola Droid Bionic] phydo:
Any new radio or bootloader? If not you can mod the system.img and flash
[Motorola Droid Bionic] papi92:
It really has nothing in it. No system files. Ill upload it
[Motorola Droid Bionic] papi92:
http://db.tt/Iy5GD4ZG
[Motorola Droid Bionic] 0mie:
Lame lol
[Motorola Droid Bionic] bigeddthemonk:
Maybe they got smart and did this to ward off cheesecake users?
[Motorola Droid Bionic] papi92:
I'm talking to a close friend to verify my thoughts. Don't flash yet
[Motorola Droid Bionic] quentin0:
This is truly war. It's going to keep going back and forth, they are just going to delay the OTA as they focus their priorities on taking out root capabilities. The only way it will end is if our devs finally get dumbfounded, or if the bootloader gets unlocked and it doesn't matter what update they push; it would all be reversible by the FXZ.

If 894 has no bug fixes and is strictly an "F you" to FOR3V3R root, that definitely puts it into perspective what we're up against. It's sad how abundantly clear they make it.

I guess we ain't seen nothing yet, I'm sure one of these feisty devs/community members has an ace up their sleeve. Or somebody take one for the team and get your girlfriend to flirt with Moto's project lead.:p
[Motorola Droid Bionic] EDNYLaw:
Ok, so this seems like the perfect time to ask this question if it is in fact true that .894 breaks forever root (whether it does or doesn't isn't really the issue). I posted like a week ago about doing legal research into Verizon's (pretty blatant) violation of their C Block license while waiting for my bar results, happy to say I passed and am on my way to being a fully admitted attorney (watch out Verizon). Now I've got a pretty good handle on the legal side of things and through my readings on XDA and Rootzwiki, I have a fairly decent grasp on the technical side. In order to present the best argument to the FCC (I'm going to do more than just file a complaint to be lost in the ether somewhere) I need some actual technical knowhow. The issue is whether unlocking the bootloader will impair Verizon's reasonable network management. I need to know from KNOWLEDGEABLE people (i.e. devs or the like) what EXACTLY unlocking the bootloader will do. I don't want, it'll allow us to access the kernal and radios... I know all this. I mean what will it allow us to do that may affect network management. I'd think something along the lines of wireless tethering (but that's a horrible argument on Verizon's part because there's a million arguments why it doesn't affect them) but along those lines. If anyone can think up reasons (think like Verizon and what they would say about unlocked bootloaders affecting their network management) please let me know. If someone could help bridge my knowledge gap it'd be greatly appreciated so I can crucify this assholes for their blatant violations and maybe in the process get some bootloaders unlocked :D

Edit: By the way, the license provision explicitly states they can't block apps from being installed (subject to the network management clause) and as far as I can tell, superuser is an app and if they don't allow it to be installed that is a DIRECT violation more so than a locked bootloader. The more I think about it, the denial of root access is a clear violation.
[Motorola Droid Bionic] 0mie:
The .894 update was on 6 servers when I checked earlier today. I didn't even check QA servers

There was only 6 files I the update, so it's just them saying FU guys and breaking root.
[Motorola Droid Bionic] quentin0:
Very interesting. But doesn't the Superuser app technically install on a nonrooted phone (it just won't get root access or do anything)? Is there anything that says they can't prevent apps from functioning in their attempts to "better manage their network".
[Motorola Droid Bionic] phydo:
Does it basically only change the init script?
[Motorola Droid Bionic] EDNYLaw:
The provisions aren't really specific, so there's ruin for some lawyering. I'd make the argument that if Verizon/Motorola prevents the app from functioning this is the same as preventing the app from being used
[Motorola Droid Bionic] 0mie:
The 2 files it changes say update-binary and update-script
[Motorola Droid Bionic] wanderfowl:
So, Motorola became aware of the Forever Root method, and seems to be wasting their time in this development cycle patching roots for the new version. As such, we can assume that people from Moto are monitoring these threads with hostile-to-development intent, which pisses me off immensely.

Perhaps, then, it would be wiser for people to cease discussing and publicizing working roots for newer, cheesecake-discovered versions of the phone. In addition, we may want to admonish people who want to keep root to stop the Cheesecake-update installs.

Basically, any rooting groundwork which is publicly discussed right now for newer-than-shipping versions is just telling some Moto-drone what to patch, so, we need to keep it on the down-low. We don't want to unintentionally provide the material and research needed for Moto to lock us out of our phones more effectively.

Once the OTA drops, root methods can be released, those of us waiting for the OTA to be official before upgrading will then be able to upgrade, get root before it's patched, and have a working, rooted phone. The time following can be spent working on additional roots for the ICS model, rather than playing catchup because we tipped our hand.

Just thinking aloud.
[Motorola Droid Bionic] ticrandall:
I was thinking that earlier.. I was also thinking how utterly disgusted I am with moto. This is my first moto phone, definetly the last. I hope google does them some good. I dont get why you would go out of your way to anger your customers..

I was going to turn this phone in for a replacment because of radio issues. Guess ill hold on.to it and flash .7, keep my root.

Anyways, ramble ramble it probably is a good idea to keep further rooting solutions off the table until moto is done jerking us around.

Question, what's the likely hood someone will get the bootloader unlocked, is it a matter of time, or a 50/50 shot?
[Motorola Droid Bionic] Gadgetz:
Pretty much what the iOS devs do. All the devs doing work on this should be made aware so they don't spill the beans. Maybe temporarily close the cheesecake threads and what not until the OTA is released???
[Motorola Droid Bionic] phydo:
There is word that a new root method is around but won't be released until post ota. I don't know it but I know it's around. Don't worry.
[Motorola Droid Bionic] wanderfowl:
Although I dislike it in principle, closing the Cheesecake threads, if nothing else, so people won't flash new software and then ask all over the forums how to get root back, may not be a bad idea. This is likely work best conducted in IRC?

And having just come from iOS, this is definitely too familiar for my taste. Ugh.
[Motorola Droid Bionic] papi92:
No all the update does is validate that the mount_ext3.sh is unchanged