LozHensel
Newbie
Me again, continuing problems from this thread. I still have an iNew L4. I have now downloaded this rom, and flashed everything I can find to flash (boot, cache, recovery, system, userdata). Despite that the adware (apparently called Android.Waps.a) is still there. it's certainly persistent, I'll give it that!
I have got adb working, and fastboot seems to work too apart from one thing:. It tells me that erase commands fail. I get the following error:
$ fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.003s
Doing it as root doesn't seem to help, nor does starting the adb daemon as root.
I can flash things only so long as I pass the -u command, which means don't wipe it first, otherwise I get the above error message (barring the partition being erased - that seems to make no difference either). fastboot erase and fastboot format produce pretty much the same response too.
Interestingly adb remount also doesn't work (citing permissions), and if I open a shell on the phone (via adb shell) I don't have permission to mount anything readwrite even if I am root before opening the shell, and su is apparently an unknown command (sudo likewise...)
So why can't fastboot erase anything? Is there a hidden option I need to enable like oem bootloader unlocking? If fastboot can't do it is there another way?
I have got adb working, and fastboot seems to work too apart from one thing:. It tells me that erase commands fail. I get the following error:
$ fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.003s
Doing it as root doesn't seem to help, nor does starting the adb daemon as root.
I can flash things only so long as I pass the -u command, which means don't wipe it first, otherwise I get the above error message (barring the partition being erased - that seems to make no difference either). fastboot erase and fastboot format produce pretty much the same response too.
Interestingly adb remount also doesn't work (citing permissions), and if I open a shell on the phone (via adb shell) I don't have permission to mount anything readwrite even if I am root before opening the shell, and su is apparently an unknown command (sudo likewise...)
So why can't fastboot erase anything? Is there a hidden option I need to enable like oem bootloader unlocking? If fastboot can't do it is there another way?