They only modify the size of the system and data partitions. Of the current PIT files, I don't think any of them wipe the BML1 and BM元 boot partitions. But the important bit is that the phone will not become a Brick. This will ensure the user can still reach Download mode, even though the user will have to flash an ROM to be able to boot the phone into Android after that. If the PIT needs changing, only flash the PIT and with the bootloader tool (described above). Have the tool implement a feature to read the PIT from the phone and if the PIT provided by the user is the same, automatically do not re-partition. So long as the boot loaders are not touched, even if boot loaders are in the user provided file, the user can always recover using the 301K JIG.Īnother thing to consider is the PIT. Instead it uses the files provided by the user to flash only the rest of the phone, and never the bootloaders. Have another tool, that does similar, but that will never flash the bootloader. If a new ROM is published with a new boot loader, prevent the user from using it, until developers upgrade HEIMDALL one-click to recognize the new boot loader. I9000 or P9000.ģ) Check the USB ID of the phone is correct.Ĥ) Double checks that the boot loader files provided by the user are compatible.ĥ) Automatically use adb to switch the phone into download mode Can you do things like *#06# from the adb command line?)Ģ) Do a checksum on the bml1 and bml3 backups to identify which boot loader is actually on the device, and therefore identify the device. Some method to automatically check if the phone is 'network locked' might help. If a user cannot get root, they really should not be flashing their ROM in the first place. (Might as well backup efs also and check the user has root. Have a single tool that automatically does the following (unfortunately, only possible on a rooted phone):ġ) Uses adb to backup the bml1 and bml3 boot loaders. Too many people are, for example, accidentally upgrading P9000 ROM onto I9000. We would like to make a idiot proof ROM upgrade method.
0 kommentar(er)
