1
Gemini PDA - Android / modified boot images lead to boot cycles
« on: December 23, 2018, 02:24:55 pm »
right, one needs to make sure to use the gemini-PDA version.
Just tried something else to trace the problem somehow. I extracted the working recovery.img from my recovery partition and did a hexdump which results in this output:
00000000 41 4e 44 52 4f 49 44 21 2d a4 7a 00 00 00 08 40 |ANDROID!-.z....@|
00000010 fb c0 3a 00 00 00 00 45 00 00 00 00 00 00 f0 40 |..:....E.......@|
00000020 00 00 00 44 00 08 00 00 00 00 00 00 29 09 04 0e |...D........)...|
00000030 31 35 34 30 39 35 33 33 38 32 00 00 00 00 00 00 |1540953382......|
00000040 62 6f 6f 74 6f 70 74 3d 36 34 53 33 2c 33 32 4e |bootopt=64S3,32N|
00000050 32 2c 36 34 4e 32 20 62 75 69 6c 64 76 61 72 69 |2,64N2 buildvari|
00000060 61 6e 74 3d 75 73 65 72 00 00 00 00 00 00 00 00 |ant=user........|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
The twrp image results in the following output:
00000000 41 4e 44 52 4f 49 44 21 0b 0c 79 00 00 00 08 40 |ANDROID!..y....@|
00000010 83 17 71 00 00 00 00 45 00 00 00 00 00 80 f7 40 |..q....E.......@|
00000020 00 00 00 44 00 08 00 00 00 00 00 00 1a 11 04 0e |...D............|
00000030 31 35 31 37 33 31 32 32 37 30 00 00 00 00 00 00 |1517312270......|
00000040 62 6f 6f 74 6f 70 74 3d 36 34 53 33 2c 33 32 4e |bootopt=64S3,32N|
00000050 32 2c 36 34 4e 32 20 62 75 69 6c 64 76 61 72 69 |2,64N2 buildvari|
00000060 61 6e 74 3d 65 6e 67 00 00 00 00 00 00 00 00 00 |ant=eng.........|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
Maybe one of the tech specialists can spot the problem. The most obvious to me was the difference in the bootvariant which is user or eng. Not sure whether this is relevant.
Just tried something else to trace the problem somehow. I extracted the working recovery.img from my recovery partition and did a hexdump which results in this output:
00000000 41 4e 44 52 4f 49 44 21 2d a4 7a 00 00 00 08 40 |ANDROID!-.z....@|
00000010 fb c0 3a 00 00 00 00 45 00 00 00 00 00 00 f0 40 |..:....E.......@|
00000020 00 00 00 44 00 08 00 00 00 00 00 00 29 09 04 0e |...D........)...|
00000030 31 35 34 30 39 35 33 33 38 32 00 00 00 00 00 00 |1540953382......|
00000040 62 6f 6f 74 6f 70 74 3d 36 34 53 33 2c 33 32 4e |bootopt=64S3,32N|
00000050 32 2c 36 34 4e 32 20 62 75 69 6c 64 76 61 72 69 |2,64N2 buildvari|
00000060 61 6e 74 3d 75 73 65 72 00 00 00 00 00 00 00 00 |ant=user........|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
The twrp image results in the following output:
00000000 41 4e 44 52 4f 49 44 21 0b 0c 79 00 00 00 08 40 |ANDROID!..y....@|
00000010 83 17 71 00 00 00 00 45 00 00 00 00 00 80 f7 40 |..q....E.......@|
00000020 00 00 00 44 00 08 00 00 00 00 00 00 1a 11 04 0e |...D............|
00000030 31 35 31 37 33 31 32 32 37 30 00 00 00 00 00 00 |1517312270......|
00000040 62 6f 6f 74 6f 70 74 3d 36 34 53 33 2c 33 32 4e |bootopt=64S3,32N|
00000050 32 2c 36 34 4e 32 20 62 75 69 6c 64 76 61 72 69 |2,64N2 buildvari|
00000060 61 6e 74 3d 65 6e 67 00 00 00 00 00 00 00 00 00 |ant=eng.........|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
Maybe one of the tech specialists can spot the problem. The most obvious to me was the difference in the bootvariant which is user or eng. Not sure whether this is relevant.