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

Root Bootloader

Status
Not open for further replies.
candoopa said:
i tried it, and it did not work for me, I get the certify error
Click to expand...

So did I. So mine was signed.

Code: 
device/lge/l0/releasetools/squisher -v \
	   -p /home/sammyz/android/system/out/host/linux-x86 \
	   -k build/target/product/security/testkey \
	   --backup=true \
	   --override_device=auto \
	   /home/sammyz/android/system/out/target/product/l0/obj/PACKAGING/target_files_intermediates/l0_MPCS_US-target_files-eng.sammyz.zip /home/sammyz/android/system/out/target/product/l0/l0_MPCS_US-ota-eng.sammyz.zip
Sanitizing environment...
Unpacking /home/sammyz/android/system/out/target/product/l0/l0_MPCS_US-ota-eng.sammyz.zip...signing boot.img...Unpacking...
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=l0 lpj=676678
BOARD_KERNEL_BASE 80200000
BOARD_PAGE_SIZE 2048
kernel: /tmp/iftsign8012/boot.img-zImage
ramdisk: /tmp/iftsign8012/boot.img-ramdisk.gz
cmdline=
Signing...
Extract signing info...
Running mkimage /home/sammyz/android/system/out/target/product/l0/repack.d/ota/boot.img...

That^ happened during build, I'm sure it was signed :P
 
candoopa said:
i tried it, and it did not work for me, I get the certify error

I examined what the signature looks like when it signs it, and it does not look like it has the same format as the stock signature


you have to realize that wkpark found these keys / keytool in a Ginger Bread source that LG put out by accident, so I am sure a lot has changed since then

I find it interesting that you got that triangle and not the error, so maybe you should experiment and little more, maybe we did not use the same method

for the record i did

unpacked stock recovery and repacked it
and then did

./signimg.sh recovery.img
Click to expand...

i assume you edited teh script? as it doesnt have teh right parameters for packing a boot.img for every device, you need to edit the mkbootimg line and put in the motion 4g related mkboot.img command
 
negative if it didnt work then you would need to unbrick which means wiping your phone and starting from scratch on root recovery etc.

just curious to throw this out there, how much would you guys pay to be able to use custom kernels/recoveries?
 
Sounds like it worked and custom recoveries and kernels will be coming your way =-) Once its completely verified I have no issues with anybody wanting to buy me a beer ;-)
 
Shabbypenguin said:
negative if it didnt work then you would need to unbrick which means wiping your phone and starting from scratch on root recovery etc.

just curious to throw this out there, how much would you guys pay to be able to use custom kernels/recoveries?
Click to expand...

If you'd like to elaborate further, I'm sure you would get a better response.
 
well at the moment only shabby knows the mkboot.img command changes he made in the script. sounds like we need to buy shabby a beer too.
 
sammyz said:
So did I. So mine was signed.

Code: 
device/lge/l0/releasetools/squisher -v \
       -p /home/sammyz/android/system/out/host/linux-x86 \
       -k build/target/product/security/testkey \
       --backup=true \
       --override_device=auto \
       /home/sammyz/android/system/out/target/product/l0/obj/PACKAGING/target_files_intermediates/l0_MPCS_US-target_files-eng.sammyz.zip /home/sammyz/android/system/out/target/product/l0/l0_MPCS_US-ota-eng.sammyz.zip
Sanitizing environment...
Unpacking /home/sammyz/android/system/out/target/product/l0/l0_MPCS_US-ota-eng.sammyz.zip...signing boot.img...Unpacking...
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=l0 lpj=676678
BOARD_KERNEL_BASE 80200000
BOARD_PAGE_SIZE 2048
kernel: /tmp/iftsign8012/boot.img-zImage
ramdisk: /tmp/iftsign8012/boot.img-ramdisk.gz
cmdline=
Signing...
Extract signing info...
Running mkimage /home/sammyz/android/system/out/target/product/l0/repack.d/ota/boot.img...

That^ happened during build, I'm sure it was signed :P
Click to expand...


how are you verifying that a signature is being written to the file ?


I am opening the file with a hex editor and actually looking at the signature


I look at your file and did not see one


I looked at the file I made, and it had a signature, but it was not the same type of signature that stock uses
 
Shabby's custom boot.img verified. But I will tell ya'll this:

The signing tool removes the author. So whether you want to say it's still stock, there will be proof once you see we can flash recoveries.
 
sammyz said:
Shabby's custom boot.img verified. But I will tell ya'll this:

The signing tool removes the author. So whether you want to say it's still stock, there will be proof once you see we can flash recoveries.
Click to expand...


ok, well I don't want to be a Debby downer, but I just am convinced this is not working, based on what I know.

Now I am not the smartest person in the world, and I have been wrong many times, and it has usually been when I was convinced that I was right.


I really do hope that I am wrong, and that it does work.

If it does not work with the scripts, we may still be able to use the keys, and I will look into that on the weekend if I have some time

I am traveling right now and do not have access to my build system
 
shabby made it a flashable zip. and i told him to flash it just like a rom or any other flashable so i assume thats what he did.
 
Status
Not open for further replies.
Back
Top Bottom