Read the last post on that thread...
Sent from my DROID X2 using xda app-developers app
"Do you need help getting adb installed or just the instructions on how to run it?"
you're going to have to clarify, I don't understand, it looks to me like like nobody has taken him in and really tried to extract the files
Invisiblek already ran through a phone with the same screen, its as locked as the rest of ours
Sent from my DROID X2 using xda app-developers app
Developing right now:
JackpotClavin and Invisiblek have successfully loaded a custom kernel using a modified recovery ramdisk. It's still very early but this is excellent news for us. As it stands, this method wipes ClockworkMod and requires the recovery key combination on every boot, but those issues can probably both be overcome with custom scripts.
Stay tuned guys...and mash those two guys' Thanks buttons!
And I'm now rebuying the device :-D
Sent from my ADR6425LVW using xda premium
And I'm now rebuying the device :-D
Sent from my ADR6425LVW using xda premium
lol that is why you wait for a few days while everything plays out. no need to over react like the wife does
Invisiblek succesfully booted to android using "adb reboot recovery" with his modified recovery.img.
Basically we made it look as if going to recovery, but actually continuing onto boot.img.
thats not 100% accurate
i flashed a modified boot.img to our recovery partition (/dev/block/mmcblk0p18)
then rebooted into recovery
it booted up into android using this modified boot.img
i don't plan for this to be of any real use to us though. proof of concept really
we need our access to /dev/block/mmcblk0p7 (where our stock boot.img actually resided)
thing is, we can flash to mmcblk0p7 just fine, but it wont boot (wont do anything actually other than let you get back into odin mode, where you can re-flash the stock boot image, or it gives you this when you try to boot android or recovery: http://i.imgur.com/Ci0gY.png )
rest assured. this is being worked on...
thats not 100% accurate
i flashed a modified boot.img to our recovery partition (/dev/block/mmcblk0p18)
then rebooted into recovery
it booted up into android using this modified boot.img
i don't plan for this to be of any real use to us though. proof of concept really
we need our access to /dev/block/mmcblk0p7 (where our stock boot.img actually resided)
thing is, we can flash to mmcblk0p7 just fine, but it wont boot (wont do anything actually other than let you get back into odin mode, where you can re-flash the stock boot image, or it gives you this when you try to boot android or recovery: http://i.imgur.com/Ci0gY.png )
rest assured. this is being worked on...
thats not 100% accurate
i flashed a modified boot.img to our recovery partition (/dev/block/mmcblk0p18)
then rebooted into recovery
it booted up into android using this modified boot.img
i don't plan for this to be of any real use to us though. proof of concept really
we need our access to /dev/block/mmcblk0p7 (where our stock boot.img actually resided)
thing is, we can flash to mmcblk0p7 just fine, but it wont boot (wont do anything actually other than let you get back into odin mode, where you can re-flash the stock boot image, or it gives you this when you try to boot android or recovery: http://i.imgur.com/Ci0gY.png )
rest assured. this is being worked on...
indeed, I can't believe how many people are over-reacting, have you no faith in our development guys? do you have to be handed CM/AOSP on a silver platter days before the device is even released? If so you chose the wrong device to begin with!
I think some of the over reacting is justified because if a company truly wants to lock down a bootloader with encryption, it won't be broken. I don't think a single encrypted bootloader in an android device has ever been broken. If it turns out to be something different, like S-OFF on HTC devices or some such then that's one thing. An encrypted bootloader is something else entirely and would have a lot of implications to our enjoyment of these devices. Namely it would mean running anything other than the stock kernel would be like running a VM in an underpowered PC. We could lie to ourselves and say that it was OK, but that's about it.
. . .
thing is, we can flash to mmcblk0p7 just fine, but it wont boot (wont do anything actually other than let you get back into odin mode, where you can re-flash the stock boot image, or it gives you this when you try to boot android or recovery: http://i.imgur.com/Ci0gY.png )
rest assured. this is being worked on...
locked bootloader: a bootloader that protects certain partitions from being modified. Flip a switch (S-ON to S-OFF), and the bootloader is unlocked. Or more appropriately, NAND protection is removed, meaning the various protected partitions on the NAND internal flash memory are now able to be mounted read/write. Like the confusing terminology of "encryped bootloader," there's nothing "locked" about the bootloader itself. The bootloader is locking up areas of the internal flash memory. That's what devs are trying to "unlock."
signed bootloader: a bootloader signed by the manufacturer to assure it's official. A signed bootloader can be either locked or unlocked. Just because it's signed doesn't imply it's locked. The Engineering bootloader is an example of a signed but unlocked HBOOT.
encrypted bootloader: same as a signed bootloader, but the signature is encrypted, making forgery of the signature practically impossible. One possible solution is to flash a leaked Engineering HBOOT with that same encrypted signature. There's no guarantee that this image will ever be leaked or that some other security measure isn't in place to prevent this workaround. Another solution is to find some way to hack into the phone's radio and call a command to flip the switch from S-ON to S-OFF. But there's no guarantee that such an exploit exists on all phones.
Invisiblek succesfully booted to android using "adb reboot recovery" with his modified recovery.img.
Basically we made it look as if going to recovery, but actually continuing onto boot.img.
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
kexec -l /sdcard/kernel --reuse-cmdline --ramdisk=/sdcard/ramdisk
mount /dev/block/mmc1... /system