Hoping this is still monitored! My TF300t is unlocked, rooted, TWRP v2.5.0.0 installed and ran nvflash backups when I was on v9.4.3.17. After a year of doing fine,
I lost my bootloader menu and always start in APX mode. I've managed to update to v9.4.3.30 manually but thinking I still have the bootloader flashed during the
nvflash process (I've always run US software per "About tablet", but it still shows the WW SKU v9.4.3.30 bootloader...always showed after doing the nvflash backups).
Hopefully still reading, lol! Without fastboot access, I've tried most everything to get the bootloader menu back - figure a stock v9.4.3.30 bootloader might
fix it. No matter what, the bootloader doesn't flash or stick - maybe rebooting because to get into ICS requires rebooting using wheelie/nvflash so it "prevents" the flash?
I'm wondering if trying the original method with the dlpkgfile and command file in post #2 would still work in updating my bootloader, update me to first JB version with
the JB bootloader, and get me booting normally? At which point I can apply the newer updates & re-root...
Main concern (if I should try this) is the dlpkgfile is smaller than the OTA update. Is it a subset or the complete v10.4.2.9 JB update?
And in case wondering, I have already tried manually updating using US_epad-user-10.4.2.9.zip but it freezes on final boot up. Appears the bootloader is still
the old ICS one and didn't update to JB v10.4.2.9... Thanks for any insights on using the original process or other ideas!
I lost my bootloader menu and always start in APX mode. I've managed to update to v9.4.3.30 manually but thinking I still have the bootloader flashed during the
nvflash process (I've always run US software per "About tablet", but it still shows the WW SKU v9.4.3.30 bootloader...always showed after doing the nvflash backups).
Hopefully still reading, lol! Without fastboot access, I've tried most everything to get the bootloader menu back - figure a stock v9.4.3.30 bootloader might
fix it. No matter what, the bootloader doesn't flash or stick - maybe rebooting because to get into ICS requires rebooting using wheelie/nvflash so it "prevents" the flash?
I'm wondering if trying the original method with the dlpkgfile and command file in post #2 would still work in updating my bootloader, update me to first JB version with
the JB bootloader, and get me booting normally? At which point I can apply the newer updates & re-root...
Main concern (if I should try this) is the dlpkgfile is smaller than the OTA update. Is it a subset or the complete v10.4.2.9 JB update?
And in case wondering, I have already tried manually updating using US_epad-user-10.4.2.9.zip but it freezes on final boot up. Appears the bootloader is still
the old ICS one and didn't update to JB v10.4.2.9... Thanks for any insights on using the original process or other ideas!