Hot answers tagged rom-flashing
I had the same problem while upgrading to CM13 from CM12.1. You can solve this problem without deleting your database files and therefore losing data as suggested in the other answers. The culprit seems to be broken database onUpgrade code in the TelephonyProvider of CM. The ppp_number column of the carriers table does not exists, but the upgrade code ...
The answer is almost definetly no. Although there might not be much difference between the models, there are bits that are different. These bits won't work. Other bits may depend on these bits, and they won't work either. The baseband and radios might work fine, but the rest of the mismatched components will lead to, at best, a soft brick. I have a Moto G ...
The arguments which may be supplied in the recovery.command file: * --send_intent=anystring - write the text out to recovery.intent * --update_package=path - verify install an OTA package file * --wipe_data - erase user data (and cache), then reboot * --wipe_cache - wipe cache (but not user data), then reboot * ...
You can try this while the phones is on. (You MUST have USB debugging enabled and authorized) adb shell recovery --wipe_data
Have you rebooted the device after "Unlocking bootloader"? fastboot reboot You need to execute this command before flashing custom ROM. Also, You don't need to turn on USB debugging when unlocking bootloader.
Only top voted, non community-wiki answers of a minimum length are eligible