digital signature validation of elf files - Galaxy Tab S2 Q&A, Help & Troubleshooting

Hey,
I saw that in the device kernel there is an implementation of digital signature validation in digsig.c file.
However I cannot tell if the validation is already being called before executing the elf file .
Is it already being called? where?

Related

Unable to root my Legend

Hey guys,
Can you please help me on this.
Legend:
bought in India
Firmware Versin: 2.1
Baseband : 47.26.35.04U_7.05.35.26L
Kernel : 2.6.29-e3993620
Build : 1.32.720.3 CL155118
Procedure followed : http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
I was able to create gold card without a problem but when I run step1-linux.sh, I get the error "FAILED (remote: 43 main version check fail)"
and at step 2: error: device not found is the error.
can someone please help me out here
====================================================================
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$ ./step1-linux.sh
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
[sudo] password for amarendra:
erasing 'cache'... OKAY
... OKAY
About to start flash...
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option.
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$ ./step2-linux.sh
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$ error: device not found
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$ ./step2-linux.sh
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$ error: device not found
[email protected]:~/Desktop/r4-legend-root/r4-legend-root$
===============================================================
tried in Windows 7 with HTC Sync installed and in Ubuntu 10.4
Your software version must be 1.31 or below. Dont know why they dont tell that.
make sure your device have sofware version 1.31 or below., if not, downgrade it first.
Thanks for the replies guys. btw, is is possible to downgrade without rooting?
desiibond said:
Thanks for the replies guys. btw, is is possible to downgrade without rooting?
Click to expand...
Click to collapse
Ofcourse you can, just search for official WWE ROM, but it will flash your radio too, search suitable official ROM. Search in legend foeum, i ever shown one here.
Sent from my HTC Legend using Tapatalk
BesFen said:
Ofcourse you can, just search for official WWE ROM, but it will flash your radio too, search suitable official ROM. Search in legend foeum, i ever shown one here.
Sent from my HTC Legend using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade using 1.31 HTC Official. Now, the problem is that I am able to erase the cache but when I try to load the rom.zip, I am getting the error 'device not found'. Though to reinstalling HTC Sync app in win7. uninstall went fine but now it is not able to install saying some sub-app is not able to load. I think it will be better to load my home PC with XP and try the process again
Thanks a lot for the reply BTW.

[Q] how to return to stock 2.2 on nexus

HELP!!!!!!!!!!!!!!!!
I downloaded the Update-Passion-Full-FRF91.zip and it gives me an error when i try to flash! What am I doing wrong.
Error is
E:no signature (575 files)
E:verification failed
someone

(remote: invalid kernel address: not lie in memory) when booting the lg350z kernel

I have found the source for LG-350Z kernel over LG's opensource official website was successful when compiling despite some errors during compilation I was able to pass that by adding some fixes. It was compiled with GCC 4.8 compiler. Now the thing is that when trying to boot it with the following command:
fastboot boot zImage-dtb
as I tried another image without dtb extension:
fastboot boot zImage
I get this error:
creating boot image...
creating boot image - 6518784 bytes
downloading 'boot.img'...
OKAY [ 0.229s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.251s
Can anyone please tell me why it is not booting or how to fix it?
Note: the kernel is not modified yet, I am just learning how to compile a stock kernel from the source I am kinda new to this.
please any help same here infinix hot5 x559c[
C:\platform-tools>fastboot boot twrp-3.3.1-0-hammerhead.img
Sending 'boot.img' (13290 KB) OKAY [ 0.615s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed
]
could it be the use of the wrong recovery image which I pulled from the team win official page itself I have done a couple of times using different recoveries specific for infinix hot 2 from the same brand the problem is that can't find the one specific for my device please any advice on this thanks.

Downloading And Building QQ1B.200105.004 Kernel?

I attempted following the official guide, but was unable to find the kernel sources in the checked out tree.
Am I missing something obvious?
What would be the correct way to download the kernel and build it for the Pixel 4 XL?
Same QQ1B issue
Hi, I am having issues also. When I try to fastboot the image I get:
creating boot image...
creating boot image - 15968256 bytes
Sending 'boot.img' (15594 KB) OKAY [ 0.440s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
When I built for the QD1A version, I had no issues. I hope someone can help us..

Moto G6 Forge - Cannot flash to recovery

I have a Moto G6 Forge Cricket that I forgot the password to. I have been trying to boot into another image without data loss in order to go in and delete the password config files, but have not been able to get anything to work. USB debugging doesn't seem to be on, the bootloader is locked, and I have no idea if it's possible. I can access fastboot and android recovery. Fastboot says the product variant is "jeter XT1922-9", leading me to believe that it's just a reskinned moto g6 Play.
I have tried recovery loading update aroma file manager from SD card, which failed signature check. Updating over adb doesn't work, as the phone doesn't show up in adb at all, only fastboot.
I tried flashing TWRP recovery for the moto g6, and got the following output on PC:
C:\Android\SDK\platform-tools>fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17626 KB) OKAY [ 0.559s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
On the phone, I see a series of yellow cmd log lines leading up to "cmd: flash:recovery" followed by pink "Mismatched partition size (recovery)" Some posts said that this was an ignorable error and to just proceed into recovery, but when I did it just went to the normal android recovery.
I also tried just using fastboot boot, but that obviously didn't work due to the locked bootloader.
C:\Android\SDK\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (17626 KB) OKAY [ 0.563s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I'm out of ideas and out of google search results that aren't SEO spam to read. If anyone knows something else I could try I would be happy to hear it. Thank you so much!
The only thing I can think of is using the factory recovery to erase the user partition / factory reset.

Categories

Resources