Quote:
Originally Posted by porkupan
Just want to correct some misinformation.
Two things have nothing to do with each other. - enable_adb only enables the ADB. If you don't need the ADB, you don't have to run it.
- The SD recovery can be done without enabling the ADB. It only reconstructs two partitions: /data and /system
- ADB and serial console are two unrelated things. The "serial console" (USB serial gadget) in recovery mode can be achieved by copying the package into the "main memory", and switching to recovery mode. The ADB login is available at runtime, when the reader is connected to a PC running ADB.
- enable_adb doesn't install a new bootloader. If corrects the uboot variables to enable loading a larger ramdisk (needed to fit the ADB).
|
thanks, you confirmed my impression on enable_adb, and beside the fact that the new .bin contains only an adapted loading parameter for the ramdisk, everything was very clear to me.. actually big surprise because I expected uboot env data to boot where contained a part in the boot.src file out of the bin, btw some mkimage magic I miss...
"can be achieved by copying the package into the "main memory""? I don't follow you there.. do you mean to write into the internal flash the two .ko? they are actually included in the ramdisk/lib/modules etc..
my problem, I m trying to get a dump of the partitions, I am at the beginning of the beginning... your flashing tools based on XXX update.package won't work for me as I believe the RSA key is different. I think the RSA key is somewhere stored around the beginning of the bootloader (I looked at your scripts to extract the .packages) I need a dump before.. so I am back to the beginning