FORUMS

Beats Music No Longer Accepting New Accounts

Whenever Apple launches a new product or service, it definitely manages to grab the … more

Do You Do Self-Repairs on Your Devices?

As smartphone designs become more and more complex, self-repairs on devices are also becoming … more

Sony Z4 Slips Out of Top 5 Smartphones in Japan

In a bid to streamline its flagship series which had been losing credibility over the … more

Sprint’s New Unlimited Plan with Ridiculous Capped Speeds

The carrier game in the United States is perpetually rushing forward at … more
Thread Deleted Subscribe to Thread Email Thread
Prev Previous Post   Next Post Next
Have lost my boot menu/fastboot access & appears to be bootloader related. Currently only have access to APX, ADB, & TWRP. Have tried numerous times to
flash the v9.4.3.30 blob.EBT (using the "nvflash -r download 5 blob.EBT" command) but doesn't appear to be taking (WW SKU displayed matches one from AndroidRoot,
not the US SKU from the blob I'm trying to flash). Also downgraded to v9.4.3.17 as a test and all but the bootloader were updated. Same - has a US SKU, but still a
WW bootloader displays...

Without fastboot, can I use "nvflash -r --download 13 blob.EBT" to get it into staging, reboot and hope it takes? And to make sure staging is clear, is there any problem
doing a format_partition (within nvflash) on it?

Is there a better way that might get it flashed correctly? Would adb work (dd if=/sdcard/blob.ebt of=/dev/block/mmcblk0p4) or would I need to have the entire blob as
the input file?

One last resort would be to try flashing the bricksafe.img. Sure wish I knew why I have the nvflash backup files saved in triplicate. Not very useful when I don't know how to use
them to get me back to SOP

Thanks!
Last edited by wha2do; 23rd February 2014 at 03:56 AM.
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes