• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Custom recovery on x!!!!!!!

oh you shouldn't have done that. Now people will flame you if it doens't happen. you know people don't read smiley! ;)
 
Link to AllDroid's Twitter

What they said






This is awesome:D:D:D:D

I just talked to my guy who works at motorola about this, and they apparently knew this was going to happen. They made the locked bootloader to stop everyone from being able to crack this thing and flood moto with bricked phones, like what happened with the first Droid. They knew the smart devs out there would pop it eventually. Thats what he said when he saw all this on here. They just want the flow of hacked phones that would get swapped out from verizon and sent back to moto under warranty to slow way down.
 
I just talked to my guy who works at motorola about this, and they apparently knew this was going to happen. They made the locked bootloader to stop everyone from being able to crack this thing and flood moto with bricked phones, like what happened with the first Droid. They knew the smart devs out there would pop it eventually. Thats what he said when he saw all this on here. They just want the flow of hacked phones that would get swapped out from verizon and sent back to moto under warranty to slow way down.

By no means am I starting a rumor (just daydreaming) but I wish Motorola would realize that they can't stop it and now that it's cracked just open it up for us. It would make everything much easier.
 
I just talked to my guy who works at motorola about this, and they apparently knew this was going to happen. They made the locked bootloader to stop everyone from being able to crack this thing and flood moto with bricked phones, like what happened with the first Droid. They knew the smart devs out there would pop it eventually. Thats what he said when he saw all this on here. They just want the flow of hacked phones that would get swapped out from verizon and sent back to moto under warranty to slow way down.

I find that an odd stance for them to take. Seems there would be more bricked phones due to the locked bootloader because its so much easier to do. I guess its also easier to see thats what happened and therefor deny the claim though
 
I just talked to my guy who works at motorola about this, and they apparently knew this was going to happen. They made the locked bootloader to stop everyone from being able to crack this thing and flood moto with bricked phones, like what happened with the first Droid. They knew the smart devs out there would pop it eventually. Thats what he said when he saw all this on here. They just want the flow of hacked phones that would get swapped out from verizon and sent back to moto under warranty to slow way down.

This is where Motorola is being stupid. Why not use that efuse or some other method. To trip something that makes it easy for them and VZW to know if the phone was hacked and simply turn bricked phones away if the trigger is triggered. Everyone would be happy with that (except users that bricked their phones. But that's on them if they take the risk) win win for everyone.
 
I find that an odd stance for them to take. Seems there would be more bricked phones due to the locked bootloader because its so much easier to do. I guess its also easier to see thats what happened and therefor deny the claim though

Yeah and then they go nuts sending lawyers to shut down sites that post the SBF, a file that can fix a bricked phone. Apparently not everyone at Motorola are on the same page.
 
Yeah and then they go nuts sending lawyers to shut down sites that post the SBF, a file that can fix a bricked phone. Apparently not everyone at Motorola are on the same page.

Actually I find the whole C&D on the .sbf file the most out of character thing. It is weird to a point that I'm wondering if it really was a full blown C&D

Who throws a C&D at a website for hosting usb drivers (which can be downloaded at any moment from the moto site, android sdk, etc) and an .sbf and Doesn't include in that C&D the OTHER copyrighted files being hosted on the website, like all the Droid 1 .sbfs?
 
Actually I find the whole C&D on the .sbf file the most out of character thing. It is weird to a point that I'm wondering if it really was a full blown C&D

Who throws a C&D at a website for hosting usb drivers (which can be downloaded at any moment from the moto site, android sdk, etc) and an .sbf and Doesn't include in that C&D the OTHER copyrighted files being hosted on the website, like all the Droid 1 .sbfs?

Kind of makes me think that the sbf may be more "special" than anyone thought or thinks. It does re flash the phone in a weird way.
 
I'm glad I downloaded and saved the .sbf file while it was available. I usually grab those type of things "just in case".
 
They don't want to jump the gun and realese something that will possibly brick our phones. They are taking their time polishing and packaging this thing up so that when its realesed there wont be the need for upgrade versions. So wait patiently because it is coming!!! I never thought I would see a custom recovery, and I was already getting used to the fact of just having root.
 
I thought I would be be running froyo by now.:D That is probably it tough, they want to have froyo ready too, or maybe koush and birdrain combined forces

Yeah but there hasn't been any communication from any of them in some time now.

Are they hold up in an underground bunker hiding from Moto special ops?
 
Yeah but there hasn't been any communication from any of them in some time now.

Are they hold up in an underground bunker hiding from Moto special ops?

Maybe the MSO took them to a far away island and said try hacking from here
 
I thought I would be be running froyo by now.:D That is probably it tough, they want to have froyo ready too, or maybe koush and birdrain combined forces

I dont think the DX will be running Froyo until the OTA starts anyway. I dont think you can run Froyo on a 2.1 kernel. On the original Droid if you use froyo with a 2.1 kernel it thinks the battery is dead when its not and bootloops.
 
I dont think the DX will be running Froyo until the OTA starts anyway. I dont think you can run Froyo on a 2.1 kernel. On the original Droid if you use froyo with a 2.1 kernel it thinks the battery is dead when its not and bootloops.

yes, though the Milestone people managed at least to get together a build of froyo that can sit on the old kernel. It is not FroYo in the strict sense, since nothing that requires the new kernel works but it does have everything else.

Ok, so it's not really a counterpoint, but interesting nonetheless
 
Back
Top Bottom